I Thought I Was Designing a Map… Until I Learned I Was Actually Designing a System.

Discovering Geofencing After days of research, I came across Geofencing.

Geofencing is a technology that creates a virtual boundary around a physical location using GPS coordinates.

Whenever a vehicle enters, exits, or stays inside that boundary for a defined period, the system can automatically trigger actions.

Those actions could include:

• Sending notifications

• Updating trip status

• Recording arrival and departure times

• Alerting operations teams

• Triggering business workflows

Suddenly, everything made sense

I wasn't trying to build a map anymore.

I was designing how an intelligent system should behave. Thinking Like a UX Design Engineer

This was the point where my mindset started changing.

Instead of asking:

"How should this screen look?"

I started asking:

• What event triggers this notification?

• Which user should receive it?

• What happens if GPS accuracy drops?

• What data should be stored?

• How should the interface respond while the system processes the event?

Those questions weren't just about design.

They were about system design. Understanding the System Behind the Design

One of the biggest lessons from this project was realizing that every interface is backed by a system.

In this case, the flow looked something like this:

Vehicle moves → GPS detects location → System checks geofence → Business rules run → Database updates → Notifications are sent → Dashboard refreshes