Your store app and push notifications

Every ecommerce plan includes a branded mobile app for your store, for Android and iPhone. It has your logo, colours, menus, banners and products, and it updates itself from your admin. The same app can send order and delivery updates as phone notifications, and shoppers can talk to your assistant inside it.

At a glance

What	Where you set it	Notes
Turn the app on, home page, tab bar, update policy	Storefront → Mobile app	The app reads everything from your site. You never rebuild it for a content change.
Links that open in the app, Sign in with Apple	Mobile app → App identity	Android package name and signing fingerprint, iOS bundle id and team id
Download page and footer block	Mobile app → Store link, then Site Builder → Footer → Get the app	`/get-app` shows the install steps. `/get-app/android` always points to the newest Android file, so a printed QR code never goes out of date.
Phone notifications	Notifications → Settings and Policy, plus one Firebase project	See the five steps below
Chat button and assistant	Messaging → Settings	Avatar, assistant name, greeting and quick actions are the same on the website and in the app

1. Get the app

Open My Account → Downloads on storeconsole.com and download the mobile app. It is free with every ecommerce plan.
Follow the app's README. You only change files under config/: your brand, your site address, your signing keys and your Firebase values.
Build the Android file, or the store builds, and upload it. With a direct-download Android file, put its address in Mobile app → Store link. Every page's footer and /get-app update straight away.

2. Phone notifications in five steps

Use one Firebase project per store, created with the store owner's own Google account. It is free.

Firebase project. At console.firebase.google.com, create a project. Add an Android app with your app's package name, and an iOS app with your bundle id. For iPhone, upload an APNs key under Project settings → Cloud Messaging.
App values. Copy the project id, project number, and each app's API key and app id into your app's config/env/prod.json (FIREBASE_PROJECT_ID, FIREBASE_SENDER_ID, FIREBASE_ANDROID_API_KEY, FIREBASE_ANDROID_APP_ID, FIREBASE_IOS_API_KEY, FIREBASE_IOS_APP_ID), and build the app again.
Server key.
- Under Project settings → Service accounts, generate a private key.
- Save it on your server outside the public folder (for example storage/app/private/firebase/credentials.json).
- Set FIREBASE_CREDENTIALS to that path and NOTIFICATION_FCM_ENABLED=true in .env.
- Run php artisan config:cache and php artisan queue:restart.
Admin. Turn on FCM in Notifications → Settings. In Notifications → Policy, switch FCM on for order, delivery, payment, booking and rewards messages. Leave sign-in codes and offers off unless you want them.
Test. Sign in on the app, allow notifications, then place a test order or change an order's status. The phone shows it within seconds. Notifications → Reports, filtered to FCM, shows it as sent.

The app asks for permission right after sign-in. Shoppers can switch notifications off under Account → Notifications in the app, or mute just one group, such as offers, in their phone's settings.

3. Chat inside the app

When chat is on, the app shows the same chat button as your website, with your assistant's avatar. Once an hour a short greeting appears beside it. Inside the chat:

your quick actions appear;
product suggestions arrive as cards that open the product in the app;
cart and order answers come with Pay now, Checkout and Track order.

An AI / Human switch in the chat header hands the conversation to your team and back to the assistant. When File upload is on, shoppers can send up to five photos. Change the avatar, name, greeting, quick actions or uploads in Messaging → Settings, and the app follows.

Signed-in shoppers always have the notifications bell in the app header. It opens their latest notifications, with Mark all read and View all notifications, and tapping one opens its page in the app.

4. Sign-in in the app

Email and password, a one-time email code, passkeys and fingerprint unlock work out of the box. Google and Facebook sign-in use the redirect addresses you already registered for your website, so you change nothing in their consoles. On Android, the shopper comes back to the app by themselves after choosing their account.

When something does not work

You see	What to do
No notifications, and Reports show FCM failed with Driver [fcm] not supported	Update Store Console. Versions before November 2026 could not send app notifications.
No FCM line in Reports for an order	FCM is off for that message in Notifications → Policy.
The phone never asked for permission	The app was built without the Firebase values, or the shopper is not signed in.
Google sign-in stays in the browser	Update Store Console to November 2026 or later.
Links open the browser, not the app	Check Mobile app → App identity, then reinstall the app.

From the November 2026 update, the website can send browser notifications too. They work in Chrome, Edge and Firefox, and in Safari on iPhone and iPad once the site is added to the Home Screen. To turn them on, open Notifications → Settings → Browser push, press Generate keys and switch on Web Push. Shoppers are asked once after they sign in. They can change it later under My Account → Notifications.