Sahara Pet Care

Project cover

Architecture

Flutter clients use Provider for app state. Firebase Auth identifies users; Firestore stores pets, caregivers, bookings, and orders. FCM handles push; Maps and Geolocation support discovery and live tracking.

Product gallery

A focused snapshot of the key screens and flows from this build.

The Challenge

Pet owners need a single place to discover caregivers, manage pets, book services, shop for products, track orders, explore adoption options, and communicate with caregivers. Sahara was designed to bring these workflows into one cross-platform mobile experience.

The Solution

I built Sahara as a Flutter app backed by Firebase services. The app includes authentication, caregiver discovery, pet profiles, booking flows, favorites, adoption, shopping, cart and order workflows, chat models, notifications, and location-based features. The goal was to create a mobile-first product with clear user flows and maintainable state management.

Technical Implementation

The application uses Flutter, Dart, Material 3, Firebase Auth, Cloud Firestore, Firebase Messaging, Provider state management, Google Maps, geolocation, Cloudinary media handling, shared preferences, and modular screens, services, models, providers, widgets, and utility layers. State is organized across modules for authentication, bookings, pets, caregivers, favorites, location, and cart management.

Outcome

Sahara shows my ability to work beyond web development by building a cross-platform Flutter/Firebase application with 6 major workflows and a 5-stage booking lifecycle involving automation, active service tracking, geolocation, and Google Maps integration.

What I learned

• Modeling Firestore collections for read-heavy caregiver lists forced clear denormalization rules.
• Keeping booking state in a dedicated provider reduced cross-screen bugs in long flows.
• Treating maps and geolocation as optional degradation paths improved cold-start reliability.