Push notifications
Send to everyone, a segment or one customer, from the dashboard or the API. Permission is asked when you choose, not at first open.
How it works · Apps
The project you build in the editor becomes an iOS and an Android app. We package it, submit it to the stores under your name and push updates after launch. Here is the path, and where the stores set the rules.
Preview of the Northlight store app on a phone: a search field, a seasonal banner, category filters, a grid of bestsellers with photos and prices, and a native tab bar.
Northlight
v1.4.2 · build 87
From editor to store
You control the first three and the last one. Review and release timing belong to Apple and Google.
Review times are set by the stores and vary. Other timings are placeholders.
Minutes to hours
Your app is the same project as your website: same pages, products and checkout, laid out for a phone. Native pieces such as the tab bar, the push permission prompt and the app icon are settings, not code.
You seeDraft
Instant
Scan a code and the draft opens in the SparkIO preview app on your own phone, live, as you edit. Run checkout with test cards before anything is submitted.
You seePreview
≈ 10 minutes to package
When you press Submit we build the iOS and Android binaries, sign them with certificates we manage for you and upload them to your App Store Connect and Google Play accounts, with the listing, screenshots and privacy answers you filled in. The accounts are yours and the app is published under your name.
You seeSubmitted
Usually days, set by the stores
Apple and Google review every new app and most updates against their guidelines. We prepare the submission to avoid the common rejections, but the decision and the timing are theirs. If a reviewer asks for changes, the note appears in your dashboard.
You seeIn review
On approval, or on your date
Once approved, the app goes live immediately or on the release date you chose. The store links appear in your dashboard, and the install buttons on your website start pointing to them.
You seeLive
Minutes, no store review
Changes to pages, products, prices and layout reach installed apps the next time they open, without a new store submission. Changes to native capabilities, such as a new permission or a new SDK, are a new binary and go through the stores again.
You seeUpdate rolled out
In-app checkout
Physical goods and services sold in your app use SparkIO checkout, exactly as on the web. Digital goods and subscriptions consumed inside the app are a different case: Apple and Google require their own in-app purchase systems for those, with their own fees and rules. We do not work around this, and you should plan for it.
Studio Lamp
Physical product, shipped · $249.00
SparkIO checkoutDesk Refill Club
Monthly box of physical goods · $18 / month
SparkIO checkoutThe calm desk, in five lessons
Video course, watched in the app · $49
Store in-app purchaseJournal Plus
Digital subscription, read in the app · $4 / month
Store in-app purchaseThe stores set these rules and change them. Exceptions vary by region; check the current guidelines.
Included in every app
Each of these is a setting in the editor and an event in the dashboard, with the same names as on the web.
Send to everyone, a segment or one customer, from the dashboard or the API. Permission is asked when you choose, not at first open.
The same login as your website. Orders, subscriptions and saved cards follow the customer between web and app.
The catalog and the cart are cached on the device. Browsing works without signal; checkout waits for a connection.
A link to a product or page opens the app when it is installed and the website when it is not. One URL, both destinations.
Installs, sessions, screens and the checkout funnel in the dashboard, with the same event names as the web.
Native crashes are collected with the app version and device, grouped by cause, and shown next to the release they belong to.
Questions
Build from your existing project; submit when you are ready.