Hey founders, what are you building?

🚀 Built something cool and want more people to know about it?

I created ContactJournalists.com because PR was one of the biggest growth drivers in my own business.

We have a 7 day free trial for you to get stuck in and look around :)

A single feature can do so much more than generate a nice ego boost:

✨ Build high-authority backlinks
✨ Improve your SEO
✨ Increase your visibility in AI search (GEO)
✨ Drive targeted traffic to your website
✨ Build trust with potential customers
✨ Open doors to podcast interviews and partnerships

The problem? Finding relevant journalists and podcasts takes forever.

That’s exactly why I built ContactJournalists.com.

What you get:

📰 Live press requests from journalists actively looking for expert comments and product recommendations

🎙️ Hundreds of podcasts looking for guests

🔎 Searchable journalist database with reporters, bloggers, and editors across dozens of niches

✍️ AI Pitch Helper to help you craft stronger responses

📂 Save contacts and media opportunities to your own lists

📈 Track your submissions in one dashboard

👀 See when journalists save your profile

Who it’s for:

🚀 Solopreneurs
💻 SaaS founders
🛍️ Ecommerce brands
📣 PR agencies
🏋️ Coaches and consultants
🤖 Indie hackers
🏢 Startups and small businesses

If you’re building something and want to get featured in the press, appear on podcasts, and grow your brand organically, it’s designed for you.

🎁 Free 7-day trial
💷 Then just £14/month

It takes about 30 seconds to get started.

👉 https://www.contactjournalists.com

Would genuinely love your feedback from fellow founders and marketers. 😊

#PR #SEO #GEO #SaaS #Solopreneur #Startups #IndieHackers #PodcastGuest #BuildInPublic

Not looking for sympathy, just figured I'd share what I built in case anyone finds it useful.

The thing I'm most proud of: it analyzes your mistake patterns and generates AI exercises targeted at exactly what you keep getting wrong. Generic typing practice always felt useless to me, so I tried to build the opposite.

If you're a dev who cares about typing speed, I'd genuinely appreciate you trying it(codetype.tech).

Founder here - would love any feedback.

I built TestLaunch because I keep seeing Play Store developers posting that they need testers, feedback, or people to join their testing links.

TestLaunch is a free place to list your app, share your testing link, and let testers find projects that need help.

You can add your app name, platform, category, test duration, contact email, description, testing link, and what kind of feedback you are looking for.

The goal is simple: give Play Store developers one clean page to share instead of chasing scattered tester posts everywhere.

It is brand new, so feedback is welcome.

https://tipitylabs.online

Figured I’d post mine as well since Cursor limits how many referral signups work each month

Referral gives 50% off the first month on Cursor Pro,Pro+,and Ultra plans:
https://cursor.com/referral?code=V6CY3ZZOOPEX

Looks like it’s for new accounts / first paid signup only. I also get usage credits if someone signs up through it (ill give you a smooch)

Been using Cursor a lot lately for React,Swift,and general AI workflow stuff so figured someone here might get use out of it.

After months of late nights, learning as I go, and rebuilding things more times than I can count… my app Simonara is finally live on Google Play 🎉

I originally started building it because I’m genuinely terrible at gifting under pressure. I’d wait until the last minute, overthink every option, forget ideas people mentioned months ago, and spend WAY too much time scrolling trying to find something meaningful. I launched the web version first and then worked almost everyday to get it on the Google Play Store. (Apple store coming soon...)

What’s wild is I had zero real tech background before starting this journey. I’ve basically been figuring things out piece by piece while balancing work, kids, life, and everything else in between.

Launching something publicly is honestly terrifying, but also really exciting.

Still a lot I want to improve, but seeing real people use something that started as just an idea in my head feels surreal.

Would genuinely love feedback from anyone willing to try it or even just hear how you personally approach gifting for people you care about. [Simonara Gifting App](https://play.google.com/store/apps/details?id=com.simonara.gifting)

Hey everyone, I hope you are well.

I built a platform for builders who built vibecoded sites/businesses/apps/start ups etc, who just want to build and not worry about markets, competitor analysis, pitch decks, business plans etc. You pop your URLs, code, files, images, chatgpt, Claude, Gemini chats etc in and it generates it all for you. You pivot, change prices, markets, it changes it all for you as a living document and workspace and export it in any format you want.

This idea stemmed from my own frustrations of building a healthcare startup as a tool for myself but spiralled into something else.

It's early stages and looking for some potential testers if possible who will get free access to help me improve it and hopefully help you too.

https://ceoworkspace.lovable.app/

Cheers

Hey everyone,

One thing I kept noticing with iOS releases is that even solid apps often get delayed during App Store review for issues that aren’t really about the core product.

Things like missing metadata, incomplete privacy details, subscription setup inconsistencies, or small guideline oversights tend to cause repeated rejection cycles and slow down launches more than the actual code does.

So I built AppReviewer Preflight.

It’s a structured pre-submission checklist tool designed to help iOS developers catch common App Store review risks before submitting a build.

Instead of relying on memory, scattered notes, or last-minute checks, it centralizes everything into a clear workflow you can actually follow before release.

Key Features:

• Pre-submission checklist focused on common iOS review risks
• Filter checks by app type (subscriptions, IAP, ads, UGC, login-required apps, etc.)
• Severity labels for critical vs. major issues
• Mark items as resolved or unresolved during review
• Add internal notes for QA, handoff, or team tracking
• Fast search across rules and submission topics
• Save progress locally and continue anytime
• Export reports as PDF or JSON
• Quick access to official Apple guideline references
• Clean workflow designed for iPhone and iPad

Who it’s for:

• Indie developers preparing first launches
• Agencies shipping client apps
• Product and QA teams managing release cycles
• Developers trying to reduce avoidable App Store delays

What it helps you do:

• Catch privacy and compliance issues earlier
• Validate monetization and subscription setups
• Reduce preventable rejection cycles
• Track unresolved review items in one place
• Improve release confidence and consistency

The goal is to make App Store submission more predictable and less reactive.

You can try it here:
https://apps.apple.com/app/appreviewer-preflight/id6761920856

I vibe-code with agents a lot and got tired of glancing back at the chat every time a long reply finished. So I made Aftertone: after each agent response, a local Supertonic ONNX voice reads a short line (what landed, blockers, next step) — not the whole wall of text.

What it is

• Runs on your machine (~/aftertone), MIT, no TTS subscription
• Cursor and Claude Code work today (Codex / OpenCode on the roadmap)
• Per-chat on/off (/aftertone-on in Cursor, /aftertone_on in Claude)
• Agents use a <spoken_summary> tag at the end of replies; if there is no tag, it stays quiet (tag-only mode by default)

Install (Linux/macOS):

curl -fsSL https://raw.githubusercontent.com/omarelkhal/aftertone/main/scripts/install.sh | bash -s -- --install-uv --start-daemon

Then in Cursor: Hooks on + trusted workspace. In Claude: /aftertone_on in the chats where you want audio.

Repo / docs: https://github.com/omarelkhal/aftertone

Happy to answer setup questions. If you try it, I would love to know whether the spoken summaries actually help your flow or feel like noise.

Over the past 18 months, I’ve switched from 15 years of “traditional” software engineering (manual memory management, strict type‑driven development, line‑by‑line debugging) to a vibe‑first workflow. I want to share a detailed, non‑pessimistic comparison – and then explain why I believe vibe coding will replace most traditional coding, leaving only one niche for the old guard.

This post is not AI‑generated. I’ve used LLMs (GPT‑4, Claude, Copilot) to refine my thinking and generate code, but every word here is my own. Let’s dive in.

1. Definitions (so we argue from the same map)

• Traditional coder – Prioritises exact syntax, manual control flow, test‑driven design, and deep understanding of every abstraction layer. Often writes code “from scratch” with minimal AI assistance beyond autocomplete.
• Vibe coder – Focuses on intent, flow, and outcomes. Uses LLMs to generate, refactor, explain, and test code. The vibe coder’s job is to guide the AI, review its output, and maintain the product vision – not to wrestle with brackets.

2. Where vibe coding excels (evidence from my own workflow)

I recently built a full‑stack document‑parsing pipeline (FastAPI + React + PostgreSQL) in 8 hours using a vibe‑coding approach. The same project would have taken me 3–4 days traditionally.

How I did it (educational part – tools & process):

Step	Tool	What I did (vibe style)
1. Requirements	GPT‑4	Described the desired user journey in plain English. AI returned a PRD + data model.
2. Backend boilerplate	Cursor + Copilot	Typed // create a FastAPI endpoint that accepts PDF, extracts tables, returns JSON. AI wrote 90% of the endpoint.
3. Database	Claude	Asked “given my models, write Alembic migration and SQLAlchemy relationships”. Fixed 2 minor foreign‑key issues.
4. Frontend component	v0.dev + manual tweaks	Generated a drag‑and‑drop upload component. Manually added error handling and loading states.
5. Integration & debugging	Cursor chat	Pasted error logs. AI suggested the exact fixes. I understood each fix before applying.

Key insight: I didn’t “blindly copy”. I read every line the AI wrote, questioned it, and sometimes rewrote 10‑20%. But I never typed boilerplate loops, DTO mappers, or CRUD endpoints manually. That’s the vibe coder’s advantage: speed without losing understanding.

3. Traditional coding’s remaining value (and its inevitable shrinking)

Traditional skills are not useless. But their highest leverage is now in exactly two places:

1. Building the AI agents themselves – LLM infrastructure, agent frameworks (LangGraph, AutoGen), tool‑use protocols, and evaluation systems. Those require deep systems knowledge.
2. Safety‑critical or mathematically verified systems – aerospace, medical devices, formal verification. But even there, AI‑assisted development is creeping in.

For everything else – web apps, internal tools, data pipelines, MVPs, automations – vibe coding is already faster, cheaper, and often more readable (because the AI enforces consistent patterns).

Conclusion of this section:
The traditional coder who refuses to adopt vibe workflows will become a specialist – the person who builds the LLM that vibe coders use. Everyone else will vibe code. That’s not pessimism; it’s observing the exponential curve of AI code generation.

4. Addressing the common anti‑vibe arguments (constructively)

>

Rebuttal: So do traditional coders who skip reviews. The difference: a vibe coder can ask the AI to “review this for SQL injection” and get an instant security analysis. Traditional security requires manual audit or expensive tooling. Vibe coding, done right, includes AI‑assisted review as part of the loop.

>

Counter: I’ve learned more by vibe coding – because I ask the AI to explain why it chose a certain pattern. I’ve deepened my knowledge of async Rust, complex SQL window functions, and React hooks exactly this way. Vibe coding is not “copy‑paste”; it’s dialogue‑driven learning.

>

Rule #1 of this sub: low‑effort posts are banned. Same for code. A vibe coder who just dumps AI output without understanding is a bad vibe coder. The professional vibe coder reviews, refactors, and tests – but at 10x speed.

5. My personal workflow rules for professional vibe coding

If you want to adopt vibe coding without becoming lazy, here is the system I use (and recommend):

1. Never commit AI code you don’t understand – read every line. If unclear, ask the AI to explain.
2. Use AI for generation, not for decision‑making – architecture, tech stack, trade‑offs are human.
3. Write tests first – then ask AI to implement until tests pass. That keeps you in control.
4. Keep a “vibe log” – document which prompts gave good results. That’s your reusable knowledge base.
5. Manually handle edge cases – AI often misses the weird inputs. That’s your job.

Following these, I’ve shipped 5 projects in 3 months. Zero major bugs in production. My traditional‑coder friends are shocked.

6. Final conclusion (the future, as I see it)

>

The future software engineer will be a product‑focused vibe coder – fluent in English, system design, and AI prompting. They will build what used to take teams of traditional coders.

The only traditional coders who remain will be the ones building the AI agents themselves – the LLM architects, agentic workflow engineers, and tool makers. Everyone else will vibe code.

That is not a threat. It is an upgrade.