Blueprint

The Blueprint is the dashboard’s main workspace once setup is done. It’s a grid of cards covering the features most apps want — push notifications, sign-in flows, in-app purchases, deep linking, app store submission, and so on.

Each card opens to a detailed page with:

• A short explainer of what the feature is and why you might want it
• A list of prerequisites (e.g. “you need a paid Apple Developer account”)
• Step-by-step instructions
• Often a 3–5 minute video walkthrough
• An AI-ready prompt you can paste into Claude Code (or your editor of choice) to do the actual implementation

How the Blueprint is organised

Cards are grouped into three buckets:

Foundations

The basics every app needs. Things like:

• Setting up sign-in and sign-out flows
• User profiles and avatars
• Basic navigation
• Theme and design system

Features

The functionality that makes your app yours. Examples:

• Push notifications
• In-app payments / subscriptions
• Image uploads
• Realtime updates
• Offline support
• Search

Polish

The stuff that makes the difference between a hobby project and a shippable product:

• App icon and splash screen
• App Store screenshots
• Privacy policy and data deletion endpoints
• Onboarding flows
• Crash reporting and analytics

Cards filter by your device track

When you picked iPhone or Android in the setup guide, Mosayic remembered. Cards relevant to one platform are highlighted; cards specific to the other are dimmed. You can toggle the filter or switch your default device track from your account settings.

The “AI-ready prompt”

Most cards include a prompt block you can copy. The prompt:

• Tells the AI what you’re trying to build
• Points it at the relevant files in your codebase
• Lists the libraries and patterns Mosayic projects already use (so the AI doesn’t reinvent them)
• Sets expectations for testing and verification

The prompt assumes you’re using Claude Code, which can read and edit files directly in your project. With other tools you may need to copy the prompt and the relevant file contents manually.

Tip

The prompts are starting points, not finished spells. Tweak them to match your app — add your own constraints, remove things that don’t apply, paste in any reference UI screenshots you have. The more specific the prompt, the better the result.

Coming soon cards

Some cards show a “Coming soon” badge. These are features Mosayic plans to support but hasn’t documented yet. You can still build the underlying feature using your own approach — Mosayic isn’t a closed platform — but the curated walkthrough isn’t ready yet.

Why “Blueprint”?

Because the cards aren’t features that exist in your app already. They’re plans for features you can choose to build. Each one is a small, tested recipe for going from “I don’t have X” to “I have X working in my real app, on my real device, with my real users.”