I’ve been working on Frateca, a text-to-speech app that converts articles, PDFs, documents, and other text into natural-sounding audio, for more than a year now.

Today I released a free Chrome extension to make it much easier to use!

Now, when you’re reading something online, you can send it to Frateca directly from Chrome and turn it into audio without copying and pasting the text manually.

You can listen to the generated audio or download it if you want to listen later.

I originally built Frateca for people who prefer listening to long articles, research papers, newsletters, and other reading instead of sitting in front of a screen.

Frateca also works with:

• Webpages and blog posts
• Substack and Medium articles
• PDFs
• EPUB and Word documents
• Copied text
• Photos of text
• iPhone and Android

The Chrome extension is completely free (you get 1 hour of audio generation every day).

I’d really appreciate any feedback, especially if you use text-to-speech regularly. I’m still actively improving it and would love to know what features would make it more useful.

Free Chrome extension

web version

iPhone app

android app

I recently built Kivho, an ASO tool I've been building for the past few weeks.

Because exisiting ASO tools kind too expensive or few really sucks...

Kivho helps indie developers research App Store keywords, analyze competitors, and figure out which keywords might actually be worth targeting. and it also provides an AI agent that does research and all the necessary stuff for you...

Now It would be really helpfull for me if some real people would test and tell us about UX improvements

Not looking for fake testimonials or 5-star reviews. I genuinely want to know what's broken, what's confusing, and what's missing.

So I'm giving 10 early users free access to the premium plan.

• 100% off with promo code: EARLYTEST (use this while checkout, no credit card required)
• No credit card required.
• Access to premium features.
• only applicable for $19/month plan

All I ask is that you actually try it and tell me what you think. Even if your feedback is that the tool sucks, I'd rather hear that now.

I've spent enough time building what I think developers need. It's probably time to hear from developers themselves.

Here's the link: https://kivho.com/

If you're working on an iOS app or struggling with App Store visibility, I'd love to have you test it.

And if you already use another ASO tool, I'd be especially interested in hearing what Kivho does worse.

Anyone interested?

I'm building Terminus - an iPhone app that puts a card from your own flashcard set on the Lock Screen and Home Screen widgets

how it's built: SwiftUI + WidgetKit, App Intents so you can answer right on the Lock Screen widget, FSRS for the review schedule. the waitlist page is a plain page on Cloudflare Pages, with PostHog counting visits per link tag

the waitlist page has been up for a few weeks. the numbers so far:

• 143 visits
• 4 people started typing an email
• 0 sign-ups

what I think went wrong:

1. the page never said it's free - "Free to download. No account." goes live today
2. "get it when it's ready" sounded far away - it's actually in App Review, and the page says that from today
3. I had no idea where visits came from - every link now has a tag, and the page starts logging the referring site today

where it stands: 1.1 is back in App Review because I added iCloud sync between iPhone and iPad

would love a blunt look at the page - what would make you sign up, or close the tab? https://terminus-cards.pages.dev/?tag=reddit-buildinpublic

Anybody with me here?

You can spend months building something amazing…

And still have zero users.

Because building is the comfortable part.

Getting strangers to care? That’s the real challenge.

What’s harder for you?

A) Building
B) Finding users
C) Getting honest feedback

I’m curious what other builders think. 👇

Hello everyone,

I’m working on https://makerswall.io which is a community-driven platform where makers trade feedback on each other’s projects. It is built around reciprocity:  in order to get feedback, you have to test someone else’s project first.

Why I built this

I kept struggling to get insightful feedback on my own projects. Unless you have a network of skilled people with time to spare, you’re likely find hard to find real testers. I didn’t want to spend money getting feedback for projects that aren’t profitable yet and might never be.

How it works

• Submit your project (app, SaaS, website…)
• Claim someone else’s project, test it, and write a report for its maker
• Each report earns you credits. You can spend them to read the reports on your own project or to boost it so it gets tested sooner.

It’s 100% free, credits are only earned and cannot be bought.

We opened publicly this weekend and 18 projects from 17 makers are already in. Seeing the first real feedback go back and forth has been great.

Building in public

I will regularly post updates about how this community evolves and what I'm learning about growing it. My first paid project was a failure in both acquisition and distribution so I'm taking a step back and learning more about marketing by working on a 100% free project. On top of that, makers wall is already providing me and other makers with great feedback on how to update my original project so I can relaunch it in the next months and hopefully get my first customers.

Feedback

Two things I'd love your honest take on:

• Is the landing page pitch clear within a few seconds?
• Do the credit rules make sense, or do they feel like friction?

If you submit a project, I'd like to hear how it went. Criticism welcome.
Thanks, and I hope it helps you too!

Hey r/buildinpublic! 👋
I wanted to share a major milestone and some lessons learned from our 5.0 release of Fine.
Over the past few months, I spent countless hours (and a tons of Claude Code tokens) refactoring our app to combine pro editing controls with on-device AI—without having to send user data to cloud servers.
What We Built & Lessons Learned:
On-Device AI Workflows: We integrated local AI inference for object/people removal, sky replacement, studio-grade 3D relighting, and local face retouching. Building these to run smoothly on iPhone hardware while keeping memory footprint low was a huge engineering hurdle.

3D Graphics & Shader Effects: Added 3D typography (extruded text with materials like chrome, jelly, and glass) plus 160+ stylized image effects.

Video & Live Photo Engine: Built a multi-track timeline supporting speed curves, kinetic typography, and Live Photo animations.

Privacy First: Every depth map computation, face mesh calculation, and AI model run strictly on-device—zero user photos uploaded.

Questions for fellow builders:
How are you balancing on-device model size vs. output quality in mobile apps?

For those who do big feature updates, what onboarding flows have worked best for you to introduce new features without overwhelming existing users?

Would love to hear your feedback, thoughts on the UI, or critique!
🍏 App Store: https://apps.apple.com/us/app/fine-photo-editor/id1391571907
🌍 Web: https://fine.youthpe.com

A few weeks ago I was on holiday in Cornwall and went into a public toilet where someone had written a message on the mirror.

It said “Have a fantastic Sunday! Hopefully it will stay dry and you can all make the most of it!!”

I thought it was quite a nice thing for someone to do, just leaving a little message for whoever happened to use the toilet that day, and I checked back each morning to find a new message.

It gave me an idea and I’ve spent the last few weeks building On The Mirror⁠, where a new message appears on a virtual mirror every day.

Anyone can submit a message, and each day one is randomly picked to appear on the mirror. It could be something positive, funny, thoughtful or just something you want to say to a complete stranger.

There’s no liking or voting on messages, everyone gets the same one each day.

The site is now live and I’m hoping to get enough submissions coming in to keep it going for a while.
It’s been a fun little project to work on and I’d be interested to hear what people think, especially if there’s anything I could improve.

I’ve shared it with my family and have had a few messages submitted by them. Some feedback from one of my sisters was that I should build an iPhone widget that shows the new message each day. Another suggestion was to use the webcam/front facing camera as the site background so it looks like an actual mirror.

Both of these ideas are in the pipeline.

I’ve also been thinking about whether I could use the project to support a charity like Mind, as I think the idea of leaving positive messages for strangers fits quite nicely with mental health and wellbeing.

Would be interested to hear what people think of those ideas, or if there’s anything else you’d like to see added.

Last week, I launched Undertone, a little AI side project I’ve been working on.

The idea is simple: pick five things you love (films, TV shows, books, songs), have a short conversation with an AI, and discover an unexpected pattern connecting your choices.

I wanted to explore whether AI could go beyond generic personality descriptions and uncover something genuinely interesting about someone’s taste.

After spending weeks experimenting with models, refining prompts, building the experience, and getting everything ready for production, I finally launched it at 99p.

One week later, I’ve had my first few paying customers! 🎉

It’s a tiny milestone, but seeing people discover something I built and decide to pay for it, without me personally approaching them, has been incredibly rewarding.

The biggest lesson so far? Building the product was the easy part. Getting people to discover it, understand what it does, and trust it enough to pay for an experience they haven’t tried is an entirely different challenge.

I’ve been experimenting with LinkedIn, Reddit, and a few communities to understand what resonates. Some posts get engagement, others disappear into the void. And occasionally, Reddit removes them before anyone even sees them. 😂

I’m still learning, and my immediate goal is modest: get to 25 genuine paying customers and see what I can learn along the way.

If you’re curious, Undertone is at findyourundertone.com. I’ve also put together a short video showing how the experience works.

For those who’ve launched small consumer products, what helped you get past those first few customers?

Would love to hear your experiences!

I built Styx because I was drowning in windows. Half a dozen repos open, a coding agent running in each one, and a mess of credentials for every service those agents needed to actually ship anything.

Styx pulls all of that into one place. Every repo you’re working in, the agents building in them, and the logins they need, switchable from a single window.

The name is deliberate. Nothing crosses the river without you. If an agent wants to deploy or touch live data, it stops and asks first. That’s the whole point: let the agents move fast, but keep a hand on the gate.

Website: https://heystyx.com/

Github Repo: https://github.com/NicholasFlemmer/styx-app

For the past month, I've been working on a project called Falbor. It's a platform where you can connect your website, and an AI agent analyzes your product to help you find ways to promote it and get more traffic. I really want to build a cool community around Falbor, where people can contribute to the GitHub repo, make changes, and help me improve the code.
Here's the repo: https://github.com/falbor-devs/falbor
If you think this project could help you, I'd really appreciate it if you gave it a star!

Today I learned refresh tokens and short expiry

Then I made an signup end point.

I work at Autonomous. Here we’ve been building Intern, a small desk device that runs an AI agent for you around the clock. A few people asked why it’s a box and not just an app, so here are the three decisions that shaped it, plus what we gave up for them: https://www.autonomous.ai/intern

1. The agent gets its own place to run
Most agent setups live on a laptop, which means they stop the moment the lid closes. We wanted the agent somewhere that stays on, separate from the computer you actually work on. 
Intern is a 4.7 inch cube built on an Orange Pi 4 Pro (8-core ARM, 6GB LPDDR5, 64GB storage expandable to 256GB), powered over USB-C and connected over Wi-Fi 6. So it sits on your desk and runs all day. 
Say you set up a morning summary or ask it to watch a GitHub repo. That keeps going overnight, and the result is waiting in your chat when you wake up, whether your laptop was on or not.

2. It comes with an agent, but you’re not locked in
Setting up an agent from a repo can take a whole weekend of keys, errors, and trial and error. So Intern ships with OpenClaw or Hermes already installed. Under the hood, the OS treats the agent as a swappable piece: Hermes, OpenClaw, PicoClaw, Codex, Claude Code, and OpenCode all sit behind the same gateway, and the agent’s personality lives in a plain markdown file called SOUL.md rather than in code. 

If you already have your own setup, the developer edition gives you an open shell to install the agent you use.

3. You talk to it where you already are
We didn’t want another app you have to remember to open. Setup happens once in the app: add Intern, pick your Wi-Fi, and it handles the pairing. After that you just message it through Telegram, Slack, Discord, iMessage, or voice. 
To teach it something new, you can grab a skill from the Skill Store, or type what you want in the app and it’s ready the next time you talk to it.

The OS is open source if you want to poke around: https://github.com/autonomous-ai/Physical-AI-Operating-System

If you’ve built something that needs to run all the time, did you go with dedicated hardware or a server? Would you make the same call again?

I can spend hours coding, fixing bugs, and shipping features.

Then I open X to share what I did…

“shipped some updates today.” 💀

So I started building Shipstory.

The idea? Connect GitHub, turn real commits and PRs into post drafts, and stop staring at a blank page.

No made-up achievements

No generic AI fluff

Just the work you actually did

I am still building it. Planning to launch in the next 2 to 3 days... 👀

Curious about other builders here:

How do you turn your daily coding work into something worth sharing? Do you keep notes, use AI, or just wing it?

Today, sending a message across the world takes seconds. But moving money internationally can still involve intermediaries, multiple fees, currency conversions, and delays.

It makes me wonder what finance will look like 10 years from now.

What if international payments became nearly instant? What if businesses could receive money from customers anywhere in the world without worrying about complicated payment systems? What if AI handled personal budgeting, automated savings and financial decisions in the background?

We're already seeing digital payments, stablecoins, tokenized assets and AI driven financial tools evolve.

But the bigger question is whether the future of finance will simply make today's systems faster or completely change how we think about money.

What do you think will fundamentally change finance over the next decade: AI, blockchain, or something we haven't imagined yet?

Yesterday

I went back through Armor to understand it better and read up a bit. My friend and I also talked about Orient: how useful it could be for vibe coders, and whether it could grow into an ecosystem instead of staying a single plugin. Nothing shipped.

Lesson

A comment on Day 2 stuck with me: a folder on your own machine isn’t a safe boundary for an AI system. Anything it can read can leave with it.

Question for you
If you vibe code, what do you lose track of most as a project grows?

On subs like r/forhire, r/slavelabour and r/DesignJobs, about 3 in 4 posts are people advertising their own services or spam. The real jobs are in there, but you scroll past a lot to find them, and a fair number of what's left are scams.

So I made Only Hiring: https://onlyhiring.hassandev.me

How it works:

A scheduled job pulls new posts from about 19 hiring subreddits. Anything tagged [For Hire] or [Offer] gets dropped before any LLM call, which costs nothing and catches a lot of the noise. An LLM reads the rest and decides whether someone is actually hiring. For the ones that are, it writes a short summary and pulls out the pay, role, work mode, location and skills. It also gives each post a scam score from 0 to 1, based on signs like upfront fees, Telegram-only contact, requests to rent your account and payment in crypto. Posts at 0.4 or higher get a warning, and at 0.6 or higher they're hidden unless you choose to see them. Reposts are collapsed into one listing.

The site is Next.js on Vercel, reading from a Neon Postgres table through a role that can only SELECT. The dataset is small enough that filtering and search run in the browser, and the filters are kept in the URL so you can share a filtered view.

I made a couple of choices on purpose. I don't store post bodies; you get my summary and a link back to Reddit, which is where you apply. And there are no accounts or analytics at all. If you mark a job as applied, that's saved in your browser's localStorage and nowhere else.

What isn't great yet: Many job posts don't share budgets or salaries, so it's hard to filter job posts with price. This is a problem with the people posting vague jobs, but I wonder if I could fix this better on my end too. Also, deleted Reddit posts can also stay listed for a while before they drop off.

The website code is open source: https://github.com/hassanaziz0012/only-hiring. The scraper and grader live in a separate private repo.

I'd like feedback on two things: whether each listing tells you enough to decide if a job is worth opening, and whether the scam warnings feel useful or just noisy.

I have a faceless YouTube channel and editing my far took the longest time. I used to post once per week and even that took my such a long time to edit 10 minute videos, in addition to researching about a topic, writing the script, and recording my voice.

So I built Kinetic: an AI agent that helps me with my full end to end video making process.

I give it an idea for a video and it:

• Does the research + script writing that I can edit
• Uses a selected style and a voiceover for the video
• Generates a full motion design video that matches the voiceover timing

This helped me start posting 3 times a week consistently for the past few months, and grew my channel to over 10k subs, from 3k subs before using this.

Try it here and would love some feedback!: https://kineticvideo.app/

(Video made with Kinetic)

In August I asked here how you find your first testers. Got a lot of good answers, and whoever told me not to start with friends was right.

What happened since:

• shipped the core thing. 3 short lessons a day picked for you
• spent like a month making lesson generation faster and cheaper. went from ~4 min to ~2 min per lesson and about half the cost
• set a price: $14.99/mo or $129.99/yr, 20 lessons a month. first lesson is free
• paying users: 1 )

My biggest mistake was living in “almost ready” mode. I kept polishing instead of showing it to anyone.

Next 2 weeks I have one goal: 20 strangers try it and 5 of them tell me what’s wrong.

If you want to be one of them: noemacreate.org, or DM me.

Where did your first 20 users actually come from?

[ Removed by Reddit on account of violating the content policy. ]

sharing an honest update because this one caught me off guard. the actual building part of my project has gotten quick, i can turn a rough idea into something usable in a couple of days now. i expected that to feel freeing. instead it exposed the real gap, which is that i do not actually know my users well enough to know what to point that speed at. i shipped three things this month and only found out afterward that people wanted none of them. the twist for me is that being able to build fast made my lack of customer understanding painfully obvious. how do you build real conviction about what to make next?