MediSearch Website – Project Story ✨ Inspiration
This idea hit me the moment I realized how confusing it is for normal people to look up medicines. Half the time, pharmacies give substitutes, and we just nod like we fully understand the difference. I wanted to build something simple, old-school reliable, and genuinely helpful — a place where you type a medicine name and instantly get clear info.
Basically, I built the site I wished existed when I googled a tablet and got 500 ads instead of one solid answer.
📚 What I Learned
This project leveled me up in a bunch of ways:
How APIs work for fetching real-time medicine data.
Structuring clean frontend logic using HTML, CSS, and JavaScript.
Handling asynchronous functions — because JavaScript loves giving you promises more than results.
Organizing search results in a simple, traditional format that humans can actually understand.
Most importantly, I learned how to turn raw data into something meaningful for people.
🛠️ How I Built the Project
I kept the whole workflow clean and structured:
Planning: Decided the core goal — user types a medicine → website returns detailed info like uses, dosage, side effects, substitutes.
Frontend Setup: Designed the UI using HTML and CSS, keeping it simple and familiar so anyone from students to grandparents can use it.
Logic & Functionality: Used JavaScript to:
Capture the search input
Fetch data from a medicine database/API
Display the results neatly
Handle errors like “no medicine found” or empty searches Testing: Checked multiple medicines, invalid inputs, slow networks, and weird edge cases.
Deployment: Hosted the website using GitHub Pages / Netlify so anyone can access it anywhere.
⚠️ Challenges I Faced
No project comes without its villains:
Finding a reliable medicine API that didn’t rate-limit me into oblivion.
Handling inconsistent data formats — some medicines had full details, some acted like they didn’t exist.
Managing UI display issues because CSS loves drama.
Making sure the search was fast and didn’t freeze the page.
Deployment errors where GitHub pretended it “didn’t see” my files.
But hey, every bug fixed = +10 experience points.
🎉 Final Thoughts
This project showed me that even a simple idea can make a real difference. A clean search box, accurate info, and a smooth UI — sometimes that’s all people need. And I’ll be honest: watching the whole thing come together felt chef’s kiss.
I’d absolutely expand this in the future with features like voice search, reminders, or even a full mobile app.
Log in or sign up for Devpost to join the conversation.