I have just released an update to my very first commercial app, Calendar Paste. It’s now v3.3.0 and sports iOS 13 compatibility, Dark Mode, and overall better layout. So it’s mostly a cosmetic and “minor tweaks” update.
Calendar Paste 1 was introduced back in late 2012. That’s 7 years ago! So, happy birthday, Calendar Paste!
To celebrate, Calendar Paste 3 will be available for free from Oct 1st until Oct 6th, and then 50% off until the end of October. The App Store listing doesn’t seem to be updated despite it being “Ready for Sale”, for whatever reason, though. Maybe it’s already fixed when you read this. v3.2 will work just fine, but not sport Dark Mode, yet.
The app was my first real app project, sufficiently simple to start with, yet interesting enough to be sold on the store.
Calendar Paste 1 kicked off my indie app developer business. I still don’t make a lot of money and have to freelance to stay afloat, but this is a very cool path to have taken. I’m loving it. In case you wonder: it never was a huge commercial success. For 7 years, it brought in something between $3 and $130 per month, with a guesstimated average of $18.53/month. Unless it didn’t sell at all, that is. So much for the dreams of yours truly in 2012 to get rich quickly, right? But I learned to code in Objective-C, use Core Data, program for iOS 5 (and then iOS 6 before the app was finished). That’s worth a lot.
That’s why I don’t sunset Calendar Paste, even though each year’s iOS update takes away time for maintenance. And I cannot warrant to add all the planned features to the app because the time is better spent on other, larger projects.
I also wrote a diary of the progress, taking extensive notes in a tutorial-like fashion, that I eventually wanted to publish as a $5 ebook – but I never did. It just didn’t seem to be worth the trouble, and shortly after most of the code was already outdated, and the lessons learned not easily applicable to Swift.
Sorry if you’re still waiting for iCloud sync. It’s theroetically possible, but would take about a week or two to implement and test, and that’s just too costly at the moment. One day I’d like to out-source development of features like this, but to do that I’d need to accumulate larger savings – so either me or someone else working on the app depends on the same solution and y’all have to hold out a bit longer.
Receive new posts via email.