I’m excited to announce the 1.0 release of Yearly for iPhone, my first iOS app to see the light of day past my own hard drive. From its description page:

Yearly lets you systematically read your Bible in a year, with daily readings from both the Old Testament and the New Testament. It’s an incredibly simple app with just one screen, showing your reading for the current day as well as for the previous and next days.

Yearly also sends a notification every morning at 5:00 AM so you can know right from your lock screen what your reading is for the day.

I spent about 12.5 hours on the initial version. It’s all written in Swift and StoryBoard. The ecosystem of native iOS development is a pure joy, more so than any other platform or set of tools I’ve worked with. It has always felt this way, ever since I began dabbling in iOS development in 2013.1

From the perspective of someone who’s never submitted an app before, I’m impressed with how fast the iTunes Store approved Yearly. I submitted it on the morning of 28th, the first day the store opened after being closed for the holidays, and it was approved midday on the 29th.2 Apple isn’t joking when it says, “On average, 50% of apps are reviewed in 24 hours and over 90% are reviewed in 48 hours.” This held true even with whatever backlog accrued over the holiday.

I’m already planning on the interative improvements I want to make in the coming weeks, including the ability to choose different color schemes and reading schedules.

Systematically reading the whole word of God is as important and relevant as ever. It’s impossible to know what 2018 holds but I do know this: having a schedule to read through the Bible is going to make it easier to get through. There’s no news feed, no blog, no other set of books, that can serve as a substitute or take precedence over the Bible.


  1. It’s not a stretch to say that for every 1 hour I’ve spent coding in iOS the past four years, I’ve spent 200+ hours coding for the web. Maybe one day that will change. ↩︎
  2. We have Phil Schiller to thank for that kind of turnaround. Thank you, Phil. ↩︎