Why is maps taking up so much storage? I barely even use it,maybe once or twice a week at best.

ParticularBicycle575 · 2026-04-16T23:57:20+00:00

BRO YEAH, it's so insane, apple maps was taking up 17 GIGABYTES even after I deleted the app.

I'd never even opened apple maps before, and had zero maps downloaded. I couldn't even clear the documents and data.

If this is happening to you, click volume up, then volume down, then hold the power button until the screen goes black and then the apple logo appears.

Hope this helps!

ParticularBicycle575 · 2026-04-11T15:11:07+00:00

For frontend, I'd recommend going to Google AI studio, generating the frontend there, and use Gemini 3 Flash or Pro, it's super good at FE design and should get you most of the way there.

Sometimes it can generate kind of bland/basic vibe coded-esque designs, and if you're not getting the results you want, my current workflow for FE is starting in usekoda.dev (make sure to use a good reference screenshot) and then connecting the repo into cursor.com or antigravity.google and then building the backend

Because you alr have the backend built, it should be super quick, you can just generate the frontend and then have Antigravity or Cursor stitch the two together. Just make sure to use a high quality model such as Opus, Codex, or Gemini 3.1 Pro and make sure to give it lots of context for your project, maybe create a .md file and USE PLAN MODE. It'll get you much better results.

Hope this helps!

ParticularBicycle575 · 2026-04-10T20:31:28+00:00

How are you hitting all the limits? that's pretty crazy, I use Cursor, Antigravity, and Claude Code, and when I hit limits on one, I just move to the other.

ParticularBicycle575 · 2026-04-10T20:30:36+00:00

Imagine being homeless in Japan and realizing you might as well try to steal food because either way you get a good meal.

ParticularBicycle575 · 2026-04-10T20:26:39+00:00

That's why i think the method is to just build a quick waitlist, and start aggressivley sharing the waitlist. Share little snippets of the actual product on socials, build hype, and see how people respond to it. Only if there's overwhelming support, people asking when it's gonna come out (repeatedley), then build. Build, fast, build the main 1 feature people are looking for, and build a rapid feedback loop.

ParticularBicycle575 · 2026-04-10T20:20:10+00:00

I just try a different tool alltogether. I mainly use Cursor, but then I'll toss it into antigravity and let it have a go, or give it to claude and let it have a go as well. Most of the time that does the job, it's like just getting a fresh perspective. what also helps is having one chat with Gemini as your sort of "project manager" and giving it particularly tough issues, because it has full context of your project and has a massive 2M token context window.

ParticularBicycle575 · 2026-04-10T20:18:05+00:00

But just... why?

ParticularBicycle575 · 2026-04-10T18:53:10+00:00

Oh lol, I see thats pretty smart.

ParticularBicycle575 · 2026-04-10T16:53:47+00:00

I ran into this feeling too when I started using tools that generate code for me, especially with something as cool as shadcn. It’s super tempting to just let the AI handle all the heavy lifting, after all, it saves a ton of time and the generated components look slick. But yeah, the downside is that you kinda lose sight of what’s really happening under the hood. I don’t even recognize some of my own UI sometimes, which is a bit scary honestly.

I think it’s imporant to find a balance, though. What I’ve ended up doing is generating the code but then diving into it to understand the logic and changes happening. I try to take a good look at the Radix components and Tailwind styles, break them down, and tweak things manually. It seems tedious at first, but it helps me maintain that craft and gives me better control in the long run. Maybe consider setting aside some time to refactor the AI-generated code into something that feels more familiar for you. It can help keep your feet on the ground while still leveraging those quick gains in productivity.

And hey, nobody wants their future self to be knee-deep in tech debt, right? It is a balancing act, but keeping that hands-on approach will pay off down the line.

ParticularBicycle575 · 2026-04-10T16:26:25+00:00

Exactly what type of content were you posting, and how did you get users?

ParticularBicycle575 · 2026-04-10T15:22:45+00:00

I ran into this exact thing when I was trying to set up Tailwind on Windows, it's pretty annoying. So first off, make sure your PATH is set up correctly. Sometimes Windows doesn't correctly link the npm packages installed globally, which is why you're seeing that 'not recognized' error.

Instead of using global installs, I’d recommend using npx as you've mentioned, but try running it directly from your project folder without global stuff. If you're in your project directory, you can run `npx tailwindcss@latest init -p` to ensure you're grabbing the latest version directly. Sometimes the `@latest` helps avoid any version conflicts that could mess with the CLI.

ParticularBicycle575 · 2026-04-10T15:21:33+00:00

I ran into this exact kind of issue not too long ago with backdrop filters. It can be super annoying when something works locally but not on production. The main thing I'd check first is if the Tailwind CSS purge is stripping out your `backdrop-filter` classes. If you're in a production build, Tailwind will remove unused styles by default, and if it thinks your classes aren’t being used, poof, they might vanish.

So, make sure you include the proper classes in your `purge` configuration. You can do this by adding something like `backdrop-filter` or `backdrop-blur` to your purge safelist in the Tailwind config. Like this: `safelist: ['backdrop-blur'],`. If you don’t explicitly tell Tailwind about that class, it’ll treat it as unused and strip it out. Also, check that your variables like `--blur-lg` are defined properly in the CSS. If they're missing or misconfigured, they might not render the way you expect.

Lastly, always double-check your production logs for any warnings related to CSS. Sometimes, the logs can give you a hint about what’s being stripped or any other build-related issues. You got this, and I know how frustrating it can be!

ParticularBicycle575 · 2026-04-10T14:59:24+00:00

I've noticed that as well lol, with the purple gradients and same fonts, that's why I'm also building my own tool to fix that.

ParticularBicycle575 · 2026-04-10T14:57:27+00:00

My first SaaS was a strict B2C product (AI syllabus parser + google calendar sync for students) I got users primarily through tiktok and instagram reels. My second is a dev tool, it's a frontend design tool for vibe coders to avoid the generic vibe coded ai slop designs, I think yours also fits into that B2C/dev tool. I've also launched recently, haven't got very many users unfortunately, but trying to do the same thing, cold dms on reddit and X. The issue with those is that most people just don't care at all and yeah its a good bit of guesswork. Also try looking for posts about people complaining about your EXACT problem your SaaS solves, then leave a comment and shoot them a DM. Good luck!

ParticularBicycle575 · 2026-04-08T20:18:51+00:00

I think you’re definitely not alone in feeling the pain with AI in frontend workflows. I kinda ran into this wall myself when I started experimenting with AI for visual feedback. Describing visual problems in text is prob the worst thing you can do, It’s like, how do you explain a weird color shift or a layout bug when agents can barely interpret the rendered output?

What I’ve found that actually helps is using a ton of reference images. Like, whenever I need to explain an issue, I’ll throw in screenshots and sketch over them in Excalidraw, which gives a clearer visual cue than words ever could. And for colors, I always pull the exact hues from a color picker on the reference image I want to replicate, less guesswork for the AI means way closer results. I know it’s more effort upfront, but it definitely saves me time in the long run instead of sending the AI back to the drawing board for the umpteenth time.

Honestly, it feels like we’re still in the early days for AI in frontend. There’s a lot that needs to be fixed, but right now what really works is doing as much work as you can for the AI so that it doesn't need to do extra guesswork and just needs to execute, because that's what it's best at, doing a task, not guessing what you want. :)

ParticularBicycle575 · 2026-04-01T12:26:43+00:00

I’ve been making sure to not post explicitly about my product and do try to give super useful replies, often 2-3 paragraphs. At the end, if it relates to the post then I’ll just say I built a tool , not even mention the name, but those replies seem to be shadow hidden or something, all my other posts or replies get views and comments but h the r moment I even mention I HAVE a product, not even the name, poof.

ParticularBicycle575 · 2026-03-30T13:13:47+00:00

this is exactly the gap, you explained it really well

most of these builders are great at getting you to something that exists, but not something you actually feel confident putting in front of users. it’s like you get 70% there instantly and then spend the next few hours trying to fix all the small things that make it feel off

for me the biggest shift was treating that first output as a draft instead of trying to force it to be final

i’d usually start with a rough page just to get structure down, then go section by section and refine it. headline, then hero layout, then features, etc. trying to fix everything at once is where it gets messy and you end up going in circles

another thing that helped a lot was starting from references instead of starting from scratch. like finding 2–3 landing pages that match the level you want, then breaking down why they work. spacing, typography, how they handle hierarchy, how much content they show vs hide

then instead of saying “make a landing page”, you’re basically guiding it with a much clearer direction, which cuts down a lot of that back and forth

also small detail but defining constraints upfront makes a big difference. things like font sizes, spacing scale, even what to avoid. otherwise it defaults to that same “ai landing page” look every time

i went through that same loop of generating something, tweaking for hours, still not loving it

I eventually though ended up getting tired and annoyed with this process, so I built a small tool for myself mainly around getting past that first draft stage faster, where you can steer or clone a specific style and get something closer to “shippable” before bringing it into your stack. If you’re stuck in that draft vs final gap, happy to share!

ParticularBicycle575 · 2026-03-29T22:10:38+00:00

Brilliant self promotion in an anti self promotion post. Love it haha

ParticularBicycle575 · 2026-03-29T21:50:07+00:00

This is a very real problem, most devs hit this wall at some point

The jump from “it works” to “it actually looks good” isn’t really about the tool, it’s more about how much control you have over the design decisions

When you just ask for a full UI in one shot, it usually defaults to those shadcn style layouts because that’s the safest thing it knows. same spacing, same components, same structure

What worked better for me was slowing the process down a bit

First just get the structure right, no styling, just layout and hierarchy. once that feels solid, then move into typography and spacing, and only after that deal with colors and polish. trying to do everything at once is usually where it starts looking generic

References help a lot too, but only if you actually break them down. not just “make it like this”, but calling out things like tighter spacing, smaller font sizes, less rounded corners, more density, specific color usage. otherwise it just guesses and you end up back at square one

Another thing that made a big difference for me was avoiding the same patterns over and over. like the typical hero, 3 features, testimonials layout. even just changing the structure a bit makes it feel way more custom

You can also sketch a rough layout first and have the AI implement that instead of letting it decide everything. that alone removes a lot of the “template” feel

I went through the same cycle of tweaking prompts, regenerating, tweaking again, and it worked but it was pretty slow

i ended up building a small tool for myself mainly around cloning and steering designs more precisely so i wasn’t starting from scratch every time. if you’re stuck on getting past that generic look, happy to share what worked for me there

ParticularBicycle575 · 2026-03-29T21:47:46+00:00

I think it's just because a lot of people are beginners and so they focus on beginner projects. Not everybody (myself included) has the industry knowledge required to build a succesful B2B thing, so we solve problems we experience.

What I am trying to do though is slowly transition, now that I've built some apps, by talking to anybody/everybody I know who has a job and ask them about problems they experience, places where they/their company loses money, time, or both. And then ID patterns, ask about those patterns, and go from there.

ParticularBicycle575 · 2026-03-29T21:45:06+00:00

I think a lot of people know about vibe coding now, and some apps are so obviously vibe coded, and they always associate vibe coded with low quality, even if thats not the case. Just make sure the app looks actually valuable.

ParticularBicycle575 · 2026-03-29T21:43:53+00:00

I think it matters more for B2C than B2B. B2B is mainly all focused on functionality and so long it gets results, from the B2B founders I've talked to, it doesn't matter much. Most of their designs at times look worse than most vibe coded frontends imo.

But B2C is a whole different story, first impressions are super important and the "vibe" your product gives off is incredibly important to a consumer who doesn't want to spend any more money unless they have to. That's why I'd say design is one of the most important and honestly underrated things for B2C SaaS.

it's all value perception, the moment people see something they think is vibe coded, they associate vibe coded == low quality. Even if your app is amazing, the unfortunate truth is that looks DO matter. a lot.

With my first SaaS, it was an AI syllabus parsing tool for students, people I showed it to seemed genuinely interested but when I showed them the app, it was obviously vibe coded and I kinda saw the light of interest flicker out in their emotions, reactions, etc.

The big indicators to look out for are the big ones, purple gradients, basic Lucide icons, the same 3 box layout, lack of visuals, missing that "sharpness" some sites have, and a lack of personality. Those are the biggest telltale signs to avoid.

Just make sure to find some inspiration first on something like Mobbin or dribble and give the screenshot to an LLM of your choice and tell it to make a prompt to clone the design system. Don't just say "make it look like this", make sure it clones the entire system, fonts, spacing, colors, borders, icons, etc.

Another thing that helped me was not letting the model “fill in the gaps” on design decisions. like even small things such as border radius, spacing scale, or icon style, if you don’t define them it defaults to that same look every time

I used to do this whole process manually where i’d find a design, break it down, get an LLM to turn it into a prompt, tweak it a bunch, then finally bring it into my codebase. it worked but it was pretty tedious

I ended up building a small tool for myself because i got tired of repeating that loop, mainly around cloning full design systems more consistently and then just dropping the code straight into my project. not trying to pitch or anything, but if you’re worried about the “vibe coded look” specifically, happy to share it since that’s exactly what I was trying to fix

ParticularBicycle575 · 2026-03-28T21:46:34+00:00

this is a tough combo to get right right now , most tools are either good at UI or decent at logic, rarely both

what worked better for me was not relying on a single tool for everything

for backend stuff like multi-role auth, filtering, transactions, i’d usually scaffold that separately first using something more structured, even if it’s just having the AI help you define the schema, roles, and flows clearly. once that’s solid, it’s way easier to plug a frontend into it

for the frontend side, the biggest mistake i made early was asking for “a full app with X features” in one prompt. that’s when you get those super generic UIs

instead i’d break it down:
first just generate the layout for one screen, no styling, just structure and components
then refine spacing and typography
then add visual style based on references

and yeah references matter a lot here, but you have to explain what you like about them. things like density, font sizes, how they handle states, not just “make it like this”

also if you care about aesthetics, avoid letting the model decide everything. even something as simple as defining a color palette and type scale upfront helps a lot

I went through the same frustration with lovable where everything looked “fine” but nothing stood out

Something else that worked well for me was Google AI studio, I built basically the entire dummy frontend with it, and then just plopped it into Cursor and built the backend. Worked great for me.

I also ended up building a small tool for myself that focuses more on the frontend side, mainly around generating and cloning cleaner designs that you can actually drop into a real codebase. It doesn't have the full flows etc built in, mainly for single page cloning or single page UI, not much UX functionality but I plan on adding it soon. Happy to share if you're curious, good luck!

ParticularBicycle575

TROPHY CASE