Core Concepts

Terminology

App Identity. A globally unique identifier that is assigned when an app is created. Typically this identifier is in a reverse domain format (io.falkor.appname for example). This identifier is created on the platform and is used to register with destinations such as Firebase, App Store and Google Play.

Destination. Means a location in which an app can be distributed. Currently app manager integrates with Firebase for web apps, Google Play for Android apps and App Store for iOS apps.

Blueprint. Is a dynamic app template which is used in the build process along with an build instruction to create apps. Blueprints determine what features, theme, settings and options are available for an app. An app created with a blueprint cannot change it's blueprint but can upgrade with new blueprint versions.

Flavour. Is a configuration of a blueprint that enables / disables preset features in an app. A flavour can alter the app in such a way that it can appear to be different from other flavours. For example the Falkor blueprint comes with 4 flavours: Streams (Podcast app), Pathway, Standard Learning, Stories Only. Each of these blueprints shape the app by configuring features.

Rate Per Month (PRM). Is the rate of app and account creation and is the primary performance indicator on a platform. For example if you sell 10 apps and 10 accounts in 1 year your RPM will be 2. You can view your RPM in coverage under Launch Pad.

Deployment Process

Creating and deploying an app is Fast and efficient.

Versioning

App versions are in the format of major, minor and build number (2.9.10 for example). The versioning is predetermined by several factors. Knowing how this is determined is useful in understanding what blueprint, patch or iteration has been applied to an app.

Major. The first number in a version string determines a major revision / release to a blueprint. Changes to the major number denotes a milestone release or refactor of a blueprint.

Minor. The second number in a version determines the patch / minor feature release to a blueprint. Changes to the minor number denotes bug fixes, patches or additional minor features.

Build Number. The third number in a version denotes the number of builds created with the blueprint version.

An Example

An app is built using the Falkor 2.9 blueprint, the full version of the new app is 2.9.1. Using the definitions above, this means: The app has been built once using the second major release, with the ninth minor revision of the Falkor blueprint.

If the app is deployed again the version will change to 2.9.2. Meaning the app has been built and deployed twice with the same blueprint version.

If 3.0 version of the Falkor blueprint is released and the same app is built, the version will change to 3.0.1. This means it is the first build of the blueprint version 3.0.

Do I need to know this?

Versioning is very much automatic and not something you need to be too concerned about. Where this is useful is that the major and minor numbers will correspond to release notes. This will allow you to lookup changes and revisions to a blueprint. The build number is useful to cross reference with destinations to ensure that the deployed build is the latest one.

Destinations

A destination is a generic term for where an type of app can be deployed. When creating a deploying an app, you will be able to choose to deploy to Firebase for web apps, Google Play for android apps and App Store for iOS apps.

With app manager you are able to create multiple destinations for the various types. For example you may have several App Store destinations for customers that want to self publish and for your own App Store account.

Destinations