Hello everyone,
I am new to iOS development and have recently been assigned the task of completing an iOS application started last year by a coworker. The application is designed to be a handbook for medical facilities and will contain approximately 70 pages of text from a pdf when completed.
In the current implementation, the content of each page of the pdf is stored inside a variable, and loaded inside a seperate view once a specific page is selected from the menu. Continuing with this implementation would probably lead to approximately 70+ views, and an application filled with static content.
My question is whether this implementation would be rejected by the App Store due to the implementation, or whether this is a natural approach towards implementing book related apps.
(Additional irrelevent question. Is there a specific location where I should be asking about design questions? I do not want to restart building the application, but would prefer it to be build correctly)
Any help is appreciated!
If it smells like a book, walks, talks, acts like a book, there is a risk that review will push back* with the suggestion that you should publish it as a book, e or i book, actually. Based on your description, I'd tend to agree.
Is there some reason you want an app instead of an e/ibook?
*ASRGs
Your app should include features, content, and UI that elevate it beyond a repackaged website. If your app is not particularly useful, unique, or “app-like,” it doesn’t belong on the App Store. If your App doesn’t provide some sort of lasting entertainment value, it may not be accepted. Apps that are simply a song or movie should be submitted to the iTunes Store. Apps that are simply a book or game guide should be submitted to the Apple Books Store.
