Devlog 9

finally done. literally coding until my fingers are numb. completed the entire crm frontend and the desktop wrapper is fully functional. no more mock gaps or missing files.

here is the breakdown of what happened:

frontend modules (crmfrontend):

• finished the pharmacy inventory page (pharmacyinventory.tsx). it handles full batch tracking, manufacturing/expiry dates, cost/selling price margins, gst calculation (5%, 12%, 18%), and hsn codes. also threw in reorder level alerts when stock drops below threshold.
• built out pharmacybilling.tsx from scratch. doctors write rx, pharmacist pulls it, builds the bill with automatic gst and prints receipt.
• made pharmacycustomers.tsx to track loyalty points, lifetime spend, and outstanding balances. has a quick reminder trigger.
• wrote pharmacyprescriptions.tsx to handle the incoming doctor prescription queues. pharmacists can do complete or partial dispensing if we are short on stock.
• added pharmacypurchase.tsx for restock orders and supplier inventory ingestion.
• built pharmacyreports.tsx for tracking medicine usage patterns and monthly sales dashboards.
• all routes are auth-locked in app.tsx using role-based routing policies (doctor, pharmacist, receptionist, admin, super-admin).
• styling is built using vanilla tailwind classes alongside shadcn UI components like dialogs, tables, and dropdown menus for layout consistency.
• data fetching is managed using tanstack react-query to cache active lists and handles state mutators for adding/editing items.
• toast notifications via sonner trigger real-time updates for pharmacy sales completions and out of stock warnings.
• integrated standard currency formatters to display indian rupee values properly in all tables.

desktop wrapper (auracaredesktop):

• spun up electron setup. main.js manages window dimensions (1400x900 min, resizable) and ipc communication channels.
• preload.js sets up contextbridge and ipcrenderer exposing window controls safely without opening nodeintegration.
• connection strategy:
  • in dev, package.json uses concurrently and wait-on to launch the frontend dev server on port 8080 and then point the electron browser window loadurl to localhost:8080.
  • for prod, we run electron-builder which bundles our assets. npm build script builds the react frontend, copies dist to desktop/frontend-dist, and main.js loads it locally via loadfile.
• configured cross-platform packaging target options for windows (nsis installer, portable executables), mac (dmg, zip), and linux (appimage, deb) in package.json.
• added native OS window hooks for minimized, maximized, and close events so client-side buttons in the custom titlebar work.
• added shell handler for opening external web links in native browser instead of electron window.
• assets folder holds local icons configured for specific OS packing rules (ico, icns, png).

how it connects:

• the desktop shell is just a container running our react client, which talks to the node/express backend via api client calls to VITE_API_URL.
• ipc communication checks the app version and process platform.
• window actions (minimize, maximize, close) are wired back to the ipcMain handler.
• if backend is unreachable, the API services default to local mock fallback data so the app does not freeze.
• auth tokens are saved in localstorage inside the web view which carries over across app launches.

took way too long to align the dist copy paths in the build script. had a dumb bug where frontend-dist was missing and loading a blank screen, but fixed the cp target path. compilation is completely green now. going to collapse.

Devlog 8

coded for 10 hours straight. brain is absolutely fried but got most of the core pages done.
the lopsided progress is finally balancing out. frontend is starting to talk to the backend client.

made some serious headway:

• user-management.tsx: admin controls, user activity graphs, and session tracking. shows average response times and role badges.
• billing-finance.tsx: invoice lists, revenue breakdowns (upi, cash, card), stats, and mock trends.
• pharmacy/pharmacy-customers.tsx: mapped patients to pharmacy profiles. tracked loyalty points and total amount spent, plus warning badges for outstanding dues.
• app.tsx: wired up all the protected routes and role permissions. admins, doctors, pharmacists all see different stuff now.

what’s left:

• pharmacy-inventory.tsx is half-baked. literally stopped at line 65 state declaration because i needed a break. need to add medicine batch dialogs, GST calculations, and stock levels.
• missing pharmacy-prescriptions.tsx, pharmacy-purchase.tsx, and pharmacy-reports.tsx files completely. they’re imported in app.tsx but the files don’t exist on disk yet. build will crash if i try to compile right now.
• actual integrations testing with the express backend. right now it falls back to mock data if the local server isn’t running.
• need to build the electron wrapper for desktop and expo for mobile later.

everything is coming together. the app finally feels like a real crm instead of just a bunch of empty files. going to sleep now.

Project Screenshot

The attached screenshot is ai generated as the final devlog will contain demo link to try website yourselves.

Devlog 7

Worked a lot more on it and progress so far :

• Chart
• Checkbox
• Collapsible
• Command
• Context menu
• Dialog
• Drawer
• Dropdown Menu
• Form
• Hover Card
• Input otp
• Input
• Label
• Menubar
• Navigation Menu
• Pagination
• Popover
• Progress
• Radio Group
• Resizable
• Scroll Area
• Select
• Separator
• Sheet
• Sidebar, Skeleton, Slider, Sonnar, Switch, Table
• Tabs, Text Area, Toast, Toaster, Toggle-Group, toggle, Tooltip
• Use toast, Roles, auth context, use mobile, use toasts, use debounce
• Api, utils, Analytics, appointments
• billing, billing finances, compliance security.

Devlog 6

So far so good, made a whole lot of progress :

• Overall Dashboard Layout completed
• Header, Sidebar, Accordion created
• Alert Dialog, Alerts & Aspect ratio completed.
• Avatar, Badge, Breadcrumbs
• Buttons
• Calendar
• Cards
• Carousel.

around 20% frontend work finished.

Devlog 5

Progress so far :

• Finished Doctor Dashboard
• Pharmacy Dashboard
• Receptionist Dashboard
• SuperAdmin Dashboard (In progress)

Devlog 4

Okay so progress so far :

• Built the login system flow.
• Defined the different variations of dashboard based on role.
• Admin Dashboard menu.
• Controls for each role seperately divided.

Functionalities :

• added search patients functionality.
• Appointments list design and function.
• Modules overview
• Quick Actions
• Revenue Charts
• StatsCard
• Upcoming reminders
• Admin Dashboard
• Diagnostic Dashboard
• Doctor Dashboard

For now everything is just plain frontend that contains mock data and no actual working.
will take more work to finish this.

Devlog 3

Looking so far so good. worked for about 1 & half hour now and it’s looking promising. worked on login page and menu design and style (will improve more with theme customization).

Worked on role management and how each role will be handled differently.

Found out bugs here and there, will fix after i’m done with creating the dashboard menu and style.
It still needs about 10-15hrs of code based on the speed i’m working with (not sure if it’s less or more).

Debugging and implementing new features will also require time.

Devlog 2

Been Working for whole night with backend. I have made quite a lot of progress, so far so good. Almost everything that backend will need to operate is done and what’s left of it is to actually test it out.
Now after a few more checks i’ll get ahead to code the actual frontend and the design of site.

After the frontend is entirely created, i’ll test out all the backend functions and see if those works or not & if needed I might’ve to work on backend too as I go along this road………..

Devlog 1

Needed a crm that actually works for hospitals without the usual bloat. decided to split it into clean micro-services: node/express backend, react front, electron for desktop, and expo for mobile.

most of the core structure is there but progress is pretty lopsided. spent a bit of time spinning up the backend and database routes, barely touched the actual frontend pages. focus is to get all the backend api endpoints and role validations completely solid before moving on to the ui. cross-device communication is just going to be rest calls to the centralized node server.

Updated Bot’s repo & project to contain link to directly try out bot instead of just youtube video. Updated deployment method to also contain guide for pm2. Specified ai usage in readme.

you can try the bot here : https://app.slack.com/client/E09V59WQY1E/C0B95V123TQ

been working on the zerox slack bot transition. struggled with event subscriptions and socket mode on the dashboard since it kept asking for a request url — had to toggle socket mode first to bypass it. also had to invite the bot to the channel manually to get app_mention to trigger. rewrote the parser to clean the mention tag, colons, and spaces because it was throwing a fit and fallbacking to help menu. ran into background instances of node load balancing socket mode connection, killed them with stop-process to get it working. ask and roast commands updated to show the original prompt at the top. cleaned up deploy.md and slackbot.service for root systemd deployment.

Finally made the first draft for it.
bot is up and working.
I was clueless at first on what to create for project on hackclub & then just made slack bot as it will give me idea on how things work.
It was different and unique experience compared to discord bot developing (Which I mostly works on).