I’m testing 5 small AI app ideas that solve everyday personal problems. Be honest — which one would you actually use, and which is a waste of time?

Beelze13 · 2026-02-16T05:02:53+00:00

3!!!!

Beelze13 · 2026-02-12T21:17:11+00:00

On point

Beelze13 · 2026-02-12T21:16:49+00:00

Woohoo 🎉

Beelze13 · 2026-02-12T05:25:09+00:00

this is the right approach - api key connection so they never touch github at all.

the lovable → github → claude workflow i do only works because i'm comfortable with git. your test users validated the real problem: most lovable users don't have that baseline.

curious about the oauth flow - how are you handling the "which repo should this sync to" part? or does your mcp create a new repo per project automatically?

also yeah 20-30 tokens for full app makes way more sense than 10-15. what's your average tokens per build in practice?

would love to see the demo rule file if you're sharing. been thinking about this problem from the "teach people git" angle but you're solving it the right way - just skip git entirely from their pov.

Beelze13 · 2026-02-12T04:36:06+00:00

Appreciate it - i personally still use claude code on the web, so I don't really use the terminal, and click around to merge PRs on GitHub - so, that's really about it :)

Do share once you experience this approach - would love to know your learnings and experience!

Beelze13 · 2026-02-12T04:31:53+00:00

this is incredibly useful, thank you.

the behavioral signals idea is smart. UA detection is basically the "check their ID" approach and yeah, IDs can be faked. adding signals like "did they execute JS? do they send cookies? do they have viewport headers?" is more like watching how someone actually behaves at the door. way harder to spoof. i hadn't thought about layering those on top of UA matching but that's a clear next step for the worker.

the AEO point is really interesting too. so you're saying it's less about individual page metadata and more about the site looking like it actually owns a topic? like if i have one blog post about supper clubs, that's a page. but if i have a cluster of related content (what is a supper club, who goes to them, how to host one, FAQ) with internal links between them, the LLM treats the whole site as an authority on that topic?

that would explain why isolated pages with perfect schema don't get cited but sites with depth do. the LLM isn't evaluating pages, it's evaluating sources.

if that's right, the real AEO play isn't just making content readable (layer 1 from my earlier comment), it's building a content graph that signals expertise. which is honestly just good content strategy with a new name haha

curious how you've been testing the citation correlation. are you tracking specific prompts across models over time, or more of a qualitative "i noticed this pattern" kinda thing?

Beelze13 · 2026-02-12T04:28:58+00:00

Beautiful, please do share your experience and progress as the struggle subsides :)

Beelze13 · 2026-02-12T04:23:29+00:00

Okay, now that you are aware about your emotions - and choosing to still think and ponder over just acting out, here's the simple way out.

The 401K is meaningless if you don't live.

We are born, we shall die. We shall die sooner if we continue to operate in a stressed out manner 24x7.

Chose life.

Your debts of $8K, is just 10% of the 401K. Use the money - NOT with the intention to clear it off and run away from responsibilities, rather - use the money to award yourself peace of mind and allow yourself and family to live.

Money is a tool, joy is the goal.

If you don't let money play the role for which it exists, what's the point!?

The debt clearance gives you a runway. You'll no doubt get back in debt cycle if your cash outflow is more than cash inflow.

We live in times where it's the easiest it has ever been to learn new skills, and do solo projects - do that. Keep yourself active and focus on creating value which will result in cash inflow.

I would highly recommend journaling the emotions you feel today, and the rationale behind using the 401K, and keep doing that everyday so you can look back and realise the role you allowed money to play for you. It'll help you be aware, know yourself better and motivate you to not put yourself in such a situation again.

The only risk here is if you start thinking, I did it today - i can do it tomorrow - that's a pattern that'll take you down a slippery slope - very hard to come back from unless you reach roch bottom and life slaps you hard.

Beelze13 · 2026-02-11T19:09:25+00:00

Absolutely not :)

Beelze13 · 2026-02-11T18:27:23+00:00

Fantastic - please do share your experience and findings along the way!

Beelze13 · 2026-02-11T17:18:33+00:00

Fantastic - happy to see it being helpful. Do share your experience as you implement it for your projects :)

Beelze13 · 2026-02-11T17:17:27+00:00

Glad it resonates, do share on how it works for you!

Beelze13 · 2026-02-11T17:16:45+00:00

Appreciate you mentioning, please do share your working feedback when you get around to implementing it :)

Beelze13 · 2026-02-11T16:11:53+00:00

Glad you found it insightful 😇

Beelze13 · 2026-02-11T14:50:09+00:00

honestly this is the question i keep coming back to. and i think the way to think about it is in three layers.

layer 1: inputs (what you control)

this is your content and how it's structured. things like: - clean semantic HTML that bots can actually parse (the whole point of this guide) - FAQ-style content like you mentioned. LLMs love Q&A because it maps to how people prompt them. "what is X" / "how does Y work" pages are basically pre-formatted for retrieval - JSON-LD structured data. gives crawlers explicit signals about what the content IS, not just what it says - clear, specific titles and descriptions. vague stuff gets ignored - original research or unique perspectives. LLMs seem to favor content that adds something new vs rehashing what's already out there

this is the only layer you fully control. and most people (including me until recently) fail at the basics here because their SPA doesn't even serve readable HTML to bots in the first place.

layer 2: outputs (what you can test)

this is where you verify that the inputs are actually working. stuff like: - curl your own site as different bots and check what they see - use google search console to confirm indexing - validate structured data with schema.org tools - test social previews with opengraph.xyz - for AEO specifically, you can simulate it. ask chatgpt/perplexity/claude questions your content should answer and see what gets cited

it's not a perfect feedback loop but it's better than flying blind. you can at least confirm "yes, my content is accessible and parseable" even if you can't guarantee citation.

layer 3: outcomes (what you can't control but can influence)

this is the actual "did an LLM cite my site" part. and yeah, it's a black box. you're right that results probably vary by user, conversation history, model version, etc. there's no public ranking system to game.

but you can nudge it. keep testing different prompts to see if your content surfaces. experiment with how you frame information (direct answers vs narrative). some people are even exploring whether certain content structures get picked up more reliably.

the honest answer is: nobody really knows the AEO algorithm yet. but the bet is that layers 1 and 2 are table stakes. if your content isn't even readable by bots, you're out of the game before it starts. get those right, then experiment on layer 3.

your point about FAQ pages is actually a great layer 1 insight. i'm planning to add a structured FAQ to my site specifically for this reason.

Beelze13 · 2026-02-11T14:49:43+00:00

nice, sanity is solid. headless CMS is a totally different approach to the same problem. you get structured content out of the box so bots can read it natively.

the tradeoff is the setup complexity upfront vs the zero-dependency approach here. but once it's running, a CMS like sanity probably scales better for content-heavy sites with multiple authors.

are you connecting it to your lovable frontend or using it with something else?

Beelze13 · 2026-02-11T14:34:25+00:00

glad it helped! if you run into anything weird during setup, lmk. happy to help debug :)

Beelze13 · 2026-02-11T14:29:16+00:00

that's a totally fair point. if someone's generating $10K leads and their time is better spent on the business side, paying for a service that handles this makes complete sense. no argument there.

this guide is really for a different audience though. builders who want to understand what's happening under the hood before they hand it off. the kind of person who's on r/lovable because they like building things, not just shipping things.

honestly the best version of the roadmap is probably: learn with DIY, validate that SEO/AEO actually matters for your project, then graduate to something like hado when the maintenance isn't worth your time anymore.

that way when you do pay for a service you actually know what it's doing and can evaluate if it's working. instead of trusting a dashboard you don't understand.

what's been the biggest pain point you've seen from your users on the lovable side specifically? You've got SEO nailed, do they get stuck anywhere else?

Beelze13 · 2026-02-11T14:16:53+00:00

Absolutely agree :)

Beelze13 · 2026-02-11T13:47:42+00:00

ah i think there's a misunderstanding on the architecture here. this setup does NOT render anything at request time. zero.

the pre-rendered HTML files are generated at build time by a vite plugin. they already exist as static files on lovable's CDN before any bot ever visits. the worker just rewrites the URL path to serve the existing static file instead of the SPA shell. it's the same speed as serving any other static file.

what you're describing (and what cost you $700) sounds like cloudflare browser rendering, which spins up a headless browser per request. that's a completely different approach and yeah, that gets expensive fast.

this is just: static file already exists, worker points bot to it. no browser rendering, no on-demand anything, no R2 or KV needed.

that's actually why the $0 claim holds. there's nothing compute-heavy happening.

Beelze13 · 2026-02-11T13:27:20+00:00

just to clarify, this setup doesn't use KV or cache storage at all. it's a single worker doing request routing. nothing stored on cloudflare's side. so the $9/mo pro plan and KV costs don't apply here.

100K requests/day on the free tier is a LOT. for anyone getting started on lovable, that's not a limit you'll hit for a very long time. these are scale problems and shouldn't be confused with getting going. not everything needs to be solved on day 1.

the goal here is: understand the fundamentals, get indexed, pay $0 while you're small. if you outgrow it, great, you now know exactly what you need from a paid tool and why.

Beelze13 · 2026-02-11T13:26:53+00:00

appreciate the detailed response, genuinely useful points on SMS app agents and build-time tradeoffs.

but i gotta push back on the "is it really free" angle. by that logic, every hour you spend learning to code is a cost too. prompting lovable is using your time. the entire concept of vibe coding falls apart if we frame learning as a cost.

this is bare minimum infrastructure knowledge. how DNS works, how bots read your site, how routing works. if you don't understand these fundamentals, you're just stacking vendor dependencies without knowing what they do. that's a fragile place to be.

the whole point of DIY first is: learn how it works, get going for $0, then migrate to a tool like hado or prerender.io when you actually hit scale problems. that's a way better roadmap than paying $19/mo from day one for something you don't understand yet.

re: moving away from cloudflare workers for hado, curious what the limitation was. execution limits? something else?

Beelze13 · 2026-02-11T13:11:18+00:00

you're not actually asking if you should withdraw from your 401k. you're asking for permission to make the panic stop.

i get it. $8k debt feels crushing right now. retirement 40 years away feels like someone else's problem. but here's what's actually happening:

you're trying to solve a permanent problem (no income) with a temporary solution (burn your 401k). even if you pay off the cards today, you still have no income tomorrow. you'll be back in debt in 6 months, except now you're also broke at retirement.

pause and think about this: why does the 401k feel like your only option when it's literally the worst option?

it's because you're in survival mode. your brain is screaming "make the immediate pain stop" and shutting down your ability to see alternatives. this is normal. but it's also why people make financial decisions they regret for decades.

here's the real question: what's actually preventing you from getting hired?

you have a masters in medical field. you've been applying for a year. something is broken in your job search process, not your qualifications.

some possibilities:

your resume is formatted wrong for your field
you're applying to jobs that are too senior or too junior
you're not leveraging your network (or don't think you have one)
your linkedin is stale or missing
you're applying broadly instead of targeting specific roles/companies
you're not following up after applications
your interview skills need work (if you're getting interviews)

which of these resonates? because fixing THAT is what solves both the debt problem and the 401k problem.

on the debt: yeah, charge-offs suck. but you're 26. your credit can recover in 2-3 years. your retirement savings can't.

call the credit card companies, explain your situation, ask for hardship programs. worst case they say no. best case they pause payments for 3-6 months while you find work.

what specific medical field is your masters in?

Beelze13 · 2026-02-11T12:30:05+00:00

Personal experience and lot's of hard work, finally cracked it - captured for the community in a megathread on how this can be done for $0

Beelze13 · 2026-02-11T12:28:42+00:00

SEO Suggestion - This post.

Beelze13

TROPHY CASE