I think the Elixir ecosystem still lacks good documentation (beginner-friendly, guides, recipes), courses, example projects, and bootstrap projects. For web developers, seamless frontend integration with UI rendering libraries like React or Vue is also needed.
MatteoGauthier
cschmatzler
- working language server
- better linting. Styler is getting there, but it’s an internal tool without configurability
- focus on accessibility in the ecosystem. There’s not a single component library out there that gets even 5% there
- better database tooling. Automatic schema diffs and migrations that work with plain Ecto would be a great start
- analytics
6
cmo
hubertlepicki
No. And I appreciate the suggestion. I looked at it several times, and I know some good people that enjoy it very much.
From what I saw, I did not like it at all. It seems very resource-oriented, i.e. database driven. Which is also what Rails by default is, to be fair. You define schema and it creates you all sorts of interfaces on top of it, which is great for some apps but in my experience it’s often a trap for larger, more complex systems. A ticket to make a small UI change can turn into a huge endevour because your schema and more importantly - data - does not fit the use case anymore. I would love something with UX-first approach, that operates on the level of Forms and validations and Workflows that take in forms and perform actions if the forms are valid. I’ve been using this approach for both Rails and Phoenix apps for almost two decades now and it’s IMHO much better than building the app around your database schema, especially if you derive functionality from it.
2
lud
dimitarvp
Any examples, reading through which would help us understand what exactly were you doing, in coding terms?
0
hubertlepicki
We’re probably getting off topic here if we go this way very much. Should we start another thread? That’s more of a thoughts about software architecture in general than Elixir specific. I don’t know what’s the forum policy on these discussions.
1
dimitarvp
Please do. I am super interested in this. I am quite sick of most DB<->language barrier libraries that I’ve seen in all my career. Looking for something else. I have ideas but I need to refine them by discussing with others.
1
bartblast
Creator of Hologram
Thank you @mau013 for mentioning Hologram! 
@woylie - You’re absolutely right about placing Hologram in the isomorphism category rather than local-first applications. While Hologram currently focuses on isomorphism by automatically transpiling server code to JavaScript for client-side execution, my roadmap includes building a client-side database solution. This will essentially be a wrapped IndexedDB that synchronizes with the server database when online, handling schema consistency, migrations, and other database management aspects automatically.
@dimitarvp - Your vision of a cross-platform UI framework aligns well with Hologram’s long-term goals. I’m working towards a single codebase solution that can deploy to web, mobile, and desktop while reusing UI components. Hologram already implements inter-component messaging, allowing components to communicate with each other. While I don’t yet have a supervision system, it’s on my roadmap for future development.
@hubertlepicki - Your description perfectly captures Hologram’s philosophy! When you mention wanting a higher-level and simpler framework with convention over configuration, it resonates with my DX-first mentality. I prioritize minimal boilerplate while maintaining the flexibility to implement solutions outside of Hologram’s happy path. I’m also planning a database layer that will support automatic client-server synchronization when online, with an interface that’s more streamlined than Ecto while maintaining its power.
It makes me happy to see that many of Hologram’s planned features align well with what the community is looking for. I’ll be presenting at ElixirConf 2025 and will be conducting a full-day training as part of the conference. I’m planning an intensive 3-month “coding blitz” 
to get everything ready for the conference, after which Hologram should be production-ready. I’ve been gathering lots of constructive feedback through different channels lately and doing extensive planning. I’ll be presenting a detailed Roadmap and 3-month development plan soon.
8
Eiji
I’m excited about all Hologram goals, but it’s a completely different topic. Creating a native apps would always be best for system integrations. Of course in theory we can bundle a browser or use a similar solution and do same, but it’s very tricky and requires much more resources. The zed code editor is doing all drawing on GPU - there is no HTML or JavaScript stuff that happen on CPU, so that’s a huge difference. While Hologram may be best Web solution I would always prefer native apps.
1