I build SongUp AI, an AI song maker. This is a small product lesson from it, written for anyone who designs forms
for people who live between two languages.

A song for a grandparent is one of the gifts people make with SongUp AI, and the holidays bring more of them.
Think about who is typing that request. Often enough it is a grandchild who grew up in the US, the UK, Canada or
Australia, and the grandmother grew up somewhere else. The grandchild writes English comfortably. The
grandmother's language is Tagalog, Urdu, Spanish, Polish or Arabic, and the grandchild can understand it at the
dinner table but could not write a verse in it.

If your form has one "language" field, you force that person into a bad choice. Either the song comes out in
English, which is not the language the gift is for, or they try to write lyrics in a language they only half speak,
and give up.

The fix: separate "what you write in" from "what it is sung in"

In SongUp AI you describe the song, or write your own lyrics, in whatever language is easiest for you, and you pick
the song language on its own. The song language list has 76 entries. So the grandchild can type:

A warm, gentle song for my grandma Rosa. She grew up in a village near Guadalajara, raised six kids,
still makes tamales every Christmas Eve and calls everyone "mijo", even the dog.

and choose Spanish as the language it is sung in. The details survive the translation, and the name stays a name.

Three things we learned building around that split:

1. Names are not words. A translation step will happily "translate" a name or a nickname. "Mijo" should stay
"mijo". A song for a grandparent lives or dies on the names and the pet words, so those must come through as typed.

2. Script is a stronger signal than a dropdown. If someone pastes lyrics in Arabic script, they usually
want an Arabic song, whatever the dropdown says. We now let what people actually typed weigh in when guessing the
default, and the person can still change it.

3. Let people hear it before they pay. Someone writing for a grandparent in a language they only half speak is
nervous that it will sound wrong. So a free account can hear a 30-second preview of a song made from their own
lyrics before buying. One full song is $2.99, paid once, no subscription.

Why this matters beyond music

Any product used by families split across countries has the same shape: the person filling in the form is not the
person the output is for. Gift cards, greeting cards, photo books, recorded messages. If you only ask one language
question, you are quietly asking "which of these two people matters?"

A useful test: ask your form "who reads the output?" and "who writes the input?". If those can be different people
with different languages, give them two fields.

Where the song ends up

Plenty of grandparents will never open a link, so the song downloads as an MP3: families can put it on a CD, a USB
stick for the car, or a smart speaker. For this audience the download button matters more than the share button.

If you want to see the flow, the page we built for this case is here:
a song for Grandma, with her name in it.

Today's short video on the same idea: https://youtube.com/shorts/OlTDFXeNFfU

I'd like to hear from anyone who has designed for bilingual families: where else does one language field break?