Criteria | Fedena Group Mobile App | Standalone Mobile App |
|---|---|---|
Application Build | Existing common application build is used. | A separate application build is prepared. |
Play Store Submission | Institution does not need to submit a separate application. | Institution-specific application must be submitted to Google Play. |
Apple App Store Submission | Institution does not need to submit a separate application. | Institution-specific application must be submitted to the Apple App Store. |
Store Review | The common app publisher manages application submissions and updates. | Each new app submission or applicable update is subject to store review. |
App Updates | Common updates are distributed through the existing application listing. | Updates are released through the institution-specific store listing. |
Go-Live | Depends on institution configuration and readiness. | Depends on build completion, developer account verification, and store approval. |
Maintenance | Common app maintenance is managed centrally. | Institution-specific publishing and maintenance responsibilities must be agreed upon. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article