iamcare ZA: The technical side
I built iamcare ZA as my passion project after getting the idea from a designer friend on a design/development forum many years ago. This is the nth iteration. Each iteration a massive improvement on the previous. This is the first one which I am happy with start to finish :)
The application itself had to be as accessible as possible, so technologies were carefully curated in an attempt to make the application available to as many people as possible, and leverage known and stable browser technologies instead of reinventing the wheel.
Because I am a solo developer I also wanted to keep costs low, thus I opted for something that can run on the simplest of hosting packages at a marginal cost.
From a safety standpoint, the choice was made to only use social logins as to not store sensitive information. The application is also built with quite a few behind-the-scenes guardrails to try and keep users' privacy at the forefront: Cross-Site Request Forgery (CSRF) protection, Content-Security-Policy (CSP), Feature-Policy, and a few others.
The application and pipelines have been set up in such a manner that if iamcare is to be rolled out for a different country, that process is a painless as possible. More information about that can be found in the README.
iamcare ZA is and will remain completely free.


Replies