Feature and Functionality Comparison

1

Application Name (Play Store / App Store)

Published under the common Fedena Mobile App name.

Published under the institution's approved application name.

2

Application Logo

Institution branding is displayed within the app, subject to supported configuration.

Institution's logo is used as the application icon and branding.

3

Cover Image and Branding

Institution branding is displayed after users select their institution and access the app.

Institution branding is visible from the application launch experience.

4

Institution Name

Users need to search for and select their institution within the app.

Users can directly access the institution-specific application.

5

Look and Feel

Uses a common Fedena application interface with institution-specific information and branding.

Provides institution-specific branding and application identity.

6

Application Availability

Users download one common application that supports multiple institutions.

Users download the application developed specifically for their institution.

7

Application Generation

Uses the existing Fedena application infrastructure.

Requires a separate institution-specific app build and configuration.

8

Deployment Time

Generally quicker, as separate institution-specific store publication is not required.

Depends on branding, configuration, developer account verification, app build, and store review.

9

Application Updates

Common application updates are managed centrally by the application provider.

Institution-specific builds and store submissions may be required for updates.

10

Android and iOS Availability

Available through the common application listing, subject to platform availability.

Requires publication and approval of the institution-specific application on the respective app stores.