Stage 01 / 04 · Observe
Start with the plant
Photo-based identification and disease diagnosis connect the mobile client to an analysis service. Live soil readings add environmental context.
Photo + soil readings → insights
Visual + sensor inputsCase study · № 005 · 2022 to 2023
FLORAGENIC · understand the plant, then care for it
A mobile plant-care ecosystem connecting visual diagnosis, live soil readings, products, nurseries, gardeners, payments, and ongoing care.
Mobile + AI + IoT
The central idea
The scan is only the beginning.
01The problem
Plant care is fragmented across species research, disease diagnosis, soil readings, supplies, local nurseries, and professional help. Beginners often discover problems only after visible damage appears.
Interactive field notes / system map
Explore the plant-care loop
Conceptual walkthroughSelect a stage ↓
Stage 02 / 04 · Understand
Make care information accessible
Species, care, growth, and treatment information give the user a way to interpret the plant and its environment.
Analysis → care information
Mobile service integrationStage 03 / 04 · Act
Connect care to a next step
Products, nursery discovery, and gardener booking extend the journey beyond diagnosis into practical care actions.
Care need → product / nursery / gardener
Commerce + servicesStage 04 / 04 · Connect
Orchestrate the mobile experience
The React Native client coordinates GraphQL, Firebase, payments, images, sensors, and the analysis service across the care journey.
Mobile client ↔ connected services
Client and integration workProduct flow · simplified for this case01 / 04
Insight should lead somewhere useful.
02The mobile product
- Authentication, profiles, gardeners, nurseries, store, cart, wishlist, orders, and payments.
- Photo capture and upload flows for identification and disease-analysis services.
- IoT sensor views for moisture, temperature, and acidity data.
- GraphQL product data, Firebase storage/database, and Stripe checkout.
- Location-aware discovery and booking surfaces for nurseries and gardeners.
03Decisions that mattered
01One care journey.
Diagnosis is more useful when the next actions, products, readings, or people are in the same product.
02Mobile owns the orchestration.
Hashaam's public code shows the client coordinating GraphQL, Firebase, payments, images, sensors, and the analysis service.
03Authorship stays precise.
The public Flask/TensorFlow repository's commits belong to a collaborator, so this case claims Hashaam's mobile client and integration work, not sole authorship of the ML backend.
04Outcome
The public repository documents a substantial React Native client across commerce, service booking, plant scanning, and IoT workflows. The current case study presents a broader product vision; scale claims are intentionally omitted until they can be independently supported.