[trailrunner46]

Congrats on the launch. As a fellow elixir enthusiast I wanted to say nice work integrating the client side and pulling this together, you are doing a ton of stuff all at once. I don’t have a use case right now but still will poke around to see what you have built!

[urs]

Thank you, to be honest Abinsthe and Apollo go together incredibly well.

I think coming from Rails and switching out controllers for resolvers made adjusting to building SPAs far easier. I still think building routing on the client side feels strange, but it’s way easier when GraphQL just gives you one endpoint to hit and with Apollo you just query exactly what you need.

[trailrunner46]

Yes, Abinsthe is quite incredible! I have used it with react and vue and had some success. However lately whenever liveview is the right fit I find myself fist pumping all over the place. Something magically about writing most of your code in elixir and only sprinkling JS when needed. Your site is very ui heavy so I imagine it needs to have a lot of js strictly client side so a SPA makes sense (I just find the mental overhead of having to deal with a js framework front end and a elixir backend tricky).

[urs]

Yeah the original application borrowed heavily from our first product which predates LiveView so we stuck with what we knew. Our first product actually predates contexts and schemas in Phoenix. We started working on it around the time Phoenix was deprecating models from 1.2 to 1.3.

LiveView is incredible, but I haven’t used it enough to know the shortcomings. From the outside looking in, it does seem nice to work with a view that’s already nicely coupled with the app.

[trailrunner46]

Makes total sense, I only used LiveView for a new project that I started within the last year, I can imagine it being tough to only use a little bit in an existing app, especially if its SPA hitting an api. Cool to see you evolved as Phoenix evolved.