Reskyt and your ecommerce

Reskyt does not replace the ecommerce: it integrates with it and depends on it.

Your store remains the source of truth. The app shows it, adds native capabilities to it, and gives it presence in the stores.

Split of responsibilities

Area	Depends on your ecommerce	Depends on Reskyt
Catalog, prices and stock	Yes	No
Cart and checkout	Yes	No
User accounts and login	Yes	The native capabilities integrated on top of it (biometrics, social login)
Content and translations	Yes	The app-specific configuration
Payment gateway	Yes	The modules that make its flow work inside the app
Push notifications	No	Yes
Deep links and Universal/App Links	Configuration on your domain	Behavior inside the app
Publishing and updates	Store accounts, yours	Build, submission and maintenance

What this means in practice

Perceived performance is largely your website’s performance. If a product page is slow in the mobile browser, it will be similarly slow in the app. Optimizing the store is optimizing the app.

Your store’s availability determines the app’s. The app shows your ecommerce; if your store does not respond, the content does not appear.

Store changes arrive without republishing. What you publish on the web is in the app immediately.

Changes on the web can affect the app. A change to the theme, the selectors or the login flow can affect app features that rely on them, such as biometric login when it is integrated. Redesigns should be communicated in advance.