Products
We build around work people actually need to do. We remove what gets in the way, test what remains, and keep refining it after launch. The aim is software worth keeping.
Our approach
Understand what someone is trying to accomplish before choosing the technology. The difficult parts belong inside the product, so the person can get on with the work.
Give each feature a job to do. Keep the choices that help, remove the ones that distract, and make the remaining decisions carefully.
Read, measure, and try a small version. Research should challenge an idea before it becomes a feature, and help us see whether it actually improves the work.
Corrections, compatibility, and support are part of making a product. We plan for the care it will need once people begin to rely on it.
Patina, in practice
Time and use are part of the making.
A material earns its patina through use and care. Software earns something less visible: better judgement, careful corrections, and the trust of the people who return to it.
That makes maintenance a design choice. Preserve the work people have already done. Keep familiar things dependable as their surroundings change. Let each update make the product more useful over time.
Current product
An IO Patina Product
Preparing for release
Write in Markdown without feeling like you're writing code.
You want to write a document you can keep using. Markdown gives you a simple file that can move between apps, but its syntax can make an ordinary writing task feel technical.
SeamText lets you read and edit that file as a formatted document. Concentrate on the writing while your work stays in ordinary Markdown, ready to open in other editors and tools.
When we share
Products appear here when they are close enough to release that we can speak about them with confidence. The same care that goes into making them goes into deciding what we say.