restrOS

Designed, built and launched within 4 weeks, for a friend's restaurants in Warsaw
- My role
- Product designer, researcher and builder
- Timeline
- 4 weeks from first conversation to launch
- Tools
- Figma, Replit, Claude Code
- Live demo
- https://restr-os--vine8.replit.app
The problem
My friend runs two Indian restaurants and juggles orders, inventory, staff schedules, reports across separate apps, WhatsApp messages and paper notes. The big restaurant platforms are built for chains and priced accordingly, so independent venues like his get left behind. Every hour spent on admin is an hour not spent with guests.
The goal
Replace the patchwork of tools with one simple app that fits how his restaurants actually work, and use AI to take the boring decisions off his plate.
What I did
After our discussion, I followed him all day to see how he works and find pain points:
- Research: spent 2 days in the restaurants, interviewed 2 managers and 5 staff, and mapped a normal day from opening to closing
- Product: picked 3 core modules to start, based on what hurt the most: online orders, short-staff
- Design: designed all flows and screens in Figma, built for busy, non-technical people (tablet/phone)
- Build: shipped a working product with AI tools (Replit, Claude Code), so we could test in the real restaurants within 2 weeks
- Launch: trained the team, collected feedback and iterated 5-6 times in the first weeks
Key design decisions
- A clean dashboard showing daily restaurant engagement, employee schedule, and key figures on top
- Easy to switch between restaurants on top of the page
- Allow integration with running apps for smooth transition
Results
My friend was happy to use the app as it gave him more control and better understanding of his restaurants.
What I learned
- Owners want fewer tools, not more features
- Spending time in the restaurant beats any survey
- Designing and building it myself let me fix problems the same day, often while sitting at his restaurant



