Back to the episode map

Research Note

Informal Product Naming Research Note

An informal name can improve memory and conversation when it is concrete, distinctive, repeatable, and socially usable. The name creates debt when it obscures category, o

Aug 4, 20262 min readBy Dalton Anderson

Informal Product Naming Research Note

Editorial conclusion

An informal name can improve memory and conversation when it is concrete, distinctive, repeatable, and socially usable. The name creates debt when it obscures category, ownership, cultural meaning, or version identity.

The article should not claim that informality caused Nano Banana adoption. The model's visible editing capability and distribution are material parts of the case.

Comparison cases

CaseDecisionLesson
Nano BananaGoogle adopted a public LMArena codename and later extended it into a familyA socially usable name can travel, but a growing family needs exact model identifiers
Android dessertsGoogle moved the public release system to Android 10Memorable names can fail global pronunciation, cultural familiarity, and version-order needs
Project ScorpioMicrosoft shipped Xbox One X while retaining Scorpio in an engine and limited editionA codename can be contained as community heritage
Bard to GeminiGoogle aligned the assistant experience with the Gemini model familyPortfolio consolidation can reduce one ambiguity and create another

Primary records are Google's Nano Banana origin account, Android naming change, Bard-to-Gemini announcement, and Microsoft's Project Scorpio Edition record.

Memory research boundary

A 2006 recognition-memory study reported better performance for concrete words than abstract words under its experimental conditions. PubMed record

That finding supports a limited observation about word processing. It does not predict product-name success. Naming also depends on category, prior associations, culture, pronunciation, product quality, distribution, legal clearance, and the surrounding brand system.

Decision model

Adopt an informal name when users carry it and the product system can supply category, ownership, and version precision. Contain it when the name has community or campaign value but should not own the product taxonomy. Retire it when its clarity, cultural, pronunciation, or portfolio costs exceed its social value.

Sources

Follow the evidence.

  1. The effect of word concreteness on recognition memorypubmed.ncbi.nlm.nih.gov
  2. Android public naming changeblog.google
  3. GIE-Benchalphaxiv.org
  4. Systematic review of human and AI co-creativityarxiv.org
  5. ai.google.dev: image generationai.google.dev
  6. CompBenchcomp-bench.github.io
  7. Bard becomes Geminiblog.google
  8. Nano Banana across Google productsblog.google
  9. EditInspectorresearch.google
  10. Nano Banana in Google Photosblog.google
  11. Gemini 2.5 Flash Image model pageai.google.dev
  12. Nano Banana examplesblog.google
  13. Google AI updates from November 2025blog.google
  14. Canva Magic Layerscanva.com
  15. Xbox One X Project Scorpio Editionnews.xbox.com
  16. How Nano Banana got its nameblog.google
  17. Gemini app updated image editing modelblog.google
Informal Product Naming Research Note