Single file including all html/js/css, Vanilla JS, no backend, scores persisted with localStorage.
Deployed using ubuntu/apache2/python/flask on a £5 Digital Ocean server (but could have been hosted on a static hosting provider as it's just a single page with no backend).
Images / metadata stored in an AWS S3 bucket.
A dermatologist a short while ago with this idea would have to find a willing and able partner to do a bunch of work -- meaning that most likely it would just remain an idea.
This isn't just for non-tech people either -- I have a decades long list of ideas I'd like to work on but simply do not have time for. So now I'm cranking up the ol' AI agents an seeing what I can do about it.
Focusing on "but security lol" is a bad take, IMO. Every early attempt is bad at something. Be it security, or scale, or any number of problems. Validating early is good. Giving non-tech people a chance is good. If an idea is worth pursuing, you can always redo it with "experts". But you can't afford experts (hell, you can't even afford amateurs) for every idea you want put into an MVP.
MVP means just enough engineered code to solve a problem, rough around the edges and lacking features sure, but not built by someone who has literally no idea what they were doing.
Prototypes of physical products are never put into production and sold to consumers. Unfortunately software prototypes "run", and are sold at that point. Then they begin to scale, and the inherent flaws in their design are amplified. The same thing used to happen with MS Access apps; the same thing still happens with "low code" solutions.
The engineers cost just as much after the prototype phase, but if you don't hire them to build your MVP then you never have one.
Everyone wants to pretend that the software used to be better, but the reality is that MVPs and sometimes even public launches were always a house of cards.