Skip to main content

First mobile(iOS) app submitted to the app store for review

I finally reached this milestone, I submitted my first iOS app for review to the Apple app store, polishing the app and doing some last minute testing and all kept me very vey busy for the last two weekends. I have been working on this app for over a year now and the following posts,
  1. Building my first mobile app: The journey so far - Part 1: The background
  2. Building my first mobile app: The journey so far - Part 2: App inception
  3. Building my first mobile app: The journey so far - Part 3: App released
tell the story of how a major life event(tragedy) lead me to begin working on this app.

Why reject the first accepted build?

Two weeks ago on a Sunday evening, I had submitted my first build for review and I managed to get a response in 7 days and that build was approved to be released to the app store. So why didn't I? well after I submitted the build for review, I managed to find 2 very small bugs, to do with the initial state of the app, so those bugs could only be spotted when you do a fresh install and perform certain specific actions. The bug fixes were really small, but the fact that I saw the bugs, I simple couldn't release it without fixing them. In either case the review process did help me with one thing i.e. I wanted to see if there is anything obviously wrong with my build to prevent it from being released on the app store. So turns out there isn't, so on getting the feedback from Apple, I just had the build "developer rejected" and submitted a new build for review.

So what did I learn from this experience?

Like, I said in one of my previous posts, HAVE A TEST PLAN BEFORE STARTING DEVELOPMENT. Really, I cannot stress this enough, having a test plan before starting development can be so very helpful, especially if development stretches over a substantial period of time and new features are added during development. At least having a test plan, if not automated tests, would be very helpful when the app is closer to being released.

What's next?

I need to build a website for the app with a good landing page and all, so that is one of the things, that I will be focusing in the coming days.
Labels:

Comments

Post a Comment

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)
Post a Comment
Read more

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...
1 comment
Read more

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...
Post a Comment
Read more