MediWb
Because Your Health Deserves Clarity
The problem MediWb solves
Fully working frontend and backend deployed in vercel
Which link is given below https://frontend-pi-seven-72.vercel.app/
- Search for Medicines (Text or Voice):
Just type or speak the medicine/disease name.
2.See all pharmacies near your current location.
3.Ask AI Chatbot for Health Guidance:
Describe your symptoms.
Get instant suggestions, precautions, and when to see a doctor.
Accessibility: Voice-based search helps people who are not tech-savvy (esp. rural Odisha).
Better Healthcare Access: Connects people to the nearest pharmacy/doctor quickly.
All-in-One App: Combines features (medicine search, maps, chatbot, prescriptions) instead of using 3–4 different apps.
Challenges we ran into
- Google Maps API Key Issue
While integrating Google Maps for showing nearby medical and pharmacy stores, we faced multiple issues related to API keys. The key restrictions and billing setup became a major blocker.
As a solution, we switched to an open-source maps API for location and nearby search, which required adjustments in our existing code.
- Voice Input Integration
Implementing voice input for searching medicines was challenging due to browser compatibility issues and accuracy in speech-to-text conversion.
Debugging required testing on multiple browsers and handling background noise problems.
- Backend and Chatbot Integration
We connected a chatbot for handling queries with the backend using the Gemini API. The API responses and authentication setup took extra time, and integrating it smoothly with the frontend was complex.
We faced debugging issues with async calls and data handling between frontend and backend.
- Frontend Styling and UI Issues
Since we wanted our website to look like a professional medical platform, matching the styling (colors, typography, responsiveness) was a challenge.
Debugging CSS conflicts and ensuring a consistent design across devices took significant effort.
- Team Collaboration Problems
While working in a group, merging each other’s code often led to version conflicts.
Debugging frontend styles after merging and resolving Git conflicts was time-consuming.
- FAQs Section
While building the FAQs section, we had issues with proper structuring of data and ensuring expand/collapse functionality worked smoothly on both desktop and mobile views.
- Final Submission Issues
During project submission, we faced last-minute bugs in responsiveness and integration, which required urgent debugging before final upload.
Technologies used