About Formudex

Few things, made properly

Formudex exists to build a small number of applications well and then keep them working. The problems worth our time are rarely solved by adding features to something that already exists; they are solved by defining one narrowly enough that it can be answered well, engineering the answer carefully, and then staying with it.

That leads to a company shaped a particular way. We take responsibility for the whole stack rather than assembling something we do not understand. We would rather ship fewer things and build them properly than spread ourselves thin. And we accept that this is slower.

The disciplines behind the work

• Software engineering. Designing systems that can be read, changed and tested by the people who have to live with them, and treating a codebase as something that will be maintained for years rather than shipped once.
• Cloud infrastructure. Running the services behind an application ourselves: deployment, configuration, observability, backups and recovery, with the operational cost of a decision considered before it is made.
• Cybersecurity. Threat modeling before implementation, secure defaults rather than optional hardening, dependency hygiene as routine maintenance, and a published route for reporting problems to us.
• Creative technology. Building systems where the interface, the timing and the feel of the thing matter as much as the data it stores, and where getting that right takes engineering rather than decoration.

These describe the experience the work draws on. Formudex itself is a new company, and we do not claim otherwise.

How we decide

• A defined problem before a line of code. If we cannot state the problem in a sentence, we are not ready to build.
• Narrow scope on purpose. What a product will not do is a design decision, made early and written down.
• Privacy by default. A product collects only what a feature needs, and what data it touches is decided before the code exists rather than described afterward.
• Platform conventions over house style. An application should behave the way its platform behaves, including for accessibility, input and navigation.
• Maintain what we ship. A release is the start of the work, not the end of it, for as long as a product is worth that investment.

Where the company stands

Formudex is currently developing its first application; it has not been announced. Research, design and engineering are under way, and there is no public release yet.

We are deliberate about this. Describing an unreleased product commits us to decisions that are still open, and a company that has not shipped is better served by being clear about what it is than by implying more. When there is a product to describe, it will be described here.

Read how we build, see the full company details or get in touch.