A small studio with an unfashionable rule

Why on-device

Most modern apps are a thin client around a server. That is a reasonable default for a social product and a poor one for a utility: your screen time, your photo library and your scanned documents are not things that need to travel.

Keeping computation local costs us speed, binary size and a certain amount of engineering comfort. In exchange the apps work on a plane, have no upload limits, no per-page pricing and nothing to breach. When a user asks "where does my data go", the honest answer is a short one: nowhere.

What we ship

Three Android apps, all live on Google Play. ScrollBreakis a screen-time breaker that interrupts doom-scrolling with a short mind-refresh instead of a hard block. ReelRoll plays your gallery as a private reel feed and includes a non-linear video editor that renders locally.ScanLocker turns paper into searchable, password-protected PDFs with on-device OCR.

CafePOS is the exception to the on-device rule: a cloud point-of-sale for cafes, quick-service restaurants and fine dining, with billing, orders, tables, inventory, customers and reports in one place. A shared counter and kitchen need shared data, so it is a connected service by design. We wrote about that trade in why an on-device studio builds a cloud POS.

Native iOS builds of ReelRoll and ScanLocker are in development. We would rather ship one app that behaves correctly on a platform than two that almost do.

How we work

The catalogue is deliberately small. Every additional product is another surface to keep secure, another policy to maintain and another support inbox — which is why we would rather improve what exists than keep adding to it.

Releases follow the Play Store's requirements properly: a changelog per version code, a signed bundle from a key backed up off-machine, and a privacy policy that is updated before a data-touching feature ships rather than after. It is unglamorous, and it is most of the job.