After 2 weeks of trial and error, I found out some fun facts for app submission to different app stores.. so...here you go :p
For App Store:
Reject reason: Testing Instructions
Prior to submitting this app, I have past exprience on how to submit iOS app in iTunes Connect. I thought it will be really smooth but guess what..I forgot to include the Testing Instructions and my app was rejected 😣
For Google Play Store:
Reject Reason: Your app's short description mentioned other brand
Example: I used "A mini game similar to Minesweeper" in my description and my app was rejected T___T But why there's so many Minesweeper game on Google Play Store? Anyways, inside the app I still put Minesweeper word but Google didnt found out because that was just a bot who rejected my app 😛
For Mac App Store:
Reject reason: We have found that when the user closes the main application window there is no menu item to re-open it.
- If your electron app is Single Window app, you have to Kill the app when "X" button is clicked (not minimize 😮) else it will be rejected and the reason for rejection will be as above. How would I know it is related to menu bar 🤔 ofcourse stack overflow taught me.. 😌
For Microsoft Store:
Reject Reason: The app promotes acquiring software through methods other than the Store
Since the electron version is built after RN.. That's why I have included a link to download on App Store and Google Play in "About" screen. But got rejected. T__T
---
Anyways, besides all these lessons learnt, I also found out that in order to ship an app, that is - from development to production.. it takes a lot more than just coding itself.
I often find myself spending time on
- Designing logo (Something that's totally alien to developer)
- Generating correct logo size & shape (especially the rounded logo on iOS 🤔)
- Reading documentation back and forth on configuration for N times (even the page present the same text)
- Endless trial-and-error to build and sign the app (cert and provisioning issue especially you are not using xcode 😏)
- Submitting multiple builds and still failing (For Microsoft store)
- Writing a proper ReadMe.md 😛 (With credits and demo)
- Generating privacy policy..
- Regenerating screenshots for all platform after you have made changes to the user interface 😮
- and etc.
Coding time itself I would say: just 2 days? 🤔 out of the total of 13 days 🤐
---
Why on earth would I take the suffering path? 😌
After going through the app-submission experience, it is clear that releasing an application involves much more than writing the core functionality. Each store can have different requirements, and small details such as testing instructions, descriptions, application behavior, and external links can affect whether a build is accepted. The trial-and-error process described here is a useful reminder that deployment and distribution need to be considered alongside development.
ReplyDeleteThe experience also shows how much JavaScript-based application development can extend beyond coding itself. Developers may need to handle packaging, configuration, signing, documentation, and platform-specific requirements before an application is ready for users. JavaScript Course in Chennai can help strengthen the programming foundation needed before dealing with these broader application-development tasks.
The examples from the App Store, Google Play Store, Mac App Store, and Microsoft Store demonstrate that every platform can introduce its own review expectations. Issues such as testing instructions, references to other brands, window behavior, and links to other stores may require changes even when the application itself works correctly. Understanding these requirements early can reduce repeated builds and unnecessary submission failures. JavaScript Training in Chennai is another relevant way to build JavaScript skills that can support application development work.
ReplyDelete