Inspiration
The problem is lack of centralized appointments which led to an entirely preventable emergency airlift and emergency hospitalization.
What it does
- An MVP of a scheduling Progressive Web App (PWA).
- User footprint and setup is minimal, most modern devices still usable should be able to download it and if not use the web version. Worst case scenario, clinic can hold some cheap rental devices that can run a PWA to loan out.
- Locally stored appointments (iOS will need regular weekly refresh) adds robustness to inclement weather knocking out internet infrastructure. (In theory, can't test in timeframe)
- Once fully refactored, maintenance should be minimal ## How we built it Due to having to solo this, a lot of Claude and vscode copilot was used followed by extensive and fast testing. ## Challenges we ran into
- I have never REALLY done this form of full stack development ## Accomplishments that we're proud of
- Capable of being downloaded
- UI although a bit messy is fairly intuitive and has a fair amount of safeguards
- Theoretically able to cache locally (no server setup in time yet)
- Centralizable and scalable ## What we learned
- Svelte existence and setup
- True power of node.js ## What's next for Clear Appointments
- See slides :p
Log in or sign up for Devpost to join the conversation.