Day One is evolving. We’re transitioning to a more stable subscription business model to ensure this app and these services always stick around.
This week we’re releasing the Day One Premium subscription service. It includes the ability to create more than ten journals and access all future premium features.
Day One has been on my iPhone’s home screen for years. It’s a fantastic journaling app for iOS and macOS. Version 2 was a paid upgrade, bringing a new design to the app, as well as a revamped sync service.
Unfortunately, this service only added end-to-end encryption in the past few weeks. Some features, like publishing a journal entry to the web for public sharing haven’t resurfaced after the change.
The subscription model has been named Day One Premium. Here’s a bit from the company’s FAQ:
What’s included in Day One Premium?
Unlimited journals, unlimited photo storage, 25% off book orders, the Mac app ($49.99 value), and more. Day One Premium users also have exclusive access to all future features including: audio recording, writing prompts, video entries, and more.
In short, if you want new features in the future, you’ll need to move over to the subscription. That will run you $49.99/year, but first-time buyers can get it at 30 percent off, coming in at $34.99/year.
If you’re like me and bought the 2.0 apps, the first year is even cheaper, at $24.99/year.
Without Premium, the Day One apps will be pretty limited. According to the FAQ, those accounts “are limited to one photo per entry, one journal, no cloud services, and no access to other Premium features.”
When Apple announced app subscriptions, Day One came to mind. It’s an app I use very often, and one that I want to see enjoying on-going development. I hope that this allows the company to continue adding features to an app that I genuinely enjoy.
I’m willing to give Day One Premium a shot, but my guess is that not everyone will be. I expect to see features like web publishing and online editing sooner rather than later. 2.0’s launch was a little rough with syncing issues and the aforementioned lack of end-to-end encryption. Any developer who moves to this model needs to prove to their users that the on-going investment is worth it.