Show HN: Wordminos – Crosswords Meet Dominos (wordminos.com)
I built a daily word game in 12 days.
The base mechanic only took an hour. Getting it to the finish line took the rest.
The work was in iteration: design, polish, juice, character. Taste, for now, is still relevant.
Enjoy!
10 comments
[ 0.21 ms ] story [ 10.0 ms ] thread- Adding a mascot(s) helped immensely for creating an identity / making it not another puzzler
- Tuning the puzzle generation constraints: how frequent 2-,3-,4-,5- size pieces are, how many shared colors, how colored markers are laid out relative to one another in the board, all helped tune the puzzles from not being outlandishly difficult or mundanely boring.
One thing I would say is that when there is a "done" or a "next" button, it took me a sec to see it as a button because the actual button color was too close to white on my monitor. So I thought it was a click anywhere kinda "done".
Webgames have really evolved far and away past what you may imagine them being able to support
This was actually my first entirely agent-coded, no code read game i made (in 20yrs of coding)
The timeline is here: https://wordminos.com/making-of/timeline.html
My main contributions were the polish, design, character, packaging ideas
I'd really be interested in seeing more about your "no code read" development process. Not worried about things like incorrect local storage writes? Or patterns that will be difficult to modify later when making changes?
Edit: Also, tech stack? Did you choose the tech stack? Or just let AI choose?
I chose the “tech stack” but it wasnt much in the way of direction: plain js and webgl, cause i planned to have that be wrapped for ios and android after