Skip to main content

How long does it take to develop an iOS app?

In the last few years, I have gotten pretty all right at developing for iOS, it’s a jump from being a web and BI developer for the 6+ years before that. Recently, I tried to see if I can think of an app concept, document it, start working on it and submit it to the app store for review in a day? Well…as I discovered, I cannot, it takes me close to 2 days or 3 working days to do so. This is my timesheet for that entire process,
  • 5:00am: Think about the problem the app solves and write a blogpost
  • 7:00am: Think of the app UI concept
  • 9:30am: Start learning those unknown iOS API
  • 1:00pm: After lunch start coding the app in question
  • 9:00pm: After having a gym and dinner break, stop working on the nearly complete app.
Next day
  • 6:00am: Finish the app i.e. from nearly complete to complete
  • 8:00am: Think of the app icon design concept
  • 9:00am: Make the app icon
  • 1:00pm: Do a final round of testing
  • 2:00pm: Think of and write the app store description and keywords
  • 4:00pm: Upload and submit the app to the app store for review
  • A a day later: App approved and released!!!
The blogpost that I wrote between 5 to 7am is The Numbers Game: Requirements. FYI, there’s also an Android version of this app but that was built separately i.e. that’s a Hybrid app built using Ionic Framework. If you wanted to try a version, I would recommend try the iOS version, in its current state, it’s a bit more optimised than the Android version.
As usual, if you find any of my posts useful support us by  buying or even trying one of our apps and leave us a review on the app store.
Or why don’t you try Numbers Game for iOS or Android (btw, the Android app was developed separately than this)
Numbers Game: Calculate Faster
Numbers Game: Calculation Master

Comments

Popular posts from this blog

Upload to AWS S3 from Java API

In this post, you will see code samples for how to upload a file to AWS S3 bucket from a Java Spring Boot app. The code you will see here is from one of my open-source repositories on Github, called document-sharing. Problem Let’s say you are building a document sharing app where you allow your users to upload the file to a public cloud solution. Now, let’s say you are building the API for your app with Spring Boot and you are using AWS S3 as your public cloud solution. How would you do that? This blog post contains the code that can help you achieve that. Read more below,  Upload to AWS S3 bucket from Java Spring Boot app - My Day To-Do (mydaytodo.com)

Addressing app review rejections for auto-renewing subscription in-app purchase (iOS)

The ability to know what the weather is like while planning your day is a feature of  My Day To-Do  Pro and as of the last update it’s also a part of the  Lite version . Unlike the Pro version it’s an auto-renewing subscription based  in-app purchase (IAP)  in the Lite version. What means is that when a user purchases it, the user only pays for the subscription duration after which the user will be automatically charged for the next period. Adding an  auto-renewing  subscription based IAP proved to be somewhat challenging in terms of the app store review i.e. the app update was rejected by the App Review team thrice because of missing information about the IAP. Therefore in this post I will share my experiences and knowledge of adding auto-renewing IAP in hopes to save someone else the time that I had to spend on this problem. In-App purchase This year I started adding IAPs to My Day To-Do Lite which lead to learning about different types of IAP...

Ionic app with a Django backend: Part 2 - The Ionic app

In this post, I will continue from where we left in Part 1 of this series.  In part 2, I will talk more about the front-end side of things. Ahh, I have a background in web development, hence I call this front-end, but that's not the most accurate thing to say in these modern times. So the right way to say this is, I will talk about the Ionic app in this Github repository(IonicAppWithRestBackend) in more details in this post. So what did we do in part 1? In part 1, we got to the point of running our backend on the web server that ships with Django . To refresh your memory, this is how we got the backend server running, Clone the repo git clone https://github.com/cptdanko/IonicAppWithRestBackend Navigate to the backend project directory cd IonicAppWithRestBackend/backend/python_django/restBackend/ Note: if you are using Windows, you may want to change "/" to "\" in the above command. Once there you can run the backend server with the follow...