What we shipped this month: geocoding, IP, time zone and more
A roundup of recent work across the API: new compatibility hosts, faster time zone and elevation lookups, dashboard features, and clearer quota visibility.
Dark mode for the dashboard
Some preferences are small and still worth getting right. Dark mode is now available across the client dashboard, a setting anyone can switch on from their account preferences whenever they prefer working against a darker interface, whether that is a matter of taste, lighting conditions, or simply what feels easier on the eyes during a long session.
Turning it on changes the appearance of the dashboard itself, the interface where usage stats, invoices, API keys, referrals, two-factor authentication and coupon codes all live. It does not touch anything about the API. Requests, responses, quota headers and pricing behave exactly the same regardless of which theme the dashboard happens to be set to, since dark mode is purely a matter of how the account management interface looks, not how the API behaves.
The setting lives alongside language preferences in the same part of the dashboard, both aimed at the same idea: the tools around an API should adapt to how someone prefers to work, rather than asking everyone to work the same way. Switching between light and dark is immediate and can be changed back at any time without losing any other setting or preference tied to the account.
The clearest case is also the most common one: checking a quota counter or a key's status at night, often on a phone, while debugging something that broke outside business hours. A bright white dashboard in a dark room is a small but real friction in that moment, and it is exactly the kind of friction dark mode removes without requiring anyone to explain why it matters.
We treat interface details like this as worth doing properly rather than as an afterthought, even for a company whose core product is an API rather than a visual application. A dashboard is still the place most people interact with My Geocode directly, checking a key, reviewing an invoice, or watching a quota counter during a busy day, and small comforts there add up over repeated use in a way that is easy to underestimate.
None of this required touching how the API itself is built or served, which is part of why it shipped as a straightforward account preference rather than a larger project. The dashboard and the API are separate layers by design, so a visual setting on one side never has any bearing on request handling, quota accounting or pricing on the other.
If you spend meaningful time in the dashboard, whether managing keys for a team or just checking in on usage periodically, dark mode is available now with no separate signup or feature request needed. It is a setting, not a plan tier or an add-on, available to every account exactly the same way.
Account settings, including dark mode and language preferences, are reachable from /dashboard at any time.