My own app!
- 6 Devlogs
- 3 Total hours
It’s very personal to me:Sick Bay is a healthcare support application designed to make it easier for users to access basic health information and get guidance when they are feeling unwell.
Ship #2
Today I fixed the broken-heart icon in Sick Bae’s header and corrected the error that was stopping the app from building for the web. I also set up automatic deployment through GitHub Actions. The latest build passed, and the app is now available for anyone to view at https://gdiva-blip.github.io/Sick-bae/. I’m going to change the app launcher icon in the next devlog, byeeee!!!!
Today I continued developing Sick Bae and focused on improving the health-guidance experience. I added a Get Help option so users can access additional support from health personnel instead of relying only on information provided by the app. I also connected this into the health guidance flow and removed the old timezone/world-clock screen because it wasn’t central to the app’s purpose. I ran flutter analyze and got No issues found, then committed and pushed the changes to GitHub. I also spent time troubleshooting Hackatime because my recorded coding time isn’t matching the amount of time I’ve actually spent working in my Code space. The tracker is installed and configured, but my dashboard is currently showing significantly less time than expected. I’m continuing to investigate this while working on the app. To be honest, it’s really frustrating because I spend hours sometimes but currently, my entire projects has just two hours logged like what the heck! The app is now further along and I’m continuing toward a polished, review-ready demo.
Ok. So today, I tried to setup the project for multiple platforms including Android, iOS, macOS, Windows and web. Still not done though. I fixed some Git issues and got my repository back to a clean state. Then, I redesigned the home screen since they’re a limited number of symptoms. So instead of choosing from already existing symptoms, users can describe what’s actually wrong with them hence the “What’s going on section”. It stills doesn’t really give feedback which I’ll continue tomorrow. The best part of today is that; I confirmed that the deployment worked and was able to install the preview on my PC. Oh yeah and the world clock feature isn’t really necessary. I was just trying something, even forgot to add a devlog on that.
At first, I didn’t understand the concept of a demo url so my demo url just kept taking me back to the readme file on my repository, but my reviewer drew my attention to it. I fully understood it and worked on it : Demo readiness. I set up and verified Linux desktop support. Cleaned up the flutter project and got flutter analyze passing. Verified the app could actually build and run. Addes flutter web support so the app could be demonstrated from my code space. Built the web version successfully. Served the web build through the code space. Configured a forwarded demo url so someone outside my code space can access the actual app. Verified that the url opens the Sick-bae interface and not just the GitHub ReadMe. Prepared the project for reviewer recertification. https://gdiva-blip.github.io/Sick-bae/
Ship #1
I’m working on the symptoms tab; trying to add features
I worked on developing SickBae;an application designed purposefully for students, to help them acess basic heath info and get guidance when they aren’t feeling well. This is to say, in the school environment during their hectic schedules. I’m working on improving the app’s design and user experience
