Standalone Mobile App – Requirements

Modified on Wed, 11 Nov at 3:26 PM

This document outlines the information, branding assets, developer accounts, and technical prerequisites required to create and publish an institution-specific Standalone Mobile App integrated with Fedena.


Unlike the Fedena Group Mobile App, a Standalone Mobile App is developed and published under the institution's approved application name and branding.


1. Application Name

Provide the preferred name of the institution's mobile application.

  • This name will be displayed on the Google Play Store and Apple App Store.

  • The name should represent the institution and be approved before the app build begins.

  • Ensure the name complies with the respective app store naming policies.

Example:

  • Institution Name:  International School

  • Application Name: International School

2. Institution Logo and Application Icon

Provide a high-quality version of the institution's logo.

  • The logo will be used as the mobile application's icon.

  • Please share a high-resolution image with a transparent background, preferably in PNG format.

  • The image will be resized to meet Android and iOS application icon requirements.

Example: International School logo.

3. Application Cover Image and Branding

Provide the institution's preferred cover image and branding assets.

  • The cover image should represent the institution.

  • Share high-resolution images without watermarks.

  • Branding elements such as colours, banners, and other visual assets should be approved by the institution.

Example:

  • Primary Colour: Navy Blue (#123456)

  • Secondary Colour: Gold (#D4AF37)

  • Cover Image: Institution campus photograph.

Final branding options will be subject to the supported application design.

4. Theme Colours

Provide the preferred theme colours for the application.

  • Primary Theme Colour:

  • Secondary Theme Colour:

  • HEX Colour Codes:

Example:

ThemeColourHEX Code
PrimaryNavy Blue#123456
SecondaryGold#D4AF37

5. Custom Pages and Institution Content

Provide the content for the pages that should be displayed in the application.

Suggested pages:

  1. About Our Institution

  2. Chairman's Vision

  3. Principal's Message

  4. Vision and Mission

6. Company / Institution Website Details

Provide the following details:

  • Institution Logo

  • Institution Name

  • Official Website URL

  • Contact Information

7. Short Application Description

Provide a short description of the application for the Google Play Store and Apple App Store, as applicable.

8. Long Application Description

Provide the detailed description of the mobile application for the respective app store listings.

9. Fedena Instance URL

Provide the complete URL of the institution's active Fedena instance.

The Standalone Mobile App will connect to this Fedena instance to retrieve the relevant information and provide the configured mobile application features.

Example:

https://internationalschool.fedena.com

Please ensure that the instance is accessible and the required connectivity is available.

10. Institution Privacy Policy

Provide the official privacy policy URL of the institution.

  • The privacy policy should explain how user information is collected, processed, stored, and protected.

  • The URL should be publicly accessible.

  • The policy must comply with the applicable Google Play and Apple App Store requirements.

Example:

https://www.example.com/privacy-policy

11. Apple Developer Account

An Apple Developer account is required if the institution intends to publish its standalone iOS application under its own developer account.

General requirements for organizational enrollment:

  • Legal entity verification.

  • D-U-N-S Number for most organizations.

  • Official work email address associated with the organization.

  • Public organizational website.

  • Authorized representative with legal authority to accept Apple's agreements.

Program Fee: USD 99 per year, subject to regional pricing and eligibility for fee waivers.

Official reference:
https://developer.apple.com/help/account/membership/program-enrollment

12. Google Play Developer Account

A Google Play Developer account is required to publish the institution's standalone Android application under its own developer account.

General requirements:

  • Developer account registration.

  • Identity and account verification.

  • Required organizational information and supporting documents, where applicable.

Registration Fee: USD 25 (one-time registration fee).

Official reference:
https://support.google.com/googleplay/android-developer/search?q=to+create+the+account

13. Firebase Configuration – Push Notifications

If push notifications are required, the necessary notification configuration must be completed.

  • Confirm whether push notifications are required.

  • The technical team will confirm the Firebase configuration and access requirements.

  • Any required project configuration or permissions should be provided through an approved secure access method.

Important: Do not share Firebase account passwords or personal login credentials through email.

14. OTP Login – SMS Gateway/API Configuration (Optional)

If the institution requires OTP-based login, an active and supported SMS gateway/API is required.

Please coordinate with your SMS service provider to obtain the required API documentation and configuration details.

  • SMS Provider Name:

  • API Documentation:

  • Sender ID, if applicable:

  • OTP Login Required: Yes / No

OTP login can be excluded from the initial scope if it is not currently required, subject to the supported configuration.

15. Test Student and Employee Accounts

Provide sample student and employee accounts for application testing.

  • Student test account should be available in the Fedena instance.

  • Employee test account should be available in the Fedena instance.

  • The accounts should have the required access permissions.

  • Test access must be coordinated securely with the Fedena team.

Important: Do not send actual passwords or sensitive login credentials through email. Use an approved secure method for sharing test access.

16. Grievance Cell Contact Details

Provide the institution's grievance cell contact information, if it is to be displayed in the application.

  • Contact Person's Name:

  • Email Address:

  • Contact Number:

Example:

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article