Best reason for a built-in downloader in Bridge

Question

I just heard the best reason to have a photo downloader built-in to Bridge. I already own Downloader Pro from Breeze Systems which is a bit complicated to set up, but has great functionality. But, because it's not integrated into Bridge, my workflow has extra steps in it that aren't necessary.
So now I just read that the new RawShooter Premium has a great feature. It has a built-in downloader and while doing the download, it is also building all the thumbnails. Thus, when the download finishes, there's no extra step to scan your whole directory and then build thumbs. This is a huge workflow time savings. My typical workflow consists of. Pop the CF card into the reader, Downloader Pro pops up. I type in a job code to help name the directory meaningfully and hit OK. I walk away while while it downloads.
I come back after it downloads. I point Bridge at the new directory. I walk away again while Bridge builds it's thumbs.
If Bridge has a built-in downloader and was building thumbs during the download, I'd save a whole step in my workflow and a bunch of time.
It makes some sense to build thumbs during the download. After all, the entire image is going through RAW during the download anyway. It's better to do whatever needs to be done to the images on the first pass rather than putting them on disk with the download process and then coming back and reading them all over again to make thumbs.
I'm writing this not because I'm thinking about switching to RAW Shooter, but because I'd like to see Bridge improve and take this extra step and time out of my RAW workflow.
BTW, it would also help to allow Bridge to continue to build thumbs when I have the ACR window open. Now, as soon as I open a RAW image, all thumb building stops until I finish with the ACR window. The fact that Bridge won't build thumbs in the background while using ACR is a real pain and is why I have to walk away and wait for Bridge to finish building thumbs before starting the RAW edits.
--John

Answer 1

>
Adobe is fully committed to an injest feature.
I hope Adobe offers a richer downloader in the future that's competitive with other downloaders and that covers all the workflow steps involved in transferring images (auto-recognition of an inserted CF card, directory creation by a user-specified rule, directory naming including custom naming, ability to split into multiple directories by day from the same card, super fast download, download verification, card clearing, thumb building, etc...) all done with one interaction at the start of the download process.
I may experiment with pointing Bridge at the download directory and letting it start indexing at the same time as my downloader is getting the images. That might save one "walk-away-from-the-computer" step in my current workflow.
I think it's a cop-out to not offer to delete the images from the CF card after download. The user should be prompted and it should be a feature the user can turn off, but it's a mandatory step in any photo workflow, every other downloader I've seen offers this option (even the one in Photoshop Elements). If some users want to only delete images by reformatting in the camera, that's their prerogative. I only reformat every once in a while and I've never had a problem and doing it from Downloader Pro saves me a workflow step.
The ideal downloader would verify that every image was successfully transferred to the PC, inform the user that everything has been transferred and then prompt to clear the card with an option to turn off this feature.
One thing that is happening in the photo marketplace is that programs like RawShooter and Aperture have 100% focused on all aspects of the RAW workflow for the pro or enthusiast that shoots RAW. While I appreciate and use many of the RAW workflow improvements in the latest ACR/CS2, I hope we see the same kind of focus from Adobe. Downloading files from the card is just one piece of that workflow and Adobe doesn't have a competitive offering in that area now.
--John