tirumalaraoa7890

Today I focused on improving the Admin flow and data management UI. I fixed the form behavior so after saving medicines or stock, the form resets correctly and allows adding multiple entries without reloading the page.

I then completed the View Medicines page where medicine and stock data are shown together. Each stock batch is displayed separately, even if the medicine is the same. I added color-based status handling: expired stock shows in red, completed stock in blue, and available stock in green, ordered in the same priority. I also added a delete option to remove specific stock entries from localStorage.

At this point, the Admin module feels stable and usable

oday I focused on the Admin module. I built admin login with two-step verification (OTP) and added simple animations with emoji-based error messages. Then I created an Admin dashboard and clearly separated actions into Add Medicine, Add Stock, and View Medicines.

I completed the Add Medicine feature by storing only medicine master data (name, dosage, timing, unit, cost) and decided to handle expiry separately in stock. I also implemented unit-based pricing (tablet / ml / packet), added image preview support, and prevented duplicate medicine IDs using localStorage.

I paused development after testing the Add Medicine flow.
Next step: Add Stock page (expiry & quantity).

Today I worked on the medicine data structure part of my project Mediq – Multilingual QR-Based Medicine Information System.

I clearly defined what information a medicine must contain when tablets are sold loose, such as:

Medicine name

Company / manufacturer

Expiry date

Dosage and usage

Warnings and instructions

This structure is designed so that all details can be accessed through a QR code, even without the original medicine strip.

Today I focused on planning the complete structure and GUI flow of my project instead of jumping directly into coding.

I finalized the three main roles in the application:

Admin – manages medicine data (name, image, usage, timing, expiry)

Shopkeeper – searches medicines, adds them to bill, and generates a QR code

Customer – scans the bill QR to view medicine details

Today I completed the full README documentation and designed the complete structure of my project QRX.

The project clearly defines the problem of loose tablet safety and provides a QR-based solution with:

• Admin-controlled medicine management
• Emoji-based medicine timing (before/after food for morning, afternoon, and night)
• Multilingual support (English, Telugu, Hindi)
• Voice-assisted medicine guidance using text-to-speech
• Clear separation of Admin, Shopkeeper, and Customer roles

I also set up my development environment in VS Code and configured Hackatime to track my work.
Next, I will start implementing the UI and core functionality step by step.