hipstapas
Create passphrases with ease from anywhere in a second!
After the creation of hipstapas.core npm package, changed the code for the API to use the newly created npm package.
There was a slight problem with the validation, but at the end all problems were solved, the API uses the npm package and the validation works as expected.
Lessons learned: upgrade your own json-validation to use proofed json-schemata validation libraries :)
Extracted the core functionality (validation and generation of passphrases, uuids, dice-passphrases with EFF wordlists and random numbers) into a npm package - hipstapas.core - and published it to npmjs: https://www.npmjs.com/package/hipstapas.core.
The course of 100 days of tech startup is over!
Achievements:
🚀SaaS is up and running
🐶Constantly in use by @keenthinker 😃
📣Got some feedback after announcing in HackerNews/IndieHackers/ProductHunt
💛Learned so much in/from the 100dots community!
Stay tuned! 🎤
Offering an API is always chalenging regarding preview and documentation. In order to make at least the preview easier, a playground section was added to the site, where the API features can be explored interactively and the result can be seen instantly without writing any code or requests at all. You are more than welcome to give it a try - https://hipstapas.dev/playground - and tell me what you think.
After 80 days since the start of the idea implementation, the MVP is finally online. A couple of hours every week after day job, the product took shape and grew steadily. All the important options (including documentation) are there and are ready to be used:
🔐passwords
🔑uuid
🆒EFF wordlist
It is always important to visualize, plan and document from the beginning the product that one is creating. Couple of weeks after the start, the mind map with the options of the product was created (https://hipstapas.dev/images/PasswordAsAService_MindMap_Features.png).
A product that serves sensitive information, must gain the trust of the users. This is how the product vision - TRUST - was born:
🔹Transparent (open source)
🔹Reliable (hosted in the cloud)
🔹User-friendly (0 configuration and it just works)
🔹Secure (no analytics, no cookies)
🔹Trustworthy (certified by the crowd)
All this helped enormously the implementation.
Repetative tasks should be automated as much as possible. Once the recurrent password change came again, I though it would be a good idea to have a modern service for new passwords, so that this can be automated. That is how hipstapas SaaS war born.
Comment