How Glassly works
Create an app, test it, then put it on a phone. The steps and what you need for each.
1. Choose a starting point
Browse the free templates and read the features and limitations on the one nearest your idea. For example, the appointments app handles bookings for one location; it does not take card payments. Sign in to Glassly with Google and create the template. Its opening setup message lets you name it and choose a colour preset, or keep the existing one, without using credits. If you start from the homepage, you can upload your own logo before creation.
Creating a template uses no credits. You can also describe a new app in plain English; generating that app uses credits.
2. Try the preview and set up your app account
Glassly prepares the app and a managed starter backend for accounts, a database and file storage. Open the web preview to try its screens. Your Glassly account and the accounts inside the app are separate: create an account inside your app to test sign-in.
For templates with an admin role, open Who runs it in the app's settings on Glassly and appoint the account you created. Signing up first does not make someone an admin. Check the customer and admin views separately.
3. Ask for a change, then check it
Describe one change in chat, such as adding a notes field to a booking. Glassly generates the changes and refreshes the preview. Try the affected flow again, including saving and reopening the data. More complex requests may need several rounds of testing and revision.
New accounts get 5 credits to try changes. Usage depends on the work requested; a fixed number of edits is not guaranteed. See plans and credit estimates.
4. Install and test on a phone
Glassly compiles and signs native iOS and Android builds on its own machines. You do not need a Mac, Xcode or a local build setup.
For iPhone installs through Glassly, connect your own Apple developer account (standard fee $99/year, paid to Apple). Android installs from a link, subject to device permissions and developer verification. Publishing on Google Play needs your own developer account ($25 once, paid to Google).
The install page guides you through the steps for your device. Android may require permission to install from your browser and developer verification steps. For iPhone, connect your Apple account and follow device enrolment on the phone. The iPhone and Android guide explains the differences.
Test on each platform you intend to support. A browser preview does not establish that camera access, notifications or device-specific behaviour work on a phone.
5. Prepare for your users
Check who can sign up, what each role can see, and the actions your users need to complete. Connect any required payment or notification services. Your own Supabase project is required for production or store builds, integration secrets, and apps that outgrow the starter backend. Glassly guides the move from the starter project.
If you publish to the stores, Glassly delivers the iPhone build to App Store Connect and produces a signed Android App Bundle for you to upload to Google Play. You complete the listing, privacy disclosures and any required testing. Apple and Google review submissions; a successful build does not guarantee approval. Read the Google Play guide before setting a launch date.
6. Maintain or export your app
Ask for further changes in chat and test each version before sharing it. Direct Android installs use the latest build on the install page; users still need to install the new version. Store releases follow each store's update process.
In settings, Download my project exports the app's Expo (React Native) source. Follow its README to configure services and run it with developer tools. The export guide explains what the download includes and what needs a separate backup.
How long does it take?
There is no fixed end-to-end time. Starting with a template avoids generating its existing screens, but backend preparation, build queues, account setup and testing still take time. Store review is a separate step. Starter backends also sleep after inactivity: about an hour on free accounts or around two days on paid plans, with restoration typically taking a few minutes.