Platform components
A breakdown of the pieces involved in a Reskyt app and who is responsible for each one.
Mobile apps
Section titled “Mobile apps”The native containers for iOS (Swift) and Android (Kotlin). They render your store in a WebView and provide the native capabilities: push, biometrics, deep links, system permissions and the system modals such as the update modal.
They are distributed as binaries on the App Store and Google Play. Any change in this layer requires rebuilding and republishing.
Minimum operating system versions
Section titled “Minimum operating system versions”| System | Minimum version |
|---|---|
| Android | Android 9 (Pie) or later |
| iOS | iOS 16 or later |
iOS 16 runs on iPhone 8, iPhone X and all later models. The iPhone 7 and earlier models are left out.
These are the current minimum versions and they may change over time. Reskyt updates the app continuously, for several reasons:
- Store requirements. Apple and Google regularly require building with recent versions of their tools and systems in order to publish and update apps.
- Customer requests. New features or integrations, such as third-party SDKs, may need more recent system versions.
- Technology and security. Improvements in security, performance and platform capabilities tend to leave older versions behind.
As new system versions are released, Reskyt may stop supporting the oldest ones. Users whose device is left out can keep using the version of the app they have installed, but they do not receive new updates.
Reskyt platform
Section titled “Reskyt platform”The set of services Reskyt operates: the configuration of each app, the building of binaries, the notification service and the integrations.
It is multi-tenant: the container and the modules are shared, and each app’s configuration, content and credentials are its own.
Backoffice
Section titled “Backoffice”The panel where the app is configured: parameters, modules, notifications, appearance and publishing.
Push notifications
Section titled “Push notifications”Sending and segmentation infrastructure, available from the backoffice and from the push API. The target unit is the device token, not the user: see users, devices and tokens.
Content and configuration
Section titled “Content and configuration”What defines an app’s behavior without touching the binary: parameters, visual identity, modal texts, your own code in the app’s JS and CSS layers, and system pages.
This layer is the reason most changes do not require republishing.
Integrations
Section titled “Integrations”Third-party services connected through modules: analytics, marketing, payments, identity, tracking, device utilities and content. Each module states which credentials it needs and whether it requires republishing.
The push notification API is the public API currently available. For code running inside the app, the available variables.