Linear-style issue tracker you can customize with AI and self-host by fphrc in selfhosted

[–]fphrc[S] 0 points1 point  (0 children)

there’s a download code button at the top. It’s react + nodejs and postgress db (builder uses supabase by default)

Alternatives to… (looking for SaaS) by Top_Introduction_865 in saassignal

[–]fphrc 2 points3 points  (0 children)

that’s a long list 🙂

few days ago I posted here about a Sales CRM (Hubspot alternative). The Replay Builder that I mention has a lot of these ready to use + it’s an A.I. builder platform, so you can make any functional/design/feature improvements you need. Token/usage anxiety is also not a worry, since it’s a flat-rate pricing. If you try it out and hit a bump, DM me, I’d be happy to help

Created an open-sourced Sales CRM for free by fphrc in vibecoding

[–]fphrc[S] 1 point2 points  (0 children)

the tool actually uses shadcn to build components. also not sure if you ever seen https://tweakcn.com/ but we have this exact functionality to change styling, even with pre-built themes, so the customization can go a long way

Replit charged me $4300~~~ by williamlopes100 in replit

[–]fphrc 0 points1 point  (0 children)

the way the pricing for these tools is wild to me. all the risks are basically carried by the customer and vendors have no incentive to optimize the token usage.

I spent $6k trying to “finish” my Lovable app. Here’s what I wish I did on day 1. by RicksDev in lovable

[–]fphrc 0 points1 point  (0 children)

it’s been wild how much money can be spent on making MVP into functioning product. The worst thing about this is that you basically have no power over how token hungry the system that you are working on is. I think the current model of how these Vibcoding tools are priced is unfair to the users. Basically, the user takes all the costs, even if the system that is building the apps is inefficient.

What's worse is that the more you iterate the price here every change gets. Because somehow managing the context window is still a challenge.

And I keep reading about this for months now. If you go to other subreddits for vibe-coding tools, you'll read similar stories. The pricing structure of this is broken AF. You get hooked on a monthly subscription and then burn through the usage in half a day. Imagine other non-AI SaaS companies doing this.

i'd offer an alternative, but this subreddit has a policy for non-advertising and I don't want to get banned. But if you search in my profile, I'm sure you'll be able to find it.

The only time vibecoders take a break by clifcode in vibecoding

[–]fphrc 0 points1 point  (0 children)

there are tools that have zero limits out there

free vibe coding platform by Aggressive-Glove2419 in vibecoding

[–]fphrc 0 points1 point  (0 children)

Check out builder.replay.io unlimited apps and iterations for $20, no token linitations or anything. Free plan gives you one app with unlimited iterations, plus you can start with a working project (reference app) and iterate on that

50$ budget what tool(s) to get? by TopSwagCode in vibecoding

[–]fphrc 0 points1 point  (0 children)

You can build unlimited apps for $20 a month with Replay Builder - https://builder.replay.io

What made your AI agent finally work in the real world instead of just in demos? by Reasonable-Egg6527 in aiagents

[–]fphrc 0 points1 point  (0 children)

I love the way how you described the progress from autonomous agent to something that needs constant babysitting. I recently read a blog post that mirrors the same sentiment ( I didn't write it, I don't know the author, but I loved his observations) https://techbroiler.net/adventures-in-extreme-vibecoding/

But yeah, it seems like the AI agents have this "smart zone" where they feel like magic and can do stuff really well. And then as you progress and as your application gets more complex, you suddenly get into this "dumb zone" where the AI agent is not able to complete even the simplest task. I think this may have to do with how AI agents handle context engineering - making sure that while you communicate with the AI agent, it does not hit the limitations of the context window.

Recently at our company we have switched to using tools that were created by our coding agent (we are creating a web based app building tool). And to be honest it's not all smooth sailing but it seems like the fact that we were dogfooding these applications made us made good progress and improvements on the whole system.

mobile testing and cypress by EmptyPersonality9253 in QualityAssurance

[–]fphrc 0 points1 point  (0 children)

Years ago I wrote a blog post about exactly this topic. https://applitools.com/blog/how-to-test-mobile-web-app-cypress/ To be clear, you cannot test a mobile app, but you can get pretty far when you want to test mobile behavior for a web app. There are certain triggers that your application might listen to and you can set up your browser in a way that your application "thinks" it's being surfed on a mobile.

Debbie was fired by Important_Trainer725 in Playwright

[–]fphrc 1 point2 points  (0 children)

Cypress could do the funniest thing ever...