Andreas Petrovits

03

Fjorten

Concept, brand & prototype

A customer service app for food trucks, built to turn everyday orders into a picture of who is buying what, when and where. I took it from concept through brand to a working prototype as the sole designer.

Client
Fjorten
Year
2026
Role
Sole designer — concept to prototype
Status
Case study in progress
Screen 01 — order intake
Screen 02 — customer patterns
Screen 03 — day summary

The brief

[Two or three sentences on the starting point: who the client was, what they had, and what was actually broken. Name the constraint that shaped everything — a deadline, a legacy system, a regulation, a team of two.]

The problem

[What the user could not do. Be specific and concrete — "SME owners had to assemble emissions data from four spreadsheets and a PDF from their energy supplier" beats "reporting was difficult".]

My role

[What you owned versus what you inherited or collaborated on. Say plainly if you were the only designer.]

Research artefact — interview notes,
competitive audit, or the old flow annotated

Caption: what this shows and what you concluded from it.

Early sketches or the first
flow diagram

Caption: what changed between this and the final direction.

Process

01

[Discovery]

[What you did, who you talked to, how many. One insight that changed the direction — the moment you learned something you did not expect.]

02

[Structure & flows]

[The decision you made about information architecture or the core flow, and the alternative you rejected. Rejected options are what make a case study credible.]

03

[Interface & system]

[Components, design system, handoff. How you kept it consistent, and what you had to compromise on to ship.]

Wireframe
Prototype state
Final screen
[One sentence a client, PM or user actually said — or the single sharpest insight from the project.]
— [Name, role, company]

The design

[Walk through the two or three decisions that matter. For each: what the user needed, what you did, and why that solution over the obvious one.]

[Keep it to the decisions you would defend in an interview. Everything else is a screenshot.]

The main view — the screen a food truck owner opens first
The one flow that makes the app worth opening

Caption: what the visitor should notice here.

Empty state / onboarding

[What this state solves]

Edge case you solved

[Why it mattered]

Outcome

[What shipped, when, and what happened after. If you have numbers, use them. If you do not, say what changed qualitatively and be honest that it is early.]

[00%][What this measures, and over what period]
[0 wks][Time from kickoff to beta, or another honest process metric]
[00][Users, screens, components — something real you can point to]