Family1st
A GPS tracking app for the Family1st device. A map-first redesign that turns a dense data tool into a calm, guided experience, with live device status, easy activation, and real-time tracking.
Overview
Family1st is a GPS tracking app for the Family1st hardware device, built for families and vehicle owners across the US to keep eyes on the people and cars they care about, under the promise "unlock peace of mind: monitor your loved ones anytime, anywhere." This was a full redesign of a live product for the client Family1st at Sieva Networks Solutions. The old app worked, but it buried its one job, showing you where someone is, under a wall of raw data. The redesign puts the map first, makes the numbers readable, and turns a utilitarian tracker into a calm, branded product with guided setup, clear device states, and Light, Dark, and System themes.
The Challenge
This was not a blank page. The product already existed and already had users, so the work was a rescue, not an invention. The old app opened onto a dim map with clip-art cars and a dense panel of values, battery, mileage, speed, fuel, direction, packed into small text with a row of unlabeled icons underneath. The one question that matters, where is my vehicle or my person right now, competed with everything else and often lost. Navigation was spread across top-bar icons and a menu that mixed a product tour with logging out. Status was a timestamp that could say "71 days ago" with nothing to flag that anything was off. The task was to keep every capability the power users depended on while making the whole thing legible, trustworthy, and simple to set up for a first-time owner.
And the obvious read, the one the whole team started with, was that the app was simply cluttered, so the fix was to tidy the data panel. That assumption is where the research began, and it's the first thing the data overturned.
Research & Insight
Because real people were already using it, the redesign started with their behaviour, not guesses. I went through analytics, heatmaps, conversion rates, and drop-off across the core journeys to see where attention went and where people quit, and I ran sessions with stakeholders, the product manager, and actual users to fill in the why.
Here's the part that mattered. We all walked in with the same assumption, that the app felt cluttered, so the culprit was the dense data panel, and the plan was basically to clean it up and call it a redesign. The data disagreed with all of us. Attention and usage clustered on one thing, the map and "where is my vehicle right now." The panel we were about to build the entire redesign around, people barely touched it. So the real problem wasn't a messy panel. It was that we'd buried the one thing people actually came for.
From there a few things were clear.
The map is the product, and it was being treated as wallpaper. People open a tracker to see a location, so the map should own the screen.
Density was hiding the data. When everything shouts at once, nothing reads. The numbers that matter needed hierarchy, not more room.
Setup was where new owners fell off. Activating a physical device, the IMEI, the subscription, the first drive, is the riskiest moment, and it needed a guided path.
Status has to be a state, not a timestamp. "71 days ago" tells you nothing at a glance. "Vehicle moving" or "low battery" tells you everything.
The app had a logo, not an identity. Trust in a safety product is visual, and consistency was missing.
I stayed honest about the evidence too. Behavioural data is strong on what people do and weak on why, and heatmaps show where attention lands, not intent, so I leaned on the user and stakeholder sessions to explain the behaviour rather than guess at it. And since the data came from existing users, I treated the riskiest calls as things to confirm, not settled facts. The lesson underneath the whole project: when what people say and what they do disagree, believe the doing, and pressure-test your own assumption before you design against it.
Product Strategy
Every move here came straight from the research.
Map first, data second. The map is the product, so lead with a full, high-quality map and a live device pin, and tuck the details into a light card that opens when the owner wants them.
Guided activation. Since setup was where new owners fell off, a step-by-step flow, scan or type the IMEI, verify, activate, set up the subscription, and a "drive the vehicle" moment that explains the ten-minute GPS acquisition, so the hardest part of onboarding stops being a dead end.
State you can read at a glance. Because status has to be a state not a timestamp, running, moving, low battery, and last-updated are carried by color and words together, so the map answers the question before you read a number.
One structured home for power features. Geofencing, trip history, track history, reports, and multi-device management move into a clear menu grouped by purpose, instead of scattered icons, so the density stops hiding the data.
A real identity, and a choice of skin. Trust in a safety product is visual, so a cohesive blue and yellow system, product photography, and Light, Dark, and System themes make it feel like a product people trust with something that matters.
Experience Architecture
The structure puts the research into flows, map first, setup guided, power features grouped.
Getting started. Onboarding states the model in one line, sign in, scan the back of your device, track your people, and a theme picker lets the app match the phone. Login and signup stay clean and standard.
Setup. The add-device flow scans the barcode or takes an IMEI by hand, verifies it, and hands off to activation and subscription (Monthly, Quarterly marked Best Value, or Annually), a payment and order summary, and the "drive the vehicle" modal that sets expectations for the first ten minutes.
The daily hub. A map-first dashboard with the live pulsing pin and a device card showing speed, address, movement, and battery. A side menu organizes everything into Dashboards (Map, Devices, Contacts, Settings), Tracking and Reports (Geofencing, Trip History, Track History, Report, IP Log), and Other Links (Alexa, Online Manual). A bottom bar keeps the map, trips, location, and account one tap away.
Managing it. A devices sheet handles multiple trackers at once with filters and per-device status, Trip History filters by date, driver, and data points, My Account holds profile, security, devices, and subscription, and Units let owners choose distance and fuel economy.
Interface System
The visual system carries the core finding into pixels, the map is the hero, and everything else earns its place quietly.
From clutter to calm. The dense old panel gives way to a card-based system with real spacing and a clear type hierarchy, so a screen that used to shout now guides.
Blue and a yellow pin. A bright blue carries the brand and its actions, and the yellow location pin, the mark from the logo, becomes the app's signature, the thing your eye finds on every map.
Status in color and words. Green for running and moving, red for low battery and alerts, always paired with text, never color alone.
A live pin that breathes. The device marker pulses to signal live tracking, the clearest possible way to say "this is happening now," which the old app could only imply with a timestamp.
Theme-aware by design. A full Light, Dark, and System palette, chosen up front rather than bolted on, so both the map and the chrome hold up in every mode.
What changed, in short:
Map: a muted backdrop → the hero of the screen
Data: a dense grid of raw values → a light card with clear hierarchy
Status: a stale "71 days ago" timestamp → live states (moving, running, low battery)
Navigation: scattered icons and a catch-all menu → a purpose-grouped menu plus a clean bottom bar
Setup: dropped straight into tracking → a guided scan, activate, and subscribe flow
Identity: a logo on a default map → a full blue-and-yellow system with Light, Dark, and System themes
Live feel: implied by a timestamp → a pulsing pin that shows tracking in real time
Outcome
Family1st was rebuilt end to end, from a dense utilitarian tracker into a calm, map-first product, with the work grounded in real usage data rather than taste. Making the map the hero and giving the numbers hierarchy lifted engagement about 25% across the core journeys. As Lead UI/UX Designer at Sieva Networks, I ran the redesign with one designer reporting to me and stayed embedded with the product manager and the development team from the first audit through to the final build.
The moment that captures the role best wasn't a screen. The developers couldn't get the live pulsing pin to behave, so rather than hand the interaction over and hope, I sat with them and traced the failure to its actual source, separating whether the problem lived in the design, the interaction, or the code. Once that was clear, I wrote a working solution and passed it to the team to implement, and the pin shipped. That's the through-line of this project, a designer who owns the outcome past the mockup, into the data that justifies it and the code that makes it real.
