tyler.io

This was a puzzler.

I’ve had an iPhone 5S since last fall, but haven’t ever done much more than just play with the slow motion video capture feature. Yesterday though, I had a need to take a slow-mo video and post it to Facebook. I recorded the video easily enough, set the slow motion start and stop points, and then used OS X’s Image Capture app to export the video to my Mac. I figured I could then just upload the movie to Facebook.

Not so fast.

The video that Image Capture pulls off your phone is the raw 120FPS movie with no slow motion start/stop points. While this behavior actually makes sense, it’s not what I wanted. I need the version with the slow motion effect. I did some googling, and the only solution is to upload the video to Facebook using iOS’s native sharing feature. This gives the Photos app an opportunity to render the video at normal speed with the slo-mo effects in place. So I tried that, but the app complained the video was too large. Fine. I tried emailing it to myself – same problem. Too large. The Photos app wanted me to trim the video to a shorter length. I did some more googling but couldn’t find any way of exporting the full-res video with the slow motion effect in place.

Aha!

It dawned on me that Apple’s Photostream feature shares full-res videos to iPhoto on Mac. So here’s what I did…

1. Create a new, shared Photostream that only you are a member of.
2. Share the video to the new stream.
3. Open up iPhoto on your Mac and navigate to the shared stream.
4. Drag the video to your Desktop.
5. Upload to Facebook/Instagram/wherever.

Boom.

What follows is the first half of the introduction to the book I’m working on about organizing your photo library with Dropbox. I thought some of you might like to see what I’ve been working on as I get closer to launching in July.

I adamantly believe that our photos and home videos are the most important digital assets we have. They document our lives, remind us of our our best moments, and teach us who we were. Yet, most people rarely give a second thought to how they preserve, protect, and share those memories. They’re content to leave everything in a giant, digital shoebox that may or may not be backed up. Thousands of photos stored in your phone’s camera roll here, a smattering of memories uploaded to Facebook and Twitter there, and none of them organized, backed up, or protected in any way.

It didn’t use to be like this. For both my sister and I, from the day we were born until we turned eighteen, my mother kept a photo album for each of us for each year of our life. By the time my sister went off to college, our family room bookcase had amassed over forty albums – filled to the brim and overflowing with photos of our youth. My mother had a longstanding rule: if the house were to catch fire, my father’s first job was to get everyone out safely. He was then instructed to run back inside and save as many of those albums as he could. And in all seriousness, my mother wasn’t exactly kidding. Those memories meant the world to her. If she were to spill coffee on one of them she’d be sad. But if she were to lose all of them in a fire, she’d be devastated. Everything else in the house could be purchased a second time. But those albums were irreplaceable.

Today, things are much better. Sure we may print off and keep some of our family photos in actual albums, but most of our digital memories live on our hard drives, where we have plenty of opportunity to back them up and keep them safe. So why do so many of us go about our digital lives with our head in the sand? Every hard drive you own, whether in your laptop, your iMac, or even your super-expensive networked storage device, will fail. It’s a guarantee. One day, the photos and videos stored on it will be lost forever when the hard drive finally dies. So why wouldn’t you take a few simple steps and spend a little extra money to ensure that when it does happen, you have a backup in place?

I’m not sure when things changed, but I suspect it’s a two part problem brought on by our increasingly online lives. As digital cameras took over and people stopped paying to develop film, the actual price of each photo plummeted. And with it, the perceived value. Further, as the digital storage space available to us increased, people began taking more and more photos – eventually reaching the point where they could no longer keep track of their photo collections or find the tools to keep them organized and protected.

Instead of photo albums of family vacations and birthday parties sorted chronologically on a shelf, our digital photo libraries are a jumbled mess. Thousands of snapshots in a single camera roll on your phone, with no meaningful way to browse through them. The oldest ones haphazardly deleted and lost forever to make room for new ones. People mistakenly believe that they can always get their pictures back from Facebook if they ever need them. Or worse, they believe that Apple is somehow magically backing up all of their photos into iCloud. Neither one is true.

While researching this book, I had a conversation with two friends. Neither is technical at a developer level, but both are long-time Mac and iPhone users. They know their way around the platform.

My first friend, we’ll call him Ted, said he was having trouble with his iPhone. His photos and videos had grown to take up nearly 10GB of storage space. And with only a 16GB iPhone, his device was very nearly out of room. He wanted to know how to backup his photos off his device but still be able to access them when needed.

He assumed there was an Apple-centric way of doing this. He figured he could just buy more iCloud storage space. He was shocked when I explained to him that the only user-friendly solution I know of is Dropbox. I told him that even if he bought more than the default 5GB of iCloud space, he’d still be limited by his on-device storage limits. iCloud only backs up what’s currently on your phone. If you delete photos and videos from your device, they’re similarly deleted from your next iCloud backup.

I walked him through how the Dropbox app works. Install it on your phone, sign up for an account, and the app periodically uploads everything in your camera roll to your Camera Uploads folder in your Dropbox. Once uploaded, you’re safe to delete them from your device – freeing up space. Then, you can either use the Dropbox app to browse your photos, view them on your computer, or use a dedicated Dropbox photo app like the wonderful Unbound.

Ted thought that idea sounded great and was ready to sign up. But then I told him the catch – the free Dropbox plan only offers 2GB of space. He needed at least 10GB, which I said would cost $99 a year.

He was dumbfounded. In an age where seemingly every online service is free, why should he have to pay for Dropbox? I tried explaining the value it added and how much I loved the service, but he just couldn’t get past the idea that this was a service that Apple should be offering as part of owning the phone. I couldn’t really disagree with him. It does seem like a problem Apple should be solving, but they’re not.

My other friend chimed in. He said he wasn’t worried about his photos and videos because he was backed up. I asked if he were already using Dropbox or paying for one of the larger iCloud storage plans. He said “No, I bought the larger 32GB iPhone so all my data is backed up with Apple.”

This time I was flabbergasted.

He went on to explain that all of his data was safe because of iCloud. I let him finish and then had to break the bad news to him that iCloud only works for the first 5GB. Once you go beyond that, none of your data is backed up unless you’re a paying customer. Apple, through all of their flashy marketing around iCloud and promises of how it “just works”, has convinced a large set of non-technical users that their most precious data, their photos and videos, is safe when it’s actually anything but.

This is exactly the problem that I’m writing about in this book. I’m desperately trying to preach to users that the data you hold so dear isn’t being handled by Apple. If you lose your phone, in most cases, your photos and videos go with it. And as I talk to more and more people about this problem and explain to them how things actually work, so often I’m met with incredulous stares. Not that they’re surprised or outraged that their data isn’t safe, but at the sheer audacity that someone would suggest they need to pay for their data’s safekeeping.

In person and in this book, my goal is to make a solid case that your data is most definitely worth the measly $9.99 per month Dropbox charges. My sister was absolutely devastated when her iMac’s hard drive failed without a backup in 2005. She mistakenly thought that her iPod’s photo cache served as a full backup of her photos. I can still remember the awful look on her face when I explained that her four years of high school photos along with the first year of her college photos were reduced to nothing more than 160 pixel wide thumbnails.

Apple never marketed to her that her iPod Photo backed up her memories, but she still mistakenly assumed that when it asked to sync her photos. But now we’re in an even worse situation where Apple really is marketing to users that all of their data is safe. I can only cringe at the thought of how many customers go to a genius bar to get a replacement phone and are told “just sign into iCloud and all your data will be restored” only to find out that’s not the case.

My mother meticulously archived and organized our family photos into dozens of albums when we were growing up. All those albums and film development cost real money. Every roll of film, every trip to the camera shop, every album, and don’t forget all the time put into organizing and pasting photos into the albums. It was an investment. The idea that everything online should be free has created a pernicious entitlement culture where users are unwilling to pay a little money to safeguard their most precious digital memories.

It’s a terrible situation and one I’m trying to correct. This book is the antidote to most people’s digital negligence. It will teach you a simple method for organizing, sharing, enjoying, and protecting your most valuable memories.

Who this book is for

I should say up front that this book is for consumers. While the sharing and backup solutions I present may be of use to professional photographers, the organization and review strategies will likely clash with the workflows of people who take photographs for a living. I also won’t be covering how to handle and process RAW format photographs. Everything I write about will assume we’re dealing with JPG files from your camera phone, point and shoot camera, or your prosumer DSLR.

I should also say that the examples I present and the software I recommend are definitely Apple-centric. We’ll be covering ways to archive photos from your iPhone and iPad, ways to share those photos with Photostreams and Apple TV, and we’ll be using tools that, to my knowledge, are only available on Mac. Most of the ideas and tactics I write about can be used on Windows or Linux platforms, but the automation techniques are Mac only.

Why listen to me?

Hopefully everything sounds great so far. But you may be wondering why you should listen to me. What makes me the expert? The simple answer is that I’ve been thinking about today’s digital photography challenges constantly for the last few years as I’ve watched my own collection become more and more unwieldy. I’ve honed my workflow to be as simple and, most importantly, automatic as possible. I’ve learned that I lose focus and things grow unorganized as the complexity of my workflow increases. But, by keeping things simple, repeatable, and efficient I’ve found a happy medium where I’m able to keep my photo library under control without devoting too much time to curating it. It’s the techniques I’ve settled on over the last few years that I plan to share in this book.

Those techniques are modeled after the principles I’ve learned practicing David Allen’s Getting Things Done methodology for the last ten years. In his book, he teaches a series of concrete steps that can be taken to reign in any complex system. I’ve simply adapted his teachings into a workflow for managing your photo library.

Further, my background as a long-time Mac app developer provides me with additional insight into finding the best software tools and automation techniques for the job.

If you follow the steps I outline, you’ll quickly find yourself with an organized photo library that’s accessible on all your devices, backed-up in case of disaster, and shareable to all your friends and family.

For six years I carried a bright green, nylon, kid’s wallet I bought from Target. I enjoyed the simplicity and “funness” of it. But last year I finally decided to grow up and buy a real, adult wallet. I hate fat, George Costanza wallets and, as a rule, only carry the absolute bare minimum of cards. So when I started shopping around my top priority was finding something equally as slim as the old kid’s wallet I had been carrying.

After reading lots of reviews I settled on a blue, leather Note Sleeve from Bellroy. It’s been a year since I started carrying it and I couldn’t be happier.

The wallet has two slots on the inside right side for your most frequently accessed cards. Each slot can hold two cards comfortably. Beneath that area, is storage for two or three less frequently used cards. There’s a small, leather pull-strap that allows you to slide the cards out for easy access. On the left is a single slot where I keep my driver’s license. Every wallet I’ve previously carried kept your license behind a plastic window so you could just show people your age. But, in practice, every restaurant or store I visited always insisted I take the card out and hand it to them. Prying it out from behind the plastic window was always a pain. I have no trouble accessing it with this wallet. I can pull it out and slide it back in without trouble.

Like most wallets, the Note Sleeve has a full-length pocket for cash. This model is barely wide enough to fit unfolded American currency, so I normally just fold my bills in half. I really like the pattern inside the pocket. Of course, no one ever sees that except for me, but I like it anyway.

Inside the cash sleeve is a secret, hidden pocket. I use this slot for my auto and health insurance cards. I rarely ever use them, but always need them with me, so this extra, hidden pocket is great for that purpose.

When folded in half, the wallet lays quite flat. I’ve compared it to a few of my friends’ wallets and the Note Sleeve is always the slimmest.

As I said above, I couldn’t be happier with my choice. It’s slim, very well constructed, and looks nice. I finally feel like a real adult.

After my previous post I got curious as to the total number of words I’ve written in Day One so far. A quick Google search didn’t turn up any obvious solutions, so here’s a short PHP script that gives you a total. Just pass it a path to your .dayone journal file at the command line like so

php count.php /path/to/journal.dayone

Back in October I wrote a post about how I’ve adopted a routine of journaling what I’m currently working on throughout the day in addition to a final recap of the whole day each night before bed. My one year anniversary of starting my journal passed back in February with little fanfare. But looking at it now, I’ve logged 626 entries and have a streak of 428 days in a row. As far as total word count, I’m guessing I’ve written somewhere between 75,000 and 100,000 words. That’s a whole book! Reflecting on that today has caused me to look back at everything I’ve accomplished this calendar year – a period where, because of the birth of my son, I thought I’d surely get very little done. Highlights include…

• Launching a brand new responsive website design
• Beginning work on a new book.
• Building and shipping a major new update to my flagship app, VirtualHostX.
• Building a shipping a new app and the accompanying web service.
• Recommitting myself to writing more on this blog – 10,000 words so far!

All while holding down a day job and learning how to care for a newborn. Not to brag, but I’m damn proud of myself for continuing to push my business forward these last three and a half months. And that’s caused me to think about what’s contributing to my productivity. What am I doing differently that’s keeping me on track and motivated.

The biggest factor I can identify is that my habit of journaling each day is finally starting to pay dividends. My nightly recap has forced me to be more aware of how I’m spending my time – precisely because every night I take five minutes and write down what I accomplished that day. On days when I don’t have much to write or when I fail to do one concrete thing to move my business forward, I don’t necessarily feel like a failure, but I do feel a little guilty. On the flip side, days where I do accomplish something give me a bit of a high – and the more days in a row I keep the chain in tact, the better I feel.

Because I’m now more aware of how I spend my time, I’m no longer haphazardly working on stuff in the moments in-between everything else in life. Instead of turning to my work simply because I’m bored elsewhere or I happen to have a free moment, I’m setting aside dedicated time each day for work.

My kid goes to bed at seven and my wife at nine. After that, the house is quiet and I’m free to do whatever I want. I’ve chosen to deliberately make those hours from 9pm until midnight all about my work. That’s not to say I don’t open a beer and have a baseball game playing in the background, but those three hours are now sacred to me. They’re when I get shit done. I no longer approach that time hoping I’m in the right mood and mindset to work. Because I have the daily journal entries to prove I’m capable of doing work at that time, I sit down at 9pm with renewed confidence knowing I’m capable and have a consistent track record of performing.

I can’t emphasize enough how important journaling has become to me. It’s caused me to be more aware of how I spend my time, which ups my confidence as I’m able to reflect on all the many things I’ve accomplished. Like a productive vicious cycle, that only serves to motivate me even more.

Back in 2008, when I worked for Yahoo!, I had the good fortune of chatting with Tom Coates a few times about the now defunct Fire Eagle location brokerage service. Fire Eagle was my absolute favorite product to come out of Yahoo! during my time there. I’ve always been fascinated by real-time location data and sad that Fire Eagle’s intersection of privacy and ease of use never caught on.

Anyway, fast-forward to last Summer, I was bummed that although so much of my life is documented through photos, tweets, and journal entries, my location data was missing. A few products tried to solve this problem post-Fire Eagle. Google Latitude (née Dodgeball) gave you a way to seamlessly track your location and view your history, but they’ve since sunsetted that product. And, besides, it was a little creepy having Google track your every step. (Which I realize they still are via Google Now, but that’s another conversation.) There was also other apps like Rove and Foursquare, but none of them offered quite the feature set I was looking for. In 2010, I even went so far as to reverse engineer Apple’s Find My iPhone API so I could remotely query my phone’s location. That worked great, but doing so on a regular basis killed my battery life. But, with iOS 7’s advances in background location reporting, I knew there had to be a better way. I wanted something that would automatically track my location as precisely as possible, respect my phone’s battery life, keep that data private by default, yet still offer the ability to granularly share my location as I saw fit.

So I did what I always seem to do. I built my own app. It’s called Rockwell, and it’s available on GitHub.

Rockwell consists of two components. An iPhone app that monitors your location and allows you to annotate where you are using Foursquare’s database of named locations. And a PHP/MySQL web service you can install on your own server that the app talks to.

As you go about your day, the iPhone app uses iOS’ significant location change reporting feature to ping the web app with your location. The web app stores your location history and allows you to go back and search your history either by date or by location.

Further, since the website knows your most recent (current) location, you’re able to share that with others. In my opinion, one of the reasons Fire Eagle failed was it was (by design) very difficult to get location data out of the service. You had to go through an intricate OAuth dance each time.

With Rockwell, you simply choose the location level you’re comfortable sharing – either precise lat/lng coordinates, current city, current state, etc – and a format – plain text or JSON – and Rockwell generates a short url you can pass around. You can use that URL to embed your plain text location on your blog, or you can use the JSON version to do something more API-ish with it. There’s no OAuth shenanigans to deal with. You can have as many short geo-links as you want, and each one can be revoked at any time.

One more thing I’d like to explain. The iPhone app reports two types of check-in data to the web service. The first kind is dumb. Just your latitude, longitude, and timestamp. Many apps like Rove and Foursquare use this data to try and generate automatic location check-ins. Based on your past history, your friends’ location, and your location, they try and guess where you might actually be at a given time. Doing this well is the holy grail of location reporting. The problem is that I’ve yet to see any service get it right. In a dense urban area, with hundreds if not thousands of locations per square mile, there’s just no reliable way to figure out where you really are with precision. (At least not without some serious machine learning, which I assume Foursquare is working on.) Rockwell dances around this problem by allowing you to augment your dumb check-ins with annotated ones. Just launch the app, tap “Check-in”, and Rockwell pulls a list of nearby locations from Foursquare. Just tap on one and you’re done. It’s saved to the web service alongside the rest of your location history.

Rockwell is working great for me currently. All the basics work. The majority of the remaining work is around coming up with nice ways to show your location history in a useful way. The code is available on GitHub. I’d love it if you gave it a try, sent feedback, and maybe even a pull request or two.

In case you missed it, I’ve been working on a new Mac app for the past month or so. I spent the last few days polishing things and getting it into an MVP state – not quite as full featured as I’d like, but complete enough that I felt comfortable sharing with the world. So, yesterday evening I launched Minion.

What is Minion?

It’s a simple concept. Minion watches for events to happen on your Mac and then notifies you when they occur. Right now, those notifications go to your email or your phone via SMS or the Minion iOS app.

The initial idea for Minion came from my good friend Mike over at Divergent Media. Back in his video editing days, he’d spend hours waiting for export jobs to finish. I have a few friends who do animation for a living, and they confirmed that, yes, waiting for a render to complete is boring and can take hours. But with Minion, you can point the app at whatever job you’re waiting on and go someplace else. Minion will buzz your phone when the job finishes.

How does Minion know when the job is done? It watches for what I call “triggers”. Things such as whether or not a file exists, if a file has reached a certain size, or if a file’s size hasn’t changed in the last five minutes. Minion can also monitor the titles of your windows or the color of a pixel on screen. Does the app you’re watching throw up a progress bar? Point Minion at a pixel at the end of the bar, and when it fills in, Minion will notify you.

But this is just the start. My long term goal for Minion is to create a local IFTTT service for your Mac. Choose from a long list of triggers to watch, and then pick a task for Minion to carry out when that trigger fires. Put the two together and you’ve got recipes you can save, reuse, and even share with other power users.

This is just the beginning.

Yesterday, Daniel Jalkut tweeted

The only things better than shipping an app are the thankless months of hard work that go into making it halfway presentable. Yep, it’s fun. — Daniel Jalkut (@danielpunkass) April 4, 2014

That’s an apt way of describing the strange mix of joy and awe programmers feel when, after hours, days, maybe even weeks or months of work, the computer does what you tell it to do.

I’ve been working on my new app, Minion, for the last four weeks. And, today, I finally had my first successful end-to-end test run of the app. Everything on the client side worked beautifully and then successfully talked to the web service and delivered a notification to my phone. It’s a thrill to see everything come together. A high that I’m not sure I could achieve so frequently if I were in any other profession.

A few weeks ago, I started working on a new Mac app called Minion. It’s nothing too big or complicated – just a quick project that I hope will be useful to Mac power users. My goal was to build the app and the accompanying web service in under six weeks. With two weeks until my self-imposed deadline, I’m well on my way to completing it. The app is built. Now, it’s just a matter of finishing the web service and the marketing website.

One thing that’s giving me pause, however, is how to price the app. The web service, while not required, is an integral part of the app. The app is definitely more useful with it included. And with that in mind, there are three ways I could go about pricing the two components.

• Charge a base price for the app plus a nominal subscription fee for the web service that allows me to break even.
• Charge a base price for the app plus a more sustainable subscription fee for the web service that earns a profit.
• Make the app free, and just charge for the web service.

A fourth option you might wonder about is not charging for the web service at all. That’s something I briefly considered, as the servers it will be running on don’t really cost me that much. However, a core feature of the service is its ability to send text messages to your phone. If I only charged an up-front fee for the app, a heavy user of the web service could eat away the money they paid for the app as sending text messages cost real money. Three-quarters of a cent per message to be exact. A user who sent three messages a day, which is not out of the question, would cost me ten dollars a year. At that rate, they’d eat through the cost of the app within a year or two or three.

With that said, I definitely have to charge for the web service to some extent. The question becomes, do I do so with the intention of making a profit or just breaking even?

Right now I’m leaning towards the profit option. My other app, VirtualHostX, has an accompanying web service called Lift Off which I charge for. The main goal of Lift Off is to make VirtualHostX a more compelling product. However, recurring revenue, even a small amount, is nice to have. And Lift Off falls squarely into the small-but-nice-to-have range. Originally, Lift Off cost users ten dollars a month. But, after consolidating some web servers and finding a cheaper source of bandwidth, I was able to drop that price to only three bucks. And that’s my concern with pricing Minion’s web service. I can always lower the price to benefit users and encourage growth, but raising it after the fact is a much thornier issue.

A third pricing option would be to just charge a single subscription fee for the app in general. I like that idea, but after asking around and talking to friends, we all agree that a subscription-based desktop app is a hard pill for users to swallow. There just aren’t any successful examples to point to.

What I think I’ll ultimately do is sell the app for a fixed price, slightly higher than I might otherwise price it. But include a free year’s worth of service in the cost. That covers my financial bases and also forces all users to become familiar with the benefits of the web service – hopefully increasing my conversion rate when it comes time to renew subscriptions the next year.

That leads me to my last pricing question. What do I charge?

I remember my eighth grade algebra teacher introducing us to quadratic equations by drawing a parabola on the board. The y-axis charted total profit and the x-axis was the cost of the app. If you charge a small fee for your product, lots of users will buy it, but you won’t make much money. If you charge a lot for your product, you’ll make more per sale but have less sales overall. The trick is to find a happy medium when enough users buy your product at a high enough price as to maximize your profit.

Since releasing VirtualHostX in 2007, I’ve played that pricing game. Originally, the app sold for a paltry seven dollars. But over time as it became more popular and gained more features, I raised the price. I remember raising the price from $7 to $12, and then $14, and then finally after two years to $19. At that time I was completely floored that people were still buying the app and thought there was no way I could ever charge more. I had reached my limit. But, here we are, seven years later and VirtualHostX is still making money at $49. Have I found that magic maximum point on the y-axis? Maybe. Take a look at the chart below.

On that chart, the blue bars show the number of new customers I gained each year. The red line is my annual revenue. As you can see, new users and revenue went up, together, every year until 2013. In 2013 I raised the price of VirtualHostX from $34 to $49. You can see that my number of new users went down, yet revenue continued to increase. That signals to me that I’ve found a happy price point. (That said, I’ve forgotten most of my statistics and have no marketing training, so it’s totally possible I’m reading this the wrong way. If you’re a professional at this, feel free to correct me.)

My challenge with pricing Minion is that I’m entering an empty market. I’ve searched around and haven’t found any other app that does what Minion does, so I have no competition to price against. My only frame of reference is my intuition and the general price point of other Mac desktop apps in the “utility / pro user” category. My gut says that should land me in the $19 – $24 range. Add to that the cost of the web service – $10 – $20 a year – along with a one-time price break, and I’m thinking I’ll price minion at $29, with a year of the web service included.

Anyway, those are my thoughts. I wanted to write them down for my own benefit so I could concretely walk through them. And maybe some of you out there have wondered what goes into pricing an app.