First, I think Hyperapp can make both small and big applications, opposed to u/PufPufPuf's opinion. A lot of people have this opinion because they are more familiar with v1's wired-in actions, which can become quite unruly. In the latest version, actions are decoupled, and can be organized/extracted however you see fit.
I've made a handful of applications in both v1 and the current released Hyperapp, and they work very well. If you want to see the latest Hyperapp in action, you can check these out:
- A timer for mob programming: https://github.com/mrozbarry/mobtime
- A canvas game, using Hyperapp for dom/state: https://github.com/mrozbarry/smash
- A router for Hyperapp: https://github.com/mrozbarry/hyperapp-router
I have a handful of older youtube videos regarding v1, you can check them out here:
- Intro to Hyperapp (v1): https://youtu.be/uWIyjI8nkz0
- Hyperapp (v1) forms and localstorage: https://youtu.be/qpt6aaMxm1E
- Unit testing hyperapps (v1): https://youtu.be/5wvPUj--HaA
Note, they are outdated, but there isn't much on youtube about Hyperapp in general.
One thing to keep in mind is the naming. A lot of people talk about "Hyperapp" as the first version, and "v2" as the current version, but this is wrong. It's more like "v1" (legacy) and "Hyperapp" (current). It gets confusing, because not everyone is on the same page with that, but this the the naming Jorge (primary author/creator of Hyperapp) has mentioned several times.