Best workflow between JS Frontend w/ Elixir backend as a solo-dev?

That would break the ‘solo’ project, right?

Having done a quite large solo project myself, I did regret it not being LiveView. The additional setup for SSR, API mapping etc was quite time consuming. Also the JS world has the awkward habit of hypes and breaking changes. Svelte might soon be a no-go once the JS framework train moves further.

However, when you really want to go the JS frontend route, the combo Absinth + Apollo is great. GraphQL provides some flexility and easier mental model (imho) while working on a separate backend and frontend.

Ps. The reason JS devs are cheaper is mostly because the language is popular and basics easy learned making for a good stream of newbies. It’s not a bad thing perse, but remember that 100x a cheap rate is more expensive then 20x a higher rate.

I have been in that hell as a solo developer.

Rails + AngularJS
Rails + EmberJS
Phoenix + vanilla Javascript

Then LiveView appeared, and I immediately switched to it the first day it was publicly released.

LiveView is the way to go. You will save tons of time. Less overwhelm. Less frustration. Simpler. More productive. Happier.

Agree with what they said! ^^

LiveView has been making leaps and bounds, not just with performance tweaks but in areas which some might have considered weak points for this type of tech.

Have a look at things like Surface - A component-based library for Phoenix LiveView and 🍿 LiveMotion - High performance animations for Phoenix LiveView and when you really must have a SPA/heavy client based JS, then you could use Hologram - full stack isomorphic Elixir web framework alongside Phoenix!

Personally I would go LiveView first and then (use it/Phoenix with) Hologram and then something like Svelte if I really really had to (tho in that case I would probably really be needing something WASM).

This is jmo, ultimately just go with your gut

Maybe a hybrid approach?

Using Svelte in your Phoenix App? I ran across GitHub - nikokozak/svonix: Render Svelte components in Phoenix views. · GitHub a while back. Did not try it but could be interesting.

Would you know how this library works? No SSR? What are the limitations?

I absolutely love LiveView, but as OP said… it’s hard finding an Elixir dev; it’s much easier finding a frontend JS dev.

Even with LiveView, I’m not a very good frontend dev. It might make more sense for me to make a GraphQL backend, then let a frontend dev work their magic in React or Vue or whatever is popular these days.

I do not think you should choose elixir for your project if your another developer knows nothing about it.
Elixir is just a tool but not a goal.

It just compiles a svelte component where you can treat it like a component or partial. The interop between live view and this library doesn’t exist so you have to prevent it from updating when using live view. As for SSR, I think not since it’s a JS component, but I’m not certain.

Exactly my issue. I love Elixir as a backend but I want to be able to have someone come in and work with the front end because I am really not that good at, nor do I like, the front end.

Too much css & tears, too little time.

What I would go with is

• Single repo, unless there’s a REALLY good reason to separate them out. Just makes following changes easier.
• Use Phoenix with NPM. You can still use esbuild, but you can also easily install all the other NPM packages you might need.
• Pick whatever frontend framework that makes sense. I’ll defer to advice by other’s here. I love Vue myself.