Frequently asked questions
Short answers. Each one links to the page that covers it in full.
Product
Section titled “Product”Does Reskyt replace my ecommerce?
Section titled “Does Reskyt replace my ecommerce?”No. The app displays your store: catalogue, prices, cart, checkout and accounts stay on your platform and are not duplicated. Reskyt adds the native layer and the presence in the stores. See Reskyt and your ecommerce.
Is the app native?
Section titled “Is the app native?”The container is native (Swift on iOS, Kotlin on Android) and provides push, biometrics, deep links, system permissions and a store listing. Store content is served from your website inside a WebView. See how Reskyt works.
Can we add custom features?
Section titled “Can we add custom features?”Part of the customisation is handled without touching the binary, from the app configuration and its own code layers. Anything that requires native capabilities is handled with modules, and that means recompiling and republishing. See what a module is.
Is the app mine?
Section titled “Is the app mine?”Yes. The App Store and Google Play accounts are owned by the customer, and the listing, the reviews, the metrics and the assets associated with those accounts belong to them. See store accounts.
Do I have to republish every time I change something?
Section titled “Do I have to republish every time I change something?”Not in most cases. Changes in your store are visible immediately. You do have to republish when you enable an SDK-type module or integrate a new provider.
Integrations
Section titled “Integrations”Can you integrate our provider?
Section titled “Can you integrate our provider?”It depends on which route it needs: web, API or native SDK. Many SDK requests are solved over web or API, with no release cycle. See integrations and SDKs.
Can you integrate our SDK?
Section titled “Can you integrate our SDK?”It requires a prior technical evaluation: no SDK is automatically compatible. We have to confirm that there is a library for iOS and Android, what permissions it asks for, what data it collects and whether it needs a bridge with the WebView. The list of what we need in order to evaluate it is in integrations and SDKs.
Can we keep our own login system?
Section titled “Can we keep our own login system?”Yes. In the usual Reskyt model, the identity system and the login are still those of the customer’s ecommerce. Additional capabilities (social login, SSO or OAuth, biometrics) can be integrated when they are part of the scope of the project. See authentication and sessions.
Can we keep our analytics and marketing tools?
Section titled “Can we keep our analytics and marketing tools?”Web-based integrations can keep working inside the WebView when they are compatible with that environment. When specifically native capabilities are needed, an additional integration through an SDK or native development may be required: see the module catalogue.
Push notifications
Section titled “Push notifications”Why are tokens not the same as active users?
Section titled “Why are tokens not the same as active users?”Because one person can have several devices, because a token only exists if the user accepted notifications, and because a token can outlive actual use of the app. The base degrades through uninstalls, device changes, reinstalls and lost permissions. See users, devices and tokens.
Can the same user have several devices?
Section titled “Can the same user have several devices?”Yes, and each one is a different token. If you segment by token without deduplicating by person, that person receives the campaign several times.
Can I send push from my CRM?
Section titled “Can I send push from my CRM?”Yes, with the push API, authenticating with the
x-api-key header.
Why is a user not receiving notifications?
Section titled “Why is a user not receiving notifications?”The most common reasons are that they did not accept the permission, or that they uninstalled and reinstalled the app, which generates a new token. The full diagnosis is in push troubleshooting.
Infrastructure
Section titled “Infrastructure”Where does Reskyt run?
Section titled “Where does Reskyt run?”On AWS, with the main region in eu-west-1 (Ireland), with redundancy across Availability Zones. See architecture.
How is security managed?
Section titled “How is security managed?”The detailed documentation is delivered under NDA. What it covers and how to request it is in architecture.
How are backups and availability managed?
Section titled “How are backups and availability managed?”Reskyt performs backups and operates with redundancy across Availability Zones. See continuity and recovery. The specific availability commitments depend on the applicable contract.
What happens in the event of a platform incident?
Section titled “What happens in the event of a platform incident?”The specific impact depends on the affected component. The architecture uses caching, CDN and decoupling between components to improve the resilience of the service. See reliability and scalability.
Stores
Section titled “Stores”Who publishes the app?
Section titled “Who publishes the app?”Reskyt builds and submits the binary, and handles the technical side of the review. See publishing to the stores.
How are updates managed?
Section titled “How are updates managed?”Every version goes through store review. When publishing, you have to update the version numbers in the update modal, or older users will not see the notice.
Support
Section titled “Support”How do I open an issue?
Section titled “How do I open an issue?”By writing to support@reskyt.com. See support.
What information do I have to provide?
Section titled “What information do I have to provide?”App and environment, what you expected and what happened, when it started, who it affects, steps to reproduce it and the full error. The list is in support.