Example prompts
For the only developer on the team
You're the one technical person — and the whole team waits on you for anything that touches code. With bychat, one person ships the whole suite: a mobile app, a landing page, an admin tool, and the internal tools your team runs on.
One setup, a whole suite of apps
Connect a Supabase project once and a single developer can stand up everything a non-technical team needs — usually just three or four bychat apps.
A landing page
A fast public site your team points customers to — built by chat, previewed live, published in one click.
An admin panel
A full-stack app with sign-in and your data on top of the same Supabase, so non-technical teammates run the day-to-day themselves.
A mobile app
An iOS/Android app on the same backend, so your team and members have what they need in their pocket.
Internal tools — and shared templates
Spin up the small internal tools the team keeps asking for. An org admin sets reusable templates once — a starting repo or even a slide deck — and everyone builds from them.
Example prompts
Copy one, tweak it to taste, and paste it into the prompt box to start building. The more specific you are about pages, components, and the look, the closer the first version lands.
Build a landing page for our product with a sign-up form that saves leads to my Supabase project.
Create an admin panel on my Supabase data with login, a table of orders I can edit, and basic charts.
Make a mobile app for our team on the same Supabase backend, with login and a list of today's tasks.
Build an internal tool to track time-off requests, with approvals and a calendar view.
Set up a reusable template from this repo so my whole org can start new admin apps from it.
Turn our onboarding doc into a slide deck the team can reuse for every new hire.
How to write a good prompt
Describe the app like you would describe a screen: the pages you want, the sections and components on them, and the look and feel. bychat builds on a modern React + Tailwind stack with a full component library, so it understands UI words.
- Pages & layout — a landing page, a dashboard, a multi-step form, a settings screen.
- Components — a nav bar, hero, cards, tabs, a data table, a chart, a dialog, a sidebar.
- Look & feel — colors and theme (e.g. "deep indigo with a light mode"), mood, rounded or sharp, light or dark.
Start with one sentence if you like — then keep chatting to refine. Mention a color or theme and bychat will carry it through; you can also tweak brand colors later in the Assets tab.