I dont know if LiveView is easy to learn though, maybe easy to learn the happy path, but when things are outside the normal path, things can be hard to figure out/understand, even when they know the basic HTTP stuffs.
At least thats been my experience with it ~3months back. I was familiar enough with elixir/phoenix/channels to source dive and figure out whats happening, and today i know liveview well enough to avoid the weird interactions, but I imagine it can be a pretty miserable experience for beginners to start with.
@hdra did you capture your LiveView experience somewhere e.g. a learning log (blog post). I would love to read it as I’m sure everyone in the Phoenix team would. Thanks!
Brain dump some bullet points as an outline that you can later expand on. You have no idea how helpful it will be to other people including your future teammates. ;-)
At first I had validation on an email input field after a day all text is put through..
I'll have to look into it next week.
The validation lines are still in de code but don't seem to work.
It's probably something stupid.
For now the website is live. I used a single db table for everything. Later I'll do it the proper way. I couldn't find an easy example how to add more complex systems.
I used gen.auth and this comes with multiple tables. I guess there is a way to gen it in ecto. But is there also a gen for a basic liveview crud, which can be changed. This way new users start with something, otherwise you start from a void.
I'm not going petal yet. I'll first try without A. I'll probably have to use it in a month when I have to integrate a js library(Html5-QRCode).
At least thats been my experience with it ~3months back. I was familiar enough with elixir/phoenix/channels to source dive and figure out whats happening, and today i know liveview well enough to avoid the weird interactions, but I imagine it can be a pretty miserable experience for beginners to start with.