Absolutely, any frontend, LiveView or React, can get messy if not carefully maintained. As the app grows and more developers contribute, regular code reviews and removing unused logic are essential, otherwise DX suffers just like in any other framework. I also agree there is still so much room for improvement in this space.
Author here: Not sure why everyone’s taking this as anti-rails or anti-laravel. It’s not. I just shared what worked best for my use case. Real-time updates are built into phoenix through channels and liveview, while in rails it’s handled through Action Cable and Turbo Streams. Both work great, but phoenix’s setup felt more integrated for what I was building.
true, there’s always more to learn. i just shared what worked best for my use case with liveview. rails is also a great framework and i enjoy using it, but liveview’s built-in real-time updates and state management fit my project needs better.
Thanks for your feedback! Yes, Oban is a third-party package, but it’s built for Phoenix, which is what I meant in the article. Also, the article is not AI-generated. I’ve mentioned the app I built with Phoenix at the bottom to give context from real experience.
Recently people found that a lot of website genereated by ai has purple theme color[1], so when first glance on your site, I think it is a vibe code product immediatlly : )
True, I just liked the gradient for branding, and I love how it looks. From your perspective, you’re right though. At least I can assure you there’s no AI-generated code on the landing page. I’ll keep working to improve it as much as possible. Thanks mate :)
It’s not just a simple todo list. The product includes advanced features like goal tracking, minimal project management, a streak system, daily task resets with a 3-task limit, and AI-powered task creation that can break tasks into subtasks. Users also get individual profiles to share streak progress and build habits. On top of that, we’re working on additional features like adding team members to projects and real-time collaboration. While it’s certainly possible to build these in Laravel, implementing them is not as seamless or straightforward as it is in Phoenix.
I completely agree. Requiring credit card info for a free trial often feels like a dark pattern designed to trap users into paying. I’m taking a different approach with my product by offering a 3-day free trial that doesn’t require a card, and a 14-day free trial for serious users. I want users to try it without any pressure or tricks and make a decision based on the value they experience, not because they forgot to cancel.
I don’t hire developers who are tied to just one framework. I prefer someone who has a solid understanding of a platform but also a mindset to learn new technologies. You don’t need a large team, just one or two talented developers on a good pay package can be more than enough, and in my opinion, it’s worth it.
