2MRWLABS is a small product studio in Bristol. We help teams turn early ideas into mobile apps and websites people return to, then keep them running when the light changes.
We prototype quickly, test with real people, and only then build properly.
Experiments are cheap; finished software is not. So we spend the early weeks learning what deserves to exist, and the later ones making it solid. Everything we try is written down, including the ideas we threw away and why, so the reasoning survives long after the meeting where it was decided.
We work with founders, small companies and teams inside larger organisations who have an idea, a half-working product or a hunch that software could fix something. We design, build, publish and maintain. We do not sell templates, and we do not hand over a product without the means to run it.
iOS and Android products, from first prototype to store release. One cross-platform codebase when it serves you; native Swift and Kotlin when the camera, Bluetooth or background tasks demand it.
Suits products people use often, on the move. Apps in detail
Company sites, content platforms with editors and search, and browser-based tools with logins and data. Fast on modest phones and easy to keep current.
Suits reaching everyone, or testing demand cheaply. Web in detail
Interviews, journey maps, sketches and clickable prototypes tested with real people. We change what confuses them, not what we merely dislike.
Suits new products, or existing ones people struggle with. Design in detail
Developer accounts, store listings, privacy declarations and reviewer notes; domains, certificates and redirects for the web. Then maintenance on a rhythm that suits you.
Suits anything going live, or already live. Launch desk
Illustrative generated image
The studio is registered in Bristol, and most of our work happens remotely: shared boards, recorded demos, written notes. That means you can work with us from anywhere in the UK, and you always have a written record of what was agreed.
Office hours are Monday to Friday, 09:00–18:00 UK time. Meetings in person are arranged in advance.
Every engagement starts with a question worth answering: will people trust this enough to sign up? Is the slow part of the job the one we think it is?
Stopping early is a good outcome if it saves you building the wrong thing.
How we shipDrop your feature ideas into Now, Next or Later. It is the exercise we run in our first workshop, and it works just as well on your own: anything that is not needed for the first release can wait until that release is teaching you something. Nothing is sent to us.
Your ideas are kept on this device only if you accept optional storage.
Shipping is the start of the day, not the end. Tick what applies to your product and the sizer suggests a level of aftercare, with the reasons. It is a rule of thumb, not a quote.
Clear guidance on researching and designing services. gov.uk
Google's design system, useful for Android conventions. m3.material.io
Practical security for small organisations. ncsc.gov.uk
No. A paragraph and a few examples of what frustrates you today is plenty. Shaping the brief is part of the work.
We will tell you if we think a simpler or cheaper route exists, and explain why. You decide.
You do, from day one: repositories, developer accounts and hosting are set up in your name.
Usually. We start with a review of the code, dependencies and release process, then tell you plainly what we find.
Monday to Friday, 09:00–18:00 UK time.