Case
BehaViewer
Concept and UX for a tool that shows where people linger in public space: from the pitch for partners to the first coded prototype.
Prototyping
From an idea to a clickable tool in the browser within a week – with real data, before anyone commissions development.
What a prototype is
A prototype is the first version of a tool you can click: a configurator, a product finder, a customer portal, an internal form. It runs in the browser, shows real content and answers the question a presentation cannot: does this work?
A sketch shows
what something looks like.
A prototype shows
whether it holds.
In a week instead of a quarter
I build prototypes myself, with code and AI tools. That means a conversation on Monday becomes a tool on Friday that you can test with customers, staff or management. Where data exists – a product catalogue, a price list, a public data service – the prototype works with the real values.
Example Behaviewer: a data-collection app for observing public spaces, from concept to clickable flows built with real components, before a single line of production code was written.
What happens next
The prototype is not the product, but the basis for it. You receive it as a running file and as a specification: flows, states, data fields, open questions. With that, your IT, your agency or a development partner can make an offer that is accurate – because everyone has seen the same thing.
What you gain
- Confidence: decide on a tool, not on a slide
- Speed: five working days from idea to clickable state
- Cost: development is commissioned once it is clear what will be built
- Involvement: experts and customers test early, while mistakes are still free
- Handover: a specification any developer can work from
How I work
- Conversation: what should the tool do, for whom, with which data?
- Structure: flows, screens and states as a sketch, sign-off on day two
- Build: prototype in the browser with real or realistic data
- Test: with two or three people from the target group, adjustments the same day
- Handover: running file, specification and a recommendation for implementation
What you get
- Clickable prototype in the browser, with real data where it exists
- Test with two or three people from the target group
- Specification: flows, states, data fields, open questions
- Recommendation for implementation
- Duration
- 5 working days
- Production
- Prototype by me; production code afterwards by your IT, your agency or a development partner
Elements I work with
- Clickable prototype in the browser
- Configurator and product finder
- Portal and internal tool
- Real data from interfaces
- User test
- Design system
- AI-assisted variants
- Specification for development
and more
Examples
- Cases on this page
- 3
- Fragments
- 9
Case
Login
New information architecture for login.org: young people find their career, taster apprenticeship and apprenticeship in six career worlds.
Case
Excellence Cruises
A website that lets you feel a river cruise before you book it: from the brand core and three navigation routes to a home page in motion.
Fragments
9Slides from presentations of these projects
Tell me about your idea: what should the tool do, and who will use it?