Mosaic, Part 1: The Problem with Apps Today

September 12, 2025 5 min read Hong

Think about the last time you planned a trip. You opened your airline's app to check flights. Switched to Google Maps for directions. Used WhatsApp to coordinate with friends. This is normal today. But it doesn't feel right, does it?

Think about the last time you planned a trip.

πŸ“± You opened your airline's app to check flights.

πŸ—ΊοΈ Switched to Google Maps for directions.

πŸ’¬ Used WhatsApp to coordinate with friends.

🌍 Maybe downloaded a translation app just for the week.

πŸ“Έ And after the trip? You probably dug through Photos and a budgeting app to figure out what you spent.

That's five or six apps β€” all for one journey.

This is normal today. But it doesn't feel right, does it?

We live in a world where apps are still siloed products. App stores want you to search, install, and learn them one by one. But our lives don't fit into silos. We live in flows β€” trips, health check-ups, courses, projects β€” and those flows cut across dozens of apps.

This series is about a different way of thinking:

Mosaic

What is Mosaic?

At its core, Mosaic is a vision:

  • Instead of monolithic apps, we think in tiles β€” small modular capabilities.
  • A user's intent ("I'm visiting Tokyo") becomes the starting point.
  • The right set of tiles assemble into a cohesive app, just for that journey.
  • And as your journey changes, the app reshapes itself.
User flow diagram showing how Mosaic adapts apps to user journeys

How Mosaic assembles the right capabilities for your specific journey

In the coming parts of this series, I'll unpack this vision step by step.

What This Series Will Cover

  • Part 1 β€” The Problem with Apps Today
    You're reading it! Why app stores and siloed apps don't fit the modern user journey. Introduce the Mosaic concept at a high level.
  • Part 2 β€” The Mosaic Concept: Adaptive Journeys
    Deep dive on "tiles," adaptive layouts, self-updating flows. Tokyo trip example.
  • Part 3 β€” Under the Hood: Context Engine, Registry, Composer
    Explain the building blocks and why this differs from MCP/agents. Discuss security, version locking, rollbacks.
  • Part 4 β€” Near Future & Beyond
    Why PWAs are the natural first step. The long-term OS-level vision. Examples: travel, health, learning.

Why Start Here?

Before we can imagine a new model, we need to clearly see what's broken today:

  • Too many apps. Every task means juggling 3–5 different tools.
  • Too much friction. Search, install, learn, delete. Repeat.
  • Too little adaptability. Apps don't evolve with your journey.

Mosaic is my attempt to rethink this from the ground up.

Homework for You

Before the next part, here's a simple exercise:

πŸ‘‰ Think of one thing you did this week that required 3 or more apps.

Write them down. How did it feel switching back and forth?

Hold onto that example β€” we'll revisit it in Part 2, when we imagine how Mosaic would handle it.

Enjoying the Series?

Share your thoughts or questions about AI-powered development.