How a Question Travels

Visual brainstorm: what a dinner question looks like when it leaves the app or email — and four ways to present questions inside the email itself. Real art, real questions.

A · The share object

What actually lands on the other person's phone when a parent taps share. Rule: the share must be complete in itself — question + story + who it's from — because most recipients will never tap anything.

A1 · Plain text

Native share sheet → iMessage/WhatsApp. Highest forward rate — text always renders, zero friction. This IS the "text it to dad" moment.

To: Mike ❯

Tonight at dinner: "Why didn't anyone from the Israelite army dare to fight Goliath?" — from David and Goliath 🛡 Bible Stories for Kidsapp.biblestoriesforkids.app/q/david

on it 👊

A2 · Story card (portrait)

Image share for the family group chat or Grandma. Art on top, question in serif, tiny brand foot. Same skeleton as the verse card — one shared design system.

Tonight at dinner

"Can you tell me why Shadrach, Meshach, and Abednego refused to worship the golden statue?"

Bible Stories for Kids

A3 · Social square

IG story / WhatsApp status. Night-washed art, question over the gradient. This is the organic-acquisition version — other parents see it and ask what app that is.

Ask your kids tonight

"If God offered you anything in the world, what would you ask for?"

Bible Stories for Kids

B · Inside the email

Four presentations of the same content. B2 is designed to be screenshotted — the screenshot IS the share button.

B1 · Speech bubbles (current)

The baseline that ships today: orange label + cream bubble per question. Clean, scannable, three questions max.

From The Fiery Furnace

"Can you tell me why Shadrach, Meshach, and Abednego refused to worship the golden statue?"

From David and Goliath

"Why didn't anyone from the Israelite army dare to fight Goliath?"

B2 · The table card

All three questions in one dashed "card" with a screenshot tag. Parents screenshot it to their lock screen or the family chat — the whole card travels as one image, brand included.

screenshot me

This week at the table

Why did Shadrach, Meshach & Abednego refuse to bow? (The Fiery Furnace)
Why didn't anyone dare to fight Goliath? (David and Goliath)
How did Esther's faith help her decide? (Esther)

B3 · One-question hero

A single question over washed story art — for a possible daily/lighter variant, or the top of the weekly send with the other two below as bubbles. Maximum feel, minimum reading.

Tonight at dinner

"Why did Jesus stop for the one person everyone else walked past?"

B4 · "Text it to dad" row

Each question carries a prefilled-SMS pill (and WhatsApp for Spanish-speaking families). One tap in a mobile email client opens Messages with the question already typed. The forward mechanism, made one-tap.

From David and Goliath

"Why didn't anyone from the Israelite army dare to fight Goliath?"

▸ Text it to dad WhatsApp

C · How the sharing actually works

Mechanics, cheapest first:

Screenshot-first design (free): make B2's table card self-contained — brand, questions, story names — so a screenshot carries everything. No engineering at all.
Prefilled SMS links (email-side, ~zero cost): sms:?&body=Tonight at dinner… works in iOS/Android mail clients. WhatsApp: wa.me/?text=… — matters for the Spanish-audio families.
App share sheet (app build): share button on the dinner card + verse card → native share with A1 text + A2 image attached. The A2/A3 cards can be generated server-side from the same fields (art URL + question + Color).
The acquisition loop: every shared object carries one quiet line ("Bible Stories for Kids") and a link that opens the story with one free listen — the share IS the free trial.

Sharing Concepts

A · The share object

B · Inside the email

C · How the sharing actually works