Product Design
UX flows, UI systems and clickable prototypes that are designed to be built — not just admired.
- ux/ui
- design systems
- prototyping
cloudsheep.dev
Wholeproducts, builtbyone
Design, web and mobile apps — dreamed up, drawn, coded and shipped by a single pair of hands. No handoffs, no telephone game, one owner from first sketch to launch.
whoami → one-person studio · stack → design · web · mobile · status → open to new projects · ls ./work → 20+ products
.NET
C#
Chrome
Docker
Figma
GitHub
GraphQL
JavaScript
MongoDB
Next.js
Node.js
PostgreSQL
Python
React
React Native
Redis
Scikit learn
Tensorflow
TypeScript
Built to keep running, long after launch.
A product does not end at handover. It gets monitored, maintained and answered for.
99.95%uptime in prod
48hresponse time
12+products shipped
6years of experience
One person, the whole product.
A one-person product studio
Design, web and mobile apps from a single pair of hands.
DPDušan PavlovićDesign and development
University of Niš
Graduate Engineer of Electrical and Computer Engineering
Computer Science and Engineering
Faculty of Electronic Engineering · Niš, Srbija
Four disciplines, one desk.
Web Development
Fast, maintainable web apps — from marketing sites to dashboards with real data models.
- next.js
- typescript
- postgresql
Mobile Apps — iOS & Android
One codebase or fully native — chosen per project, shipped to both stores.
- react native
- kotlin
- swift
Backend, APIs & Care
The unglamorous part done right: APIs, deployments, monitoring and long-term maintenance.
- node.js
- docker
- ci/cd
A process without surprises.
Discover
A call and a written brief. We define what success looks like before anything is drawn.
→ brief · estimate · timelineDesign
Wireframes to hi-fi, quickly. You review a clickable prototype, not a PDF.
→ wireframe · hi-fi · prototypeBuild
Weekly shippable increments on a staging link. You watch the product grow, not wait for it.
→ weekly staging releasesShip & care
Launch, monitoring and support. The studio stays reachable after the invoice.
→ launch · monitoring · support
Proof, not promises.
/ 012026 · Full-stack
F1 Race IoT Platform
A platform that replays Formula 1 telemetry and processes it in real time. Three independent services — feed replay, event normalization and race state — exchange messages over MQTT, and each is split internally into Domain, Application and API layers. A dashboard follows the race live. The whole system comes up with one `docker compose` command.
- .NET
- C#
- Docker
- Next.js
- Python
- Scikit learn
- TypeScript
/ 022025 · Full-stack
HealthMonitoring
An IoT system for health monitoring, written in four languages because each service solves a different problem: C# handles persistence and migrations, TypeScript event processing, Python analytics and models, Go the sensor generator. Traffic goes through a gateway, MQTT and NATS, and between services over gRPC with shared `.proto` contracts.
- .NET
- C#
- Docker
- Figma
- GitHub
- JavaScript
- PostgreSQL
- Python
- Tensorflow
- TypeScript
/ 032026 · Full-stack
BookSphere
A social platform for readers — book recommendations, clubs and live conversation. Both backend and frontend: Express with layered controllers, services and repositories, a React client on Tailwind, and Socket.IO carrying real-time messages. Three databases behind one `drivers` layer — Neo4j for relationships between readers and titles, MongoDB for content, Redis for cache and sessions.
- Docker
- JavaScript
- MongoDB
- PostgreSQL
- React
- Redis
- TypeScript
The tools I use, and the ones I skip.
I pick a boring, proven stack. Something new gets in only when it solves a problem the old one could not.
- .NET
- C#
- Chrome
- Docker
- Figma
- GitHub
- GraphQL
- JavaScript
- MongoDB
- Next.js
- Node.js
- PostgreSQL
- Python
- React
- React Native
- Redis
- Scikit learn
- Tensorflow
- TypeScript
Three ways to start working.
Fixed-scope build
project-based quoteA defined product, designed and built to a fixed scope and date.
- discovery included
- design → build, one owner
- 30 days of post-launch support
- ★ most popular
Monthly partner
monthly retainerAn ongoing seat at your table — product work shipped every week.
- rolling backlog, your priorities
- weekly releases
- priority response
Design sprint
1–2 weeks · fixed feeFrom idea to a tested, clickable prototype — fast.
- workshop + brief
- hi-fi clickable prototype
- dev-ready handoff
[ Estimator ]
Scope it in 30 seconds.
Estimated timeline
- Discover 1w
- Design 3w
- Build 6w
- Launch 1w
- Team
- Lead + 1 specialist
- Earliest start
- Nov 2026
A fixed price follows within 48 hours of an intro call.
Asked before, answered here.
cloudsheep.devusually replies within a few hours
Can we start next month?
Yes. Book a 30-minute intro call and you get a written brief and timeline within 48 hours.
Is it really just one person?
Yes — one engineer-designer doing the thinking, the pixels and the code. For specialised needs I bring in trusted collaborators, but responsibility never leaves this desk.
Do you do design and development together?
That's the whole point. Nothing gets lost between a designer's file and a developer's build, because they're the same person.
Both iOS and Android?
Yes. Usually one React Native codebase for both stores; fully native (Kotlin/Swift) when the product demands it.
How long does a project take?
A design sprint: 1–2 weeks. A typical product build: 8–16 weeks, shipped in weekly increments you can see on staging.
Who owns the code?
You do — 100%, from day one. Repos live in your organisation; there is no lock-in and nothing held hostage.
Where are you based?
Niš, Serbia (CET) — a comfortable overlap with all of Europe and US mornings. Working languages: English and Serbian.