What are the requirements for an insurance app to pass the review ?

Hello!

I work as mobile developer in a legal company that produces insurance softwares.

We're now working on a mobile app that works with some other websites and systems, its objective is to let our customers have easy access to their personal information, check amounts, do payments and more.. Our app is close to the following existing apps:

  1. Aetna Health app
  2. Oscar Health

We'd like to know what we should do in addition to development and tests. Based on Apple store review guidelines, we understand that we must add anything related to modeling, functional spec and demos.

I'd like to know if we must provide our modeling docs, like some diagrams or details about main use cases, actors (including external systems), sequences? or its unnecessary?

FYI: Our app is built with a cross-platform technology known as Expo and React Native (You can look on Google if this new to you), and its intended to work on iOS and Android both. We consider OS as a modeling entity and we have some customizations based on each OS.

I feel confused, and really need help before we proceed to review test. Please help.

Thanks in advance!

App Store Review Guidelines state:

3.2.1: (v) Insurance apps must be free, in legal compliance in the regions distributed, and cannot use in-app purchase.

There are apparently no other requirements.

.

we understand that we must add anything related to modeling, functional spec and demos.

No such thing in the guidelines. What modelling do you have in mind ?

.

'd like to know if we must provide our modeling docs, like some diagrams or details about main use cases, actors (including external systems), sequences? or its unnecessary?

That's not required or even useful for the review.

NOTE: if that does not answer your question, please explain what is obscure. If it does, please close the thread by marking the correct answer (tap on the checkmark in circle on the left of the answer).

Hi @Claude31! You said:

No such thing in the guidelines.

I think you're wrong. The guidelines says:

Don’t include any hidden, dormant, or undocumented features in your app; your app’s functionality should be clear to end users and App Review. All new features, functionality, and product changes must be described with specificity in the Notes for Review section of App Store Connect (generic descriptions will be rejected).

Also:

 If your business model isn’t obvious, make sure to explain in its metadata and App Review notes. If we can’t understand how your app works or your in-app purchases aren’t immediately obvious, it will delay your review and may trigger a rejection

What are the requirements for an insurance app to pass the review ?
 
 
Q