Earlier quoted context omitted.
I discovered Lytro at the Maker Faire when they had their "borrow a Lytro" demo. It was a great bit of marketing: take a Lytro around the Faire for an hour (where are there are always plenty of interesting subjects) and afterward they put all your shots in an online gallery for you. I got a fun shot or two that day and promptly bought one of their first cameras. But it wasn't a very good camera, and they completely m…
I've got a Lytro, and haven't used it for years, for many of the reasons you articulate. To my mind their mistake was not having an open source library that could work with their capture format, including basic support for focusing and producing an output image for display. Pretty much every new photography tech has had a community of amateurs and professionals spring up around it and (hopefully) innovate. They misse…
Oh, now you are making me wistful for what might have been.
If they'd had any kind of library or API, I could have played around with my Ken Burns idea by writing a few lines of code!
I've seen this same mistake over and over again going back to the earliest days of GUI apps: designing the user experience with hardcoded interactions instead of building the UI on top of a public API that enables others to create and experiment with their own interactions.