Start a mobile app development project

An estimate is not a number pulled from experience alone. We take your design files and brief apart into screens and states, add the parts that never appear in a design — authorisation, error handling, data migration, store requirements — and price each of them. That is why an estimate arrives with a breakdown: you can see which parts carry the cost and decide to cut or postpone them before anything is built.

• Design files in any form: Figma, Sketch, Adobe XD, or even screenshots and sketches.
• A brief, if you have one — a page of plain text is enough to start.
• A logo and brand materials, if the product has to follow them.
• Links to products you consider close to what you want, and what exactly you like in them.

That is a normal starting point, not a problem. We estimate the design phase separately and go through research, screens and a prototype before development begins. Designing first is also cheaper: changing a screen in a prototype costs minutes, changing it in a released application costs a sprint.

An estimate in hours and money with the scope written out, a proposed timeline with the sprints named, and the stack we would use with the reasoning behind it. Nothing in it obliges you to work with us, and the document is yours to take to another team for comparison.