AquaDegrees is my small app for checking water temperature near your location. I shared it again in July, after the Watch-related updates in June. It was already an existing product by then; its first store release was in September 2024.

I like applications whose purpose can be described without a tour. A person has a question, opens the app and gets the relevant information. That does not make the engineering trivial. It gives the engineering a clear direction.

For AquaDegrees, the temperature is the main answer. Location, timing and units provide the context that makes it usable. Everything else has to earn its space around those elements.

A dedicated utility has an advantage over a large information dashboard: it can remember what the user came for. There is no need to pass through several categories or interpret a screen full of unrelated values before reaching the water. The application can be small because the question is small.

There is also a responsibility that comes with that simplicity. A large number in a clean interface can look more certain than its source. I want to distinguish an accessible answer from a false impression of precision. Water conditions can vary, and the way a data source represents an area matters. A temperature should be presented as useful information, not as a guarantee about every part of a beach.

The Watch extension makes the same design question more demanding. On the phone, there is room to inspect context. On a watch face, the value must work in a glance. That is a reason to think carefully about the relationship between the surfaces, rather than build a miniature copy of every phone screen.

Small products also benefit from ordinary maintenance. Correcting a stale display, clarifying an unavailable state or making a permission request easier to understand may have more value than adding another feature. These changes do not always make dramatic screenshots, but they affect whether the app remains dependable in everyday use.

I do not see a narrow scope as a temporary embarrassment to be fixed through expansion. It can be a durable product decision. The app does not have to become a complete weather service to be useful to someone deciding whether to go to the water.

There will always be ideas for adjacent features. The question I would use to judge them is whether they make the original task easier or more trustworthy. If a feature introduces a new set of decisions without improving the answer, keeping it out can be the better design work.

AquaDegrees is satisfying to me because its purpose stays close to ordinary life. A complicated technical chain ends in a short, practical answer. The best version of that experience is one where the person barely notices the chain at all.