You can use w2ui with phoenix - normal phoenix controllers with w2ui and some json services to fetch data for w2ui. If you are comfortable with w2ui and can build rapidly - go with it.
I had supported a team who used OJET with phoenix.
All you have to do is to fit in the phoenix life cycle.
Phoenix framework as I see it has different parts to it:
- Ecto: ORM kind of thing for talking to database with help of changesets
- phoenix_html: to generate html and forms in templating like EEx, Heex
- Sockets & Channels: Realtime communication using websockets.
- Phoenix.js : javascript library to connect to phoenix sockets and channels.
- Controllers and Views: Phoenix views (some call it dead views). It’s the plain old server side rendering of web pages like Ruby On Rails, JSP, Django, etc.
- phoenix_live_view: Phoenix LiveView enables rich, real-time user experiences with server-rendered HTML. It shifts development from javascript to elixir world. You can get away with writing less javascript. It uses websockets from point 3.
Phoenix does not ship a js library like w2ui or jet,etc. It can work with these libraries as long as they fit the phoenix life cycle of Phoenix Views and Phoenix Live Views.
Except for Phoenix Live View, everything will work out of box without any issues (with w2ui). You don’t need Phoenix Live View if you are building SPA kind of pages with w2ui or Jet.
You can use 1-5 based on your requirements with w2ui and build web apps. As I see it - few Phoenix views, json services and w2ui are all you need.
