Implementation Tradeoffs

Pros:

• No dependencies beyond Google Maps + FontAwesome.
• Highly performant — vanilla JS and CSS.
• Responsive and touch-friendly.

Cons:

• No state management for deep-linking or history.
• API key exposed unless restricted by referrer or proxy.
• Markers and data hardcoded — no dynamic backend.

Good Fit For:

• Small-to-mid scale internal or public campus locator apps.
• No user-authenticated sessions or complex state.
• Can be progressively enhanced without heavy frameworks.

Could Improve:

• External config/data source (JSON or API endpoint) ?!?
• HIDE API key security (via server proxy or referrer restrictions)
• Marker clustering at scale (>50 markers) (chose to keep Houton for Reference)
• TypeScript typings for stricter safety.
• User.Primary Campus auto select
• Query the user's location via share location for closes campus.