Skip to content
The RadarNav mark and wordmark above three phones: navigation, the map of reports, and friends on the road.
01

RadarNav

Year
2026
Disciplines
Brand IdentityMobile AppsProduct DesignWeb Development

The road, together

Every driver in Podgorica already knows where the cameras are, roughly. What they know less well is what changed this morning: the mobile radar on the boulevard, the queue behind a breakdown, the stretch where somebody has just seen a patrol. That knowledge exists, in the heads of the drivers who went past five minutes ago, and it has nowhere to go.

RadarNav is where it goes. A driver reports what they see in two taps, the next driver down that road gets the warning, and the map remembers only as long as the report is true. It is a studio product end to end: the name, the mark, the app on both phones, the backend, and the site that explains it.

Platforms: iOS, Android and the web
Languages, in the app and on the site
Countries with fixed-camera data
Taps from seeing it to reporting it
Three phones: the community feed, the map of reports around Podgorica, and turn-by-turn navigation with a camera alert.

A mark that points somewhere

The identity is a radar sweep with an arrow inside it: the scope says what is around you, the arrow says which way you are going, and the app is the meeting of those two ideas. The wordmark is set lower-case and heavy, and it ends on a lime full stop that is the same lime as the search button, the progress bars and the pulse under your position on the map.

The palette is a forest green that reads as calm at a glance and a lime that is reserved for the few things that should catch the eye. Every report kind then gets its own colour — camera green, radar violet, police blue, hazard amber, drone teal, traffic red — and that colour follows it from the pin to the feed to the alert on the route.

  • #18291FInk
  • #254D38Forest
  • #C6F36BLime
  • #F7F8F2Canvas
  • #7250B8Radar
  • #2563ADPolice
  • #B65D16Hazard
The new-report sheet with six report kinds, beside the account screen with contribution progress.
The six kinds of report on radarnav.me, each with its own colour.
Six kinds of report, the same colours in the app and on the site.

RadarNav informs, it does not detect. It shows only what drivers and public documents have published, so you slow down in time and stay at the limit the whole way, not just past the camera.

No. 1 free app on the App Store in Montenegro
The friends sheet with per-friend colours and switches, beside the map following a friend at 72 km/h.
Twenty seconds of a real drive: a camera alert, then friends on the road beside you.
The map in light mode and in dark mode, side by side.
Light and dark share one palette; the map and every pin are redrawn for each.

One product, two stores, one site

The app is Expo and React Native with a single codebase for iOS and Android, Convex for the shared reports, votes, replies and friends, and Clerk for accounts. Ownership, expiry and counters are decided on the server, never trusted from the phone, and moderation is real rather than decorative: report, block and ban, an objectionable-language filter on everything people type, and a flag queue an admin actually reads.

It went live on the App Store in September 2026, with Android in closed testing on Google Play. The copy took as much care as the code: a store listing that leads with driving at the limit, not with avoiding anyone, and screenshots that never show a speed over the sign.

The radarnav.me home page in dark mode: “Know the road ahead.” beside two phones.

The site at radarnav.me is Next.js dressed in Cherry, with a theme that mirrors the app's colour tokens one for one so the two can never drift. It speaks the app's eleven languages with no prefix in the URL, has no backend of its own, and moves with GSAP only for readers who have not asked it to hold still.

The radarnav.me home page on a phone, in dark mode.
The radarnav.me home page on a tablet, with the app beside the headline.
The same page on a phone and a tablet.
Next project

Inspector Lab

View case study