Apps
Everything published under the SnowyLakes developer account, and everything being built toward it. Each page covers what the app does, the mechanism behind it, and the decisions that shaped how it behaves — and where an app is not on a store yet, its page says so.
Know how they feel
An Android app that turns a short clip of your dog into a structured read: one of six affective states, a real confidence score, the observable cues behind it — and an honest refusal when the clip isn't good enough.
Real confidence scores — never simulated
Clear when it knows. Clear when it's close.
aiRef keeps score for racket-court games from an event log that is only ever appended to. Four-corner calibration runs a real projective solve and refuses a degenerate corner set with a typed reason rather than a garbage mapping, and the rules companion answers from on-device digests, citing the pack and section — or abstaining and naming the packs it has.
Confidence draws as a level — never as a number or a percentage
Know why you're pinching it
Pinch is a grow log for people who actually garden. Ninety-seven plant types each carry what pinching that specific plant buys you, care tasks fire off the day you put the plant in the ground rather than a generic month, and the plant doctor answers a photo with a shortlist and the signs you must go and confirm yourself.
Answers arrive as a shortlist with reasoning — never one confident name
Check the code before you trust it
A QR scanner that works out where a code actually goes before you open it — resolving the redirect chain as a phone, reading the destination's HTML and certificate, and reconciling Google Web Risk, content and AI signals into one plain-English verdict.
Dangerous needs corroboration — never a single weak signal
The template
One shared template renders every app page, and a section only appears when the app genuinely has that thing. There are no empty states and no coming-soon panels.
Each page opens with the problem the app was built for, before a single feature is mentioned.
The pipeline the app actually runs, annotated with the filenames, functions and values it runs on.
Each app has a point at which it declines to answer rather than invent an answer. That moment gets a section of its own.
Client, backend, data and third parties, layer by layer — including the parts with no interface at all.
Support & privacy
Every app page links to support and to a privacy policy, and an app with a policy of its own gets a URL that does not move. All of them are static pages that resolve whether or not the app has shipped.
