Google Photos – some observations

I’m following up my previous post with some notes based on using Google Photos for a couple of days of testing and observation. This will lead into some thoughts on how I will use it, and what I need to do to make sure the Workflow is “right” for me. This might also be relevant to others, especially those using both DSLR and Smartphones, so I’d welcome comments.

The first thing to mention is that My Drive > Google Photos and the separate Google Photos menu item on your Google Drive are not the same! This is reflected in this note which advises you not to use Google Photos Backup (from your Desktop) and the sychronised My Drive > Google Photos  local folder at the same time.

What this means in practice is that if you have a Workflow that involves placing an image in your local Google Photos folder to sync to your My Drive folder on Google Drive for sharing, or for embedding in a blogpost (like the tasteful one above taken during the testing 😆 ), then you probably shouldn’t use the Google Photos Backup application.

What does this mean then? Well a couple of observations.

  1. Google Photos is a good repository for images taken with Smartphones; it’s painless, quick and ensures that if you have auto-sync switched on in either your Google Photos app, or in the Google+ app (for iOS 7, or earlier) that you have a safe and secure home for your images which will have lots of other advantages. read this excellent review by Mike Elgan for further information.
  2. If you’re a DSLR camera user then you have to think carefully whether you want to use the Google Photos Backup application on your desktop.
    1. If you don’t use any other Image Editing software then it might well be a good idea – setting the Image Quality probably to High (so that you don’t use any of your 15Mb of Free Storage) and following the guidance in the note referenced above about excluding your My Drive > Google Photos from your Google Drive synchronisation, if relevant.
    2. If you’re using something like Lightroom to post-process your images then it might be better to use the export options in the software to copy an image (or collection of images) from the software to your My Drive > Google Photos folder to sync up to Google Photos  and then on for sharing from either your desktop, or your mobile device a little later, and not using the Google Photos Backup application.
  3. Luckily none of the decisions you make now are irreversible, but a bit of careful consideration now may mean that you have the “right” workflow for your needs. For me as an iPhoneographer and DSLR camera user I’m happy to let Google Photos now be my Backup and Storage Solution of choice for the iPhone (see 1 above), but because I’m also a Lightroom user I’ll not use the Google Photos Backup application. Moreover, having made this decision it means that I can, if I chose, Import any images taken on the iPhone into Lightroom for post-processing, meaning I don’t clutter Lightroom up with images I don’t really want to keep.

Any thoughts?

Comments

comments

2 thoughts on “Google Photos – some observations”

  1. It turns out it’s all rather academic for me. No iOS 7 support, and the uploader just keeps saying “Couldn’t backup these files”, listing a bunch of RW2s (even when I have ‘upload RAW’ unchecked) and going back to ‘51,471 photos still to upload’. I guess that solves my duplicates problem, though…

    Now to see about iCloud…

    1. Yes, I referred to the “glitch” in my workflow through having an iOS 7 iPhone 4s. However … having the iPad2 on iOS 8 (albeit running rather slowly) – it does allow a workaround (should I need it).

      What’s more interesting and perhaps more worrying is the lack of a usable API for Google Photos (as yet). This popped up on Google+ this morning …

      https://plus.google.com/u/0/+GerwinSturm/posts/MVKMXEk3QCe referencing …

      http://codingwithgerwin.blogspot.co.uk/2015/06/the-photos-dilemma.html

      Bit depressing really.

Your thoughts ...