Start by creating one template and trying its main flow. This is a getting-started guide, not a timed recording: backend preparation, builds and account setup vary. A first browser preview and an app installed on your phone are separate milestones.
Choose a template that fits
Open the template gallery, inspect a preview and read its feature limits. Pick the template nearest your idea. A booking app is a useful first project if you want to see customer and admin roles; a recipe app is useful for trying saving, editing and planning. You can return to the gallery and create another template.
Give it your look
Sign in with Google and use the appearance choices shown during creation: the colours, and an icon style or your own logo. On a free account the app keeps its template’s name; your app’s own name comes with any plan. Creating a standard template is free and uses no credits. Changes requested later in chat use credits, including appearance changes.
Wait for the backend, then try the preview
Glassly prepares a managed starter backend for accounts, a database and file storage. Once the preview is ready, create an account inside your app and try its main action. Saving a booking or recipe and reopening it is a better check than only looking at a screen. For apps with admin features, appoint your in-app account through Who runs it in Glassly's app settings, then test both roles.
Try one change
Ask for something specific, such as a notes field on a booking. Check the result and describe any problem you find. New accounts get 5 credits to try this; how many changes they cover depends on the work. Pricing explains credit estimates and plans.
Put it on a phone
Free accounts include 5 native builds for your phone; paid plans have no build limit. 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). Follow the install page's instructions, then test the app on the device. The platform guide explains iPhone enrolment and Android verification. A first-time account setup can take longer than generating the app, so allow time for it.
When you return
Starter backends sleep after about an hour of inactivity on free accounts, or around two days for subscribers. Opening the app restores the backend, typically within a few minutes. Your own Supabase project is needed for production or store builds, integration secrets, or when you outgrow the starter limits.
The complete workflow guide covers what follows: device testing, preparing for users, store submission and exporting the source project.