Advice for product creators.
I think soon we'll see gazilions of new products/apps/packages launching every day, from vibe-coders.
But I see a clear path to make your product STAND OUT.
Here's my advice/prediction.
Most vibe-creators will stop at first prompts.
At the first/second version.
"Does it work? Cool, let's launch!"
So the products that will actually win their categories will be the ones where creators go DEEPER.
Successful builders will think about:
- User experience: design, minimizing unnecessary clicks, clear error messages, etc
- Docs / onboarding / Readme with VISUAL examples (images/video)
- Differentiator features: what other similar apps DON'T do?
- Warm-up the audience: start talking to potential users WAY BEFORE the launch
- Bug tracking, logging and quick fixing
- Support of the first users (including quick replies on social media)
@alexdaubois I don’t know if I am holding it wrong but xdebug(), has been fiddely and kept breaking every now and then so I gave up years ago. Maybe I should give it ago again? I would like something that just works. Lite the experience in Xcode.
How can we improve the debugger situation in #PHP? Compared to other languages, the majority of people use dd() and dump() (myself included!).
How could we change that? What the biggest friction point?
In 2017 I tweeted a screenshot of F-Bar late at night. Went to the bathroom, came back and my phone was buzzing like crazy @taylorotwell had retweeted it. Nine years later, Forge is retiring the old API. So I rebuilt the whole thing. laravel-forge-menubar.com
Have seen a lot of Claude hate out there today and just want to say I love Claude. He's my boy. Claude Code is still the best AI CLI by a wide margin. I use the others too, but CC is still top dog to me.
Using more AI in my Laravel work lately. Big potential. Disruptive tech for sure.
Claude Code writes surprisingly good Laravel code (for the most time).
But still need to design, review, test, monitor and talk to users. Make sure it actually works…
They say you shouldn’t build products just to scratch your own itch.
I still shipped an F-Bar iOS update.
Because I use it all the time. #laravel#laravelforge#php
@PovilasKorop I think as long as there's more than one option, people will formulate opinions. Even more people will formulate opinions without trying the other option.
Having used both, I know when Livewire makes sense and I know when I need Inertia instead
Anyone else regret using Livewire? : r/laravel reddit.com/r/laravel/comm…
Reddit mega-thread with 150+ comments.
Here's the summary if you don't wanna read it all.
There are actually two groups of people:
People who have NEGATIVE Livewire experience, emphasize this:
- It can be hard to debug and fix problems
- Error messages don't help much
- The instructions aren't always clear
- It can be slow sometimes
People who LOVE Livewire, say this:
- It works well for simple things like forms and search boxes
- You can use PHP instead of learning new languages
- Some people really like using it with @filamentphp
All in all, most people say Livewire works best for SMALL PARTS of websites, not whole websites as SPA full-page components.
What do you think?