IoT
Location intelligence
B2B utility
Geofencing tool - GeoFenz
A geofence is a simple idea — draw a boundary, get notified when something crosses it. Building the tool that lets anyone draw that boundary, for any reason, is the harder problem. GeoFenz was designed as a general-purpose geofencing capability rather than a product tied to one use case, and that generality is why it ended up serving asset tracking, fleet management, and kids-tracking clients without being rebuilt for any of them.
Role
UI/UX design, led design
and development
Platform
Mobile + Web
Used by
Asset tracking · Fleet management · Kids tracking
Deliverables
Cross-platform geofencing tool
01 - The problem
Most geofencing tools assume the user already knows what they want to fence — the exact perimeter, the right radius, the correct shape. In practice, that’s the hardest step: a warehouse manager, a parent, and a fleet operator all hit the same wall before they even start, because defining “where” is harder than defining “what happens there.”
GeoFenz was built around removing that friction at the primitive level — draw, save, alert — so the tool would work for whoever needed it, without requiring GeoFenz to know who that was.
02 - Key features as design decisions
i) Draw geofence — one interaction, two shapes
Users can draw either a circular radius or a custom polygon directly on the map using the same interaction model — place, adjust, confirm. Keeping both shapes under one interaction pattern avoided fragmenting the experience into two modes.
iii) My Places — a reusable library
Saved locations live in a categorized hub — home, office, warehouse, school — so applying a geofencing rule to a known place takes one tap instead of a redraw. This is what makes the tool durable rather than a one-time setup task.
ii) Frequently visited place — removing the hardest step
This is the strongest decision in the product. Instead of asking users to know where to start, GeoFenz uses historical location data (via Places API and open-source location APIs) to detect frequently visited locations and proactively suggest a geofence around them — turning a blank-map problem into a one-tap confirmation. It’s the feature that makes the tool feel intelligent.
iv) Geofence alerts — four trigger types
Alerts can be set for entering, exiting, staying more than 1 hour, or staying more than 6 hours. Each toggles independently, so the same control panel supports a parent watching for arrival/departure and an operator watching for dwell time, without a separate configuration mode.
03 - The design decision worth remembering
Frequently Visited Place reframed how the whole tool should work. The default assumption in geofencing UX is that users arrive with a plan — they know the place, the shape, the trigger. That’s false for most casual users, who have a need but no starting point.
Detecting intent from behavior and surfacing it at the right moment — rather than waiting for the user to initiate — is a pattern that extends well past geofencing. It’s the difference between a tool that waits to be operated and one that meets the user partway.
04 - Outcome
GeoFenz shipped as a mobile and web platform and is used across asset tracking, fleet management, and kids-safety contexts. The tool wasn’t purpose-built for any one of them — it was built as a flexible geofencing primitive, and its reuse across three verticals is the clearest evidence that the underlying design held up without needing to be reshaped per client.
NEXT PROJECT
Vision - Atomic Design System
View
IoT
Location intelligence
B2B utility
Geofencing tool - GeoFenz
A geofence is a simple idea — draw a boundary, get notified when something crosses it. Building the tool that lets anyone draw that boundary, for any reason, is the harder problem. GeoFenz was designed as a general-purpose geofencing capability rather than a product tied to one use case, and that generality is why it ended up serving asset tracking, fleet management, and kids-tracking clients without being rebuilt for any of them.
Role
UI/UX design, led design
and development
Platform
Mobile + Web
Used by
Asset tracking · Fleet management · Kids tracking
Deliverables
Cross-platform geofencing tool
01 - The problem
Most geofencing tools assume the user already knows what they want to fence — the exact perimeter, the right radius, the correct shape. In practice, that’s the hardest step: a warehouse manager, a parent, and a fleet operator all hit the same wall before they even start, because defining “where” is harder than defining “what happens there.”
GeoFenz was built around removing that friction at the primitive level — draw, save, alert — so the tool would work for whoever needed it, without requiring GeoFenz to know who that was.
02 - Key features as design decisions
i) Draw geofence — one interaction, two shapes
Users can draw either a circular radius or a custom polygon directly on the map using the same interaction model — place, adjust, confirm. Keeping both shapes under one interaction pattern avoided fragmenting the experience into two modes.
ii) Frequently visited place — removing the hardest step
This is the strongest decision in the product. Instead of asking users to know where to start, GeoFenz uses historical location data (via Places API and open-source location APIs) to detect frequently visited locations and proactively suggest a geofence around them — turning a blank-map problem into a one-tap confirmation. It’s the feature that makes the tool feel intelligent.
iii) My Places — a reusable library
Saved locations live in a categorized hub — home, office, warehouse, school — so applying a geofencing rule to a known place takes one tap instead of a redraw. This is what makes the tool durable rather than a one-time setup task.
iv) Geofence alerts — four trigger types
Alerts can be set for entering, exiting, staying more than 1 hour, or staying more than 6 hours. Each toggles independently, so the same control panel supports a parent watching for arrival/departure and an operator watching for dwell time, without a separate configuration mode.
03 - The design decision worth remembering
Frequently Visited Place reframed how the whole tool should work. The default assumption in geofencing UX is that users arrive with a plan — they know the place, the shape, the trigger. That’s false for most casual users, who have a need but no starting point.
Detecting intent from behavior and surfacing it at the right moment — rather than waiting for the user to initiate — is a pattern that extends well past geofencing. It’s the difference between a tool that waits to be operated and one that meets the user partway.
04 - Outcome
GeoFenz shipped as a mobile and web platform and is used across asset tracking, fleet management, and kids-safety contexts. The tool wasn’t purpose-built for any one of them — it was built as a flexible geofencing primitive, and its reuse across three verticals is the clearest evidence that the underlying design held up without needing to be reshaped per client.
NEXT PROJECT
Vision - Atomic Design System
View
IoT
Location intelligence
B2B utility
Geofencing tool - GeoFenz
A geofence is a simple idea — draw a boundary, get notified when something crosses it. Building the tool that lets anyone draw that boundary, for any reason, is the harder problem. GeoFenz was designed as a general-purpose geofencing capability rather than a product tied to one use case, and that generality is why it ended up serving asset tracking, fleet management, and kids-tracking clients without being rebuilt for any of them.
Role
UI/UX design, led design
and development
Platform
Mobile + Web
Used by
Asset tracking · Fleet management · Kids tracking
Deliverables
Cross-platform geofencing tool
01 - The problem
Most geofencing tools assume the user already knows what they want to fence — the exact perimeter, the right radius, the correct shape. In practice, that’s the hardest step: a warehouse manager, a parent, and a fleet operator all hit the same wall before they even start, because defining “where” is harder than defining “what happens there.”
GeoFenz was built around removing that friction at the primitive level — draw, save, alert — so the tool would work for whoever needed it, without requiring GeoFenz to know who that was.
02 - Key features as design decisions
i) Draw geofence — one interaction, two shapes
Users can draw either a circular radius or a custom polygon directly on the map using the same interaction model — place, adjust, confirm. Keeping both shapes under one interaction pattern avoided fragmenting the experience into two modes.
ii) Frequently visited place — removing the hardest step
This is the strongest decision in the product. Instead of asking users to know where to start, GeoFenz uses historical location data (via Places API and open-source location APIs) to detect frequently visited locations and proactively suggest a geofence around them — turning a blank-map problem into a one-tap confirmation. It’s the feature that makes the tool feel intelligent.
iii) My Places — a reusable library
Saved locations live in a categorized hub — home, office, warehouse, school — so applying a geofencing rule to a known place takes one tap instead of a redraw. This is what makes the tool durable rather than a one-time setup task.
iv) Geofence alerts — four trigger types
Alerts can be set for entering, exiting, staying more than 1 hour, or staying more than 6 hours. Each toggles independently, so the same control panel supports a parent watching for arrival/departure and an operator watching for dwell time, without a separate configuration mode.
03 - The design decision worth remembering
Frequently Visited Place reframed how the whole tool should work. The default assumption in geofencing UX is that users arrive with a plan — they know the place, the shape, the trigger. That’s false for most casual users, who have a need but no starting point.
Detecting intent from behavior and surfacing it at the right moment — rather than waiting for the user to initiate — is a pattern that extends well past geofencing. It’s the difference between a tool that waits to be operated and one that meets the user partway.
04 - Outcome
GeoFenz shipped as a mobile and web platform and is used across asset tracking, fleet management, and kids-safety contexts. The tool wasn’t purpose-built for any one of them — it was built as a flexible geofencing primitive, and its reuse across three verticals is the clearest evidence that the underlying design held up without needing to be reshaped per client.
NEXT PROJECT
Vision - Atomic Design System
View