Sample Use Cases

Sample use cases to begin with

Not sure what to type first? This page is a gallery of starter ideas. Each one is a real thing GRU953-Studio can build, written the way you'd actually say it.

You start a project by typing your idea between square brackets — for example [ a simple habit tracker for my phone ] — or by typing /studio. Pick any example below, copy it, or change the words to fit your own idea. There's no wrong way to describe it: if you can explain it to a friend, that's enough. The studio then asks you a few simple pop-up questions to make sure it understands you.

The best advice is the simplest: start small. A single page you can see working is a lovely first win, and you can always come back and grow it later.

If you haven't set the studio up yet, the Installation page walks you through it one step at a time. For the full list of what the studio can do, see Features.

What the sizes (Tiers) mean

Every idea is different, so the studio quietly sizes each job before it starts, and tells you the size in plain words. It calls these sizes Tiers. A bigger size simply means more checking and care — not more work for you. You can always ask for more or less.

Size	Roughly means	What the studio does
Tiny	A single page, no logins, nothing saved	A small, quick, careful build
Standard	Logins and/or saved data	A full design pass and independent testing before it ships
Complex	Money, or other sensitive personal data	The whole team: extra security checks, a privacy review, and tests for when things go wrong

Where an example below has a clear-cut size, it's named. Where it depends on the details, you'll see a "likely" size with the reason — the studio confirms the real size with you before it builds anything.

Web and simple tools

• A personal one-page site. [ a one-page website listing my favourite books, with a short review for each ]

  • What happens: it builds a single web page showing your books and reviews.
  • Size: Tiny — one page, no logins, nothing stored. The simplest kind of job, and a great first project.

• A small business tool. [ a booking page where my hairdressing clients can pick a free slot and leave their phone number ]

  • What happens: clients see open times, choose one, and leave a contact number.
  • Size: Standard — it needs logins and saved data, so a bigger team wakes up on its own: a proper design pass and independent testing before it ships.

Phone, desktop and every platform

• An iPhone app. [ an iPhone app that tracks how much water I drink each day ]

  • What happens: you log each drink and see your daily total, built natively for iPhone by the Swift specialist.
  • Size: likely Standard — it saves a record over time, though it's still a personal, single-user app.

• A Windows desktop tool. [ a small Windows program that renames a folder of photos based on the date they were taken ]

  • What happens: point it at a folder and it tidies the file names by date, built for Windows by the C#/.NET specialist.
  • Size: likely towards the smaller end (Tiny to Standard) — a local tool with no logins and nothing personal stored.

• One app, several phones and computers. [ a to-do list app that works the same way on my Android phone, my iPhone, and my laptop ]

  • What happens: one to-do app that runs the same everywhere, using Flutter — the studio's cross-platform default — so a single build genuinely runs on all of them.
  • Size: likely Standard — it saves your tasks and targets several platforms at once.

Handling money and sensitive data

• Something handling money. [ a small shop where people can buy my handmade candles and pay by card ]
  • What happens: a shop page where people browse your candles and pay by card.
  • Size: Complex — payments and personal details mean the full team activates: extra security checks, a privacy review, and tests for what happens when something goes wrong (a declined card, for instance), not just when everything works.

Real content in your own language

The studio doesn't fill your app with placeholder text — it writes the real words. Written content in Bangla and English is produced by Claude directly, and costs you nothing extra to generate.

• An app with real Bangla content. [ a small recipe app for my mother, with all the buttons and messages in Bangla ]

  • What happens: the Text Content Specialist writes genuine, natural Bangla copy — not a machine-translated gloss — matched to the mock-up you approved.
  • Size: likely Standard — it stores recipes and needs real written content.

• An app with generated images. [ a children's story app with a colourful illustration on each page ]

  • What happens: with your one-time yes and your own Google Gemini key, the Image Content Specialist generates each illustration, always showing you the cost first and writing alt-text (a short description that lets screen readers and people who can't see the image know what it shows).
  • Size: likely Standard — several pages of content, plus generated pictures. Generated images use an optional connection you turn on yourself; see Connecting Gemini.

Features that use AI

• A feature that uses AI. [ a tool that reads a long PDF report and gives me a plain-English summary ]

  • What happens: the AI Developer writes the instructions the AI follows, builds in "say I don't know rather than guess", and hands the Tester a fixed set of checks — so the quality is proven, not just hoped for.
  • Size: set by the usual three questions, so it can be any size — even Tiny (a plain summariser like this one often is). Any AI feature, whatever the size, gets those built-in guardrails and quality checks. An independent fairness-and-honesty review is added only when an AI feature helps decide something about a real person (this summary tool doesn't, so it wouldn't need one).

• Using a local AI model instead of the cloud. [ a private journal app that summarises my entries using an AI model that runs on my own laptop ]

  • What happens: for a feature like this, the AI Developer can offer Ollama — a tool for running AI models on your own computer, free to use (no cost) — instead of Claude, so your entries never leave your laptop.
  • Size: likely Standard — it stores private entries and adds an AI feature. This is always your choice: the studio asks first and tells you the download size before anything installs. See Connecting Ollama.

Picking up where you left off

• Pausing partway through. Say "pause this" at any point, close your laptop, and come back whenever suits you. Nothing is lost, and a plain one-page dashboard shows exactly what's done, what's next, and what's waiting on you.

• Coming back to grow something already published. You don't start over to add to a finished app — just describe the change, for example [ add a way to search my recipe app by ingredient ]. The Maintenance Agent picks up your already-published project safely and builds on it.

Where to begin

If you're deciding between all of these, begin with the smallest one — a single page you can see working:

[ a one-page website listing my favourite books, with a short review for each ]

Type it, answer the handful of questions that follow, and you'll have your first finished thing in hand. From there, everything else on this page is within reach.

When you're ready for more, the Features page shows the full range, and Installation covers anything you still need to set up.