Mobile applications
Apps for the phones your users carry, built to feel fast and natural to use. We plan for the details that make or break a mobile product, such as patchy connections, small screens and different devices.
We build web apps, mobile apps and the backend systems behind them, on clean architecture that is easy to extend. Written with care, tested properly and handed over in a state your team can work with.
Software engineering is the work of turning a design into a working product: the screens people use, the servers and data behind them and the connections to other systems. At Fat Elephant it covers web and mobile applications, backend systems, APIs and integrations, performance optimisation and quality assurance.
Six areas of engineering work, used together or on their own. Most products need several of them at once.
Apps for the phones your users carry, built to feel fast and natural to use. We plan for the details that make or break a mobile product, such as patchy connections, small screens and different devices.
Applications that run in the browser, from a focused internal tool to a full customer-facing product. They are built to be quick, accessible and simple to extend as your needs change.
The part users never see: servers, databases and business logic that hold everything together. We design it to be dependable and clear, so it can grow without being rewritten.
We connect your product to the other tools you rely on, such as payments, messaging, accounting or the systems you already run, and we design clean APIs so other products can connect to yours.
Slow software loses users. We measure where time is being lost, in the code, the database or the network, and fix the causes rather than the symptoms.
Testing is part of the work, not a step at the end. We check as we build, test the awkward cases as well as the happy path and fix problems before they reach your users.
Three phases, one team. The people who scope the work are the people who build it, and they stay on after launch.
We start from the scope, the designs and the constraints. We agree the architecture and the order of work, so the first stage is clear and the risky parts are tackled early.
We ship in regular, small releases that you can see and try, rather than one big reveal at the end. Feedback shapes the next step, and testing happens as we go.
We take the product live carefully, watch how it behaves and fix what we find. We stay on to keep improving it, or hand it over cleanly if you would rather carry on with your own team.
Yes. We build web applications, mobile applications and the backend systems behind them, and we can do all three as one project so they work together from the start.
Often, yes. We start by reading it and telling you honestly what state it is in, then agree whether to extend it, tidy it or replace the parts that hold you back.
We test as we build, including the awkward cases, and we release in small steps so problems are easy to find. After launch we keep watching how the product behaves.
Yes. We build on clean architecture and keep the code clear, so your developers can read it, review it and work alongside ours, or take it over.
You will see working software in regular, small releases, so you are judging the real thing and not a progress report. You can steer at every step.
It depends on what is being built and how much has to be connected. Tell us what you are trying to build and we will suggest the right starting point, with a clear scope agreed before any work begins.