Back/Product/GitHub Spark
BeginnerProduct

How to Build a Kid-Friendly AI Fortune Teller App with GitHub Spark

Build a one-button fortune teller in GitHub Spark, then tune the generator for short, concrete, age-appropriate fortunes and test enough outputs to catch repetition or an unexpectedly scary result.

How to Build a Kid-Friendly AI Fortune Teller App with GitHub Spark

Marco builds the fortune teller live in GitHub Spark, then Claire and Marco tighten the output from abstract prose to short, concrete, funny fortunes that work for young children.

Before you start

What you need

  • GitHub Spark access
  • A target age range and reading level
  • Examples of acceptable fortunes and topics to exclude
  • The phone or tablet that will run the app
  • An adult who will operate or supervise it

What you’ll make

A mobile fortune teller that produces one short, concrete, playful fortune per tap without collecting a child's personal information.

Tools used

  • GitHub Spark

    GitHub's AI app builder for creating apps with natural language

Step by step

The workflow

Follow the sequence once, then adapt the prompts, checks, and handoffs to your own setup.

5 steps

Step01

Provide the Initial App Concept Prompt

Tell Spark what happens when the user taps the button, who the audience is, and what the app must not collect. Start with one screen and one action.

Example prompt
Make a mobile fortune teller app for children ages [range]. When an adult taps one large button, show one new fortune. Do not ask for a name, birthday, photo, voice sample, or other personal information. Keep the first version to one screen.
Step02

Generate and Review the First Version

Open the generated app on the device you plan to use. Check the button, text size, contrast, tap target, loading behavior, and several initial fortunes before changing the visual design.

Step03

Refine the Output with a Follow-up Prompt

Replace broad requests such as "kid friendly" with a clear reading level, length limit, safe subject matter, and a few representative examples.

Example prompt
Make every fortune one sentence and understandable to a [age]-year-old. Use concrete events a child can picture. Keep the tone warm and playful. Avoid danger, death, romance, money, health, identity, appearance, and promises about the child's future.
Step04

Iterate with More Specific Feedback

Sample at least 30 fortunes. Note repeated objects, difficult words, abstract phrases, and any output that would be awkward to read aloud, then revise those specific patterns.

Example prompt
The current results repeat [pattern] and use words such as [examples]. Vary the subject, setting, and sentence shape. Use everyday words, gentle humor, and a concrete action or surprise. Here are three outputs to keep as style references: [examples].
Step05

Test the Final, Polished App

Test the finished loop on the event device with the adult operator. Confirm that each tap produces a readable result, that the interface recovers from an error, and that approved backup fortunes are available if the connection fails.

What good looks like

  • A child in the target age range can understand each sampled fortune.
  • The app avoids frightening, adult, discriminatory, medical, financial, or personally predictive content.
  • Repeated taps produce enough variety without getting stuck on one object or pattern.
  • The primary button and text remain usable on the device and in the lighting at the event.

Build your next product with ChatPRD

Turn an idea into a PRD, user stories, and a plan.

Try ChatPRD free

After the steps

Runbook notes

How to recover when the loop fails and where human judgment helps.

Recover

If it goes sideways

The fortunes sound poetic but mean very little to a young child
Add a reading level, a one-sentence limit, concrete examples, and a ban on abstract cosmic language.
The generator repeats the same object, setup, or joke across many taps
Test a larger sample, list the repeated patterns, and ask Spark to vary subjects, settings, and sentence structures.
A fortune becomes scary, adult, insulting, or too personally predictive
Add explicit excluded topics and safe fallbacks, keep an adult in control, and stop using the app if the boundary fails.
The app depends on a weak network connection at the event
Test on the exact device and connection ahead of time, and keep a short set of approved backup fortunes available offline.

Start shipping
better products.

Join 100,000+ product managers who use ChatPRD to write better docs, align teams faster, and build products users love.

Free to start
No credit card
SOC 2 certified
Enterprise ready