Welcome to our first dev log! We’ll be sharing regular updates on what we’re building and the decisions behind it.

This week: the dashboard.

Starting with “Why”

Before writing any code, we asked ourselves: what do indie developers actually need to see when they check their analytics?

We talked to dozens of developers and found some common themes:

  1. “Am I making money?” - Revenue is king, but context matters
  2. “Are people finding my game?” - Wishlists and store visits
  3. “Is something wrong?” - Anomaly detection
  4. “What should I do next?” - Actionable recommendations

The Layout

We landed on a layout that prioritizes these needs:

┌─────────────────────────────────────┐
│  Revenue (30d)  │  Units  │ Wishlists│
├─────────────────────────────────────┤
│         Revenue Trend Chart          │
├─────────────────────────────────────┤
│  Recent Activity  │  AI Insights     │
└─────────────────────────────────────┘

The key metrics are front and center. The trend chart shows you the trajectory. And the AI insights panel surfaces what you need to know without digging.

Design Principles

We’re following a few core principles:

1. Dark Mode First

Developers spend a lot of time staring at screens. A dark theme isn’t just aesthetic - it’s practical.

2. Data Density Done Right

We want to show you a lot of information without overwhelming you. Every element earns its place.

3. Glanceable Metrics

You should be able to check your dashboard in 10 seconds and know if things are good or if you need to dig deeper.

4. Mobile Responsive

Sometimes you want to check your sales from your phone. We’re designing for that from day one.

What’s Next

Next week we’re tackling the AI insights engine - how we surface recommendations without being annoying.

Stay tuned!

Following along? Join the waitlist to get early access.