So, I am around a large crud app that is split into a login app and the other actual business logic apps for authenticated users.
My ideal way to handle this division would be to implement the login using server side rendering and routing, and then implement the actual business logic apps as a regular elm SPA, but then that introduces two places where html and css need to be organized. So, you would have to replicate the branding across those two areas.
Some other alternatives:
Implement the login app as a small separate SPA
Use some advanced method of doing server side rendering with Elm
I like server side rendering and routing for the login portion of the app because it lets you reuse existing libraries for auth, and seems conceptually simpler.
Let’s speculate that react and python is the most popular combination right now. Do you think teams using that combination typically use flask auth with server side rendering and then navigate to react apps that rely on the authentication being established and injected?
I think that speculation is unrelated to whether your login page is separate from your main app. I’ve been on large (many hundreds of thousands to millions of loc, React, Ember, Elm, etc) apps that do both approaches, with a variety of backends.