App Studio: The Tool That Builds Apps, Designed from Scratch

App Studio: The Tool That Builds Apps, Designed from Scratch

Platform

Vibe coding

Design System

Design System

Vibe coding

Platform

Final design

OVERVIEW

TYPE

Web Platform

ROLE

Product Designer

YEAR

2026

READ TIME

TYPE

3 min read

TYPE

Web Platform

ROLE

Product Designer

YEAR

2026

TYPE

3 min read

I designed App Studio from scratch, working directly with the CEO: a visual builder inside Kobe Platform where retailers create, preview and publish their app’s pages without developers. Instead of designing an app, I designed the tool that creates apps.

I designed App Studio from scratch, working directly with the CEO: a visual builder inside Kobe Platform where retailers create, preview and publish their app’s pages without developers. Instead of designing an app, I designed the tool that creates apps.

THE PROBLEM

Retailers’ content lived in the CMS, with no easy way to turn it into app pages. They published without a real preview and depended on tech teams for simple changes.

WHAT I DID

End to end, reporting directly to the CEO: architecture, scope, every flow and state, a staged launch and QA with engineering.

IMPACT

4×

4×

more weekly publications in 3 weeks of beta (from 11 to 47)

App Studio: The Tool That Builds Apps, Designed from Scratch

App Studio: The Tool That Builds Apps, Designed from Scratch

Platform

Vibe coding

Design System

My process

01. Research

02. Define

03. Design

04. Test

05. Deliver

01. Research

Learning from the builders retailers already knew

Learning from the builders retailers already knew

Learning from the builders retailers already knew

Retailers were publishing without seeing what their customers would see. App Studio had to close that gap.

Retailers were publishing without seeing what their customers would see. App Studio had to close that gap.

Retailers were publishing without seeing what their customers would see. App Studio had to close that gap.

I benchmarked Tapcart, Webflow, Firebase and Framer, and analyzed VTEX, the CMS where retailers’ content lives: great for storing content, not for designing a storefront.

02. Define

Designing the architecture before the screens

Designing the architecture before the screens

Designing the architecture before the screens

130+

130+

130+

existing apps analyzed to scope the first version

The hardest part wasn’t visual. It was the information architecture.

The hardest part wasn’t visual. It was the information architecture.

The hardest part wasn’t visual. It was the information architecture.

App Studio sits next to branding, notifications and dashboards, so I designed each screen to solve today’s problems without limiting tomorrow’s.

I validated technical feasibility with developers and split the scope into sprints.

03. Design

One editor for very different users

One editor for very different users

One editor for very different users

A big part of my work was mapping every state and edge case.

A big part of my work was mapping every state and edge case.

A big part of my work was mapping every state and edge case.

Retailers drag components onto the canvas and set their content, look and destination. I designed every path and state, from errors to saves, for very different users: with or without AI, first app or existing one.

All of it runs on the design system I also built from scratch.

04. Test

Measuring what people did, not what they said

Measuring what people did, not what they said

Measuring what people did, not what they said

Lots of editing, very little publishing: the gap was the path from building a page to putting it live.

Lots of editing, very little publishing: the gap was the path from building a page to putting it live.

Lots of editing, very little publishing: the gap was the path from building a page to putting it live.

In beta, I tracked what people actually did with Google Analytics 4.

15.6 min avg. engaged time per visitor · 407 component edits · 1 user published, in week one.

05. Deliver

Launching in stages to build trust

Launching in stages to build trust

Launching in stages to build trust

Building trust before control: preview first, then editing, then publishing.

Building trust before control: preview first, then editing, then publishing.

Building trust before control: preview first, then editing, then publishing.

Three stages: a preview with the retailer’s real content, then visual editing, then publishing with drafts, versions and rollback.

Designing in code

Beyond handoff and design QA, I vibe code parts of the product with Claude Code, building changes on branches and merging them.

KEY DECISIONS

Interactive Title

A Minimum Lovable Product, not just an MVP

Why: retailers had to want to come back, not just be able to use it. Trade-off: a smaller first scope, polished instead of broad.

A visual layer on top of the CMS

Why: content stays where retailers already manage it: nothing new to maintain or migrate. Trade-off: the editor depends on how each retailer structures their content.

Reuse what already exists

Why: brand colors, components and the app’s own design system make the preview exactly what customers will see. Trade-off: less freedom to design outside the system.

Outcome

From lots of editing to real publishing in five weeks of beta.

From lots of editing to real publishing in five weeks of beta.

From lots of editing to real publishing in five weeks of beta.

51%

of all engaged time on the platform, in week one

1,000+

component edits by clients in just 3 weeks

3

clients published their app for the first time in a single week (vs. 1 in week one)

It became the platform’s most-used module from day one, with 22 clients exploring it in a single week. Next, I’m looking into why deletions almost matched additions in the busiest week.

I keep iterating with users and my developers (my partners in crime). One of the most rewarding projects of my career.

In constant

motion

© 2026