Berv-Care
Overview
I built Berv-Care from the ground up, bringing location-aware healthcare discovery, authentication, content and data tools into one responsive application.
Berv-Care helps users find healthcare providers around them, search other locations and access useful healthcare information from one interface.
I owned the build across frontend architecture, component design, authentication, data storage, maps, testing, analytics and deployment.
Location was central to the product, not just another feature.
The core experience needed to do more than display nearby hospitals. The application had to resolve the user's location, respond to place searches and keep provider results and the map aligned as that location changed.
It also needed to support authentication, healthcare content and data exports without each feature introducing its own way of managing state and data.
Keep location, server state and UI responsibilities clear.
I structured the application around reusable UI and feature-level components, keeping location logic, asynchronous data and presentation concerns separate where it made sense.
Rather than treating the map as an isolated component, I made location part of the wider application flow. Current location, place searches and provider data all work from the same source of location state.
Coordinating browser APIs, external services and application state.
I built the application with Next.js and TypeScript. Firebase handles authentication and persisted content, Google Maps powers the mapping experience, and the browser Geolocation API provides the user's current position.
React Query manages asynchronous provider and location-dependent data, including loading, caching and refetching as the active location changes. use-places-autocomplete provides Google Places suggestions for location search.
React Markdown renders stored Markdown content, while PapaParse handles CSV generation for supported data exports. Keeping these integrations behind clear component and data boundaries made the rest of the UI easier to reason about.
What's running underneath.
Framework
Next.js · TypeScript
UI
Tailwind CSS · GSAP
Data & Auth
Firebase
Maps
Google Maps API
Geolocation
Browser Geolocation API
Server state
React Query
Place search
use-places-autocomplete
Data export
PapaParse
Testing
Jest · Testing Library
Analytics
Vercel Analytics
Testing the behaviour users depend on.
I used Jest, Testing Library and jest-dom to cover key components and user-facing behaviour. I focused the tests on what a user can see and do rather than tying them to internal component implementation.
Several product flows working as one application.
The finished product brings location-aware discovery, place search, authentication, healthcare content and data export into one consistent experience.
Building it end to end also forced decisions beyond individual components: where state should live, how third-party integrations should enter the application, what needed to be reusable and how new features could be added without making existing flows harder to maintain.