r/buildinpublic

▲ 606 r/buildinpublic+28 crossposts

I built FaceGate — World's first macOS app locker with on-device Face Unlock (Open Source)

If you hand your laptop to someone for a few minutes, they can still open Messages, Photos, Notes, Mail, WhatsApp, browsers, password managers, and other personal apps. I wanted a way to protect specific applications without constantly locking my entire Mac.

I looked around for solutions, but most were outdated, paid, abandoned, or didn't feel native to macOS.

So I built FaceGate.

FaceGate is a native macOS app that lets you lock individual applications and unlock them using Face Unlock, Touch ID, or a password.

A few things I focused on from day one:

  • Everything runs locally on your Mac
  • No cloud processing
  • No accounts
  • No telemetry
  • No subscriptions
  • Fully open source

Features:

• Face Unlock powered entirely on-device using Apple's Neural Engine - little impact on cpu and gpu resources.
• Fast authentication with very low memory and CPU usage
• Liveness detection to prevent photo and video spoofing attacks
• Touch ID and password fallback
• Per-app unlock timers
• Automatic re-lock on sleep, wake, or screen lock
• Custom schedules for automatic lock/unlock periods
• Tamper protection that prevents FaceGate from being quit, disabled, or uninstalled without authentication
• Runs quietly from the menu bar with minimal system impact.

The entire project is written in Swift and designed specifically for macOS.

This is still actively being developed, and I'd genuinely love feedback from Mac users.

Some questions:

  • Is app-level locking something you've wanted on macOS?
  • Which apps would you personally lock?
  • What security or privacy features would you like to see added?

Website: https://facegate-applocker.vercel.app/

GitHub: https://github.com/dweep-desai/FaceGate-Mac

If you think I did a good job, please feel free to leave a star on my github repo - means a lot to me.

Feedback, feature requests, bug reports, and contributions are all welcome. I'd love to hear what you think.

u/AceReviewer — 1 hour ago
▲ 272 r/buildinpublic+5 crossposts

I made a few improvements to my Jeep Renegade outdoor office

I've been improving my outdoor office based on the feedback from my previous post.

A few changes so far:

• Better workspace organization

• More comfortable setup

• Easier access to everything

• Cleaner cable management

The goal isn't to build a camper.

I'm a full-time remote software engineer, and I simply wanted an office that lets me work from parks and outdoor spaces.

I'm still experimenting with power, internet and ergonomics, but every week it gets a little better.

What would you improve next?

u/CurrencyPersonal8640 — 3 hours ago
▲ 74 r/buildinpublic+6 crossposts

you roasted my baby name site last week. I shipped every single complaint. round 2

Last time I posted here, someone pointed out that my "Origin and Meaning" section

contained neither the origin nor the meaning. He was right. Noah was showing up as

Germanic. Noah.

So instead of arguing I spent the week shipping the whole thread:

- Real meanings and etymology now, with the dictionary source cited right under each one

- Added official birth records from England, Scotland, Ireland and France, so you can

see where a name is actually popular right now

- A "% of babies" view, name days (with an explanation, because nobody knows what

those are), fictional characters, similar-sounding names

- Every section shows a small badge for where its data comes from

The idea behind the site is simple: name sites mostly copy meanings from each other

and cite nothing. I want the one where you can check every single fact yourself.

Free, no accounts.

Round 2. What's the first thing you'd check to decide whether you trust a site

like this?

namestrace.com
u/chadbigd — 4 hours ago
▲ 12 r/buildinpublic+8 crossposts

App was available on the App Store for a few hours, then suddenly became unavailable in all regions

Edit: After several tests, it has become clear that the app is available in the USA and the page does not open in the EU. However, you can search for and download the app from the list in the EU, but you cannot click on it. Thanks to everyone.

Hi everyone,

I’m hoping someone here has experienced this before.

I recently launched my very first iOS app. The app was approved by Apple and the status in App Store Connect is currently “Ready for Distribution”.
For the first few hours after release, everything worked perfectly:
The App Store page loaded normally.
Users could open the product page.
The app could be downloaded.
However, a few hours later, the App Store page suddenly stopped working on all iPhones.
When users tap the app in the App Store, they either get:

“This app is currently not available in your country or region”

or

“The page could not be loaded. Please try again.”

Things I’ve already verified:
App status is “Ready for Distribution”.
Distribution method is Public.
The app is available in 175 countries, including Belgium.
No pre-order is enabled.
No changes were made after release.
The App Store URL exists.
“View on App Store” from App Store Connect opens correctly.

Example App Store link:
https://apps.apple.com/us/app/elsy-shared-collections/id6773616091

I’ve already contacted Apple Developer Support, but haven’t received a response yet.
Has anyone experienced something similar? Could this be an App Store propagation issue or some hidden regional/storefront problem?

Thanks a lot!

u/EggplantSalty2486 — 4 hours ago
▲ 29 r/buildinpublic+7 crossposts

Local coding models need better repo context, not just bigger context windows

Local coding models have a repo-context problem.

When using llama/qwen/mistral/gemma for coding, the hard part is often not the model itself. It is getting the right files/functions into context without dumping too much raw source.

Long context helps, but it does not solve retrieval.

If the model never sees the right file, it still guesses.

I’ve been building SigMap, a zero-dependency CLI that creates a compact repo map for coding workflows.

Instead of sending raw source first, it extracts:

  • function signatures
  • classes/interfaces
  • exports
  • import relationships
  • ranked file matches per query

The workflow is simple:

repo map first → find likely files → read full source only where needed

Benchmarked across 18 repos / 90 tasks:

  • 81.1% hit@5 vs 13.6% random baseline
  • ~6× better file retrieval
  • 96.9% token reduction in the benchmark setup
  • 41.4% fewer prompts per task

No embeddings. No vector DB. No npm dependencies.

This is not meant to replace LSPs, grep, agent search, MCP tools, or full-file reads.

It is meant to give local coding models / agents a cheap first-pass structure map before deeper inspection.

Repo: https://github.com/manojmallick/sigmap

Benchmark suite: https://github.com/manojmallick/sigmap-benchmark-suite

Curious how people here handle repo context with local coding models.

Are you mostly using grep/search, RAG, repo maps, MCP tools, or just relying on longer-context models?

Edit: Good point from the comments — SigMap core is model-agnostic. The docs currently look too focused on proprietary assistants, so I’ll add clearer examples for VSCodium/Open VSX, Continue, Cline/Roo Code, Aider, OpenHands, and local Ollama/llama.cpp workflows.

u/Independent-Flow3408 — 6 hours ago
▲ 149 r/buildinpublic+62 crossposts

I developed Weather World because I wanted a simpler, more helpful way to stay ahead of the forecast. I truly believe that a weather app should be a tool that makes your life easier, not a source of distraction with ads and confusing menus.

How it helps you: The core of the app is all about visual clarity. I’ve focused on creating intuitive graphs that let you see temperature shifts and precipitation trends at a single glance. Instead of reading through long lists of numbers, you can visualize exactly how your day will unfold. It’s minimalist, lightweight, and built for speed—perfect for anyone who values a clean Android experience.

I’d love your support! Please give it a try and see if it helps your daily routine. If you find it useful, please recommend it to your friends! As a solo developer, your support and word-of-mouth are what help me improve and grow.

In compliance with the community rules, I’ve shared the link via IndieAppCircle. Check it out there and let me know what you think!

Find it here: https://play.google.com/store/apps/details?id=com.danie.pocasisveta

u/Tough_Deer_3756 — 9 hours ago

What have you built this week? Drop it in the comments!

I've been working on something called The Capital over the past few weeks.

Most AI directories are useful for getting a listing, but after that there isn't much reason to come back. I wanted to experiment with a different approach.

Instead of only listing products, founders can join a weekly community competition where people vote for their favorite AI tools. Every week there's a live leaderboard, so builders can keep improving their ranking and share it with their audience.

The top 3 projects each week receive:

🏆 Featured placement on the homepage
📬 A feature in the newsletter
⭐ A permanent place in the Hall of Fame
✍️ A Founder Spotlight article

Last week 72 founders took part, and seeing founders support each other's launches has been the most rewarding part of building it.

Right now it's free to join while I continue improving the platform based on founder feedback.

If you're building an AI product and think it would fit, leave a comment or send me a DM and I'll explain how it works.

And if you're not building AI...

What are you working on this week? I'm always looking for interesting projects to follow.

reddit.com
u/National-Rip3620 — 8 hours ago
▲ 5 r/buildinpublic+3 crossposts

My back and neck were wrecked from sitting all day, so I built an app that physically won't let me ignore it

Desk job = chronic neck/back pain, and every "take a break!" app failed the same way: notification pops up, I dismiss it in half a second, nothing changes.

So I built ErgoGuard. When the break alarm fires you can click on the notification, and it opens your camera and uses on-device pose detection to watch you actually do the movement (squats, arm raises, neck stretches, etc.) and count real reps before you can dismiss it. Short, low-effort movements (30 sec–2 min) — not a workout. Fully on-device, no video ever recorded or sent anywhere. You set your own schedule and work hours. Manual fallback if the camera can't see you.

📱 iOS: https://apps.apple.com/app/ergoguard-b612d0/id6779917035
🌐 Details: https://ergo-landing.vercel.app/

One-person side project — feedback welcome, especially if you try it for a day.

u/Embarrassed_Ruin_588 — 5 hours ago

Finally reached 10k downloads :)

Hey reddit, I don’t have anyone to share this with, so here we go. This weekend I reached the goal of 10.000 downloads for my app! Six months ago I was dreaming about this and now it finally happened. (Even though some downloads are redownloads) Since I made the app available for free, I thought this might be easier, but I feel like I fought for every download. There was a lot of struggle and disbelief involved the last two years, I was almost convinced that nobody will care about the project at some point. Reddit helped me out a lot, I had many people write me dms which kept me going. Thank you, sincerely! The numbers almost look fake, since it’s exactly 10k downloads and 100 reviews, but that’s just a coincidence. Hoping to get more reviews from now on. Well, I am just really happy I have reached the first goal of this year. And if you feel like you need hear this: build that project, keep working on it, let people know what you working on. If you don’t quit, you will succeed at some point.

u/oasisaudiolab — 5 hours ago

let's self promote, what are you working on this weekend

Working on FeedbackQueue, a free to use feedback-for-feedback platform for founders to get feedback and testers without, commenting, posting, DMing, SEO, ads, or doing any marketing bs. Not even looking for them.

958 founders already, building our way to 1000 users. (hopefully before Monday)

welcome to the queue, guys.

reddit.com
u/Live-List8000 — 12 hours ago
▲ 216 r/buildinpublic+18 crossposts

I Built a Free, Open-Source Local Windows Launcher That Searches Almost Everything on Your PC

Problem

Windows Search has always felt too limited to me.

It can open apps and sometimes find files, but when I actually want to search my PC properly, it usually falls apart.

I want to search and use features like:

- Text inside files, code, and images

- Browser bookmarks and history

- Clipboard history

- Git commits

- Windows settings

- Local commands

- Local agents for Windows

Windows Search is not powerful enough for this workflow.

So I Built OmniSearch

OmniSearch is a fast, lightweight, local-first Windows launcher that opens with:

"Alt + Space"

You can also set your own custom hotkey.

It gives you one search box for your PC.

Instead of only searching apps or basic file names, OmniSearch can search across:

- Apps

- Files and folders

- Content inside files, supporting 50+ extensions

- Image OCR text

- Browser bookmarks and history

- Clipboard history

- Git commits

- Windows settings and Control Panel pages

It also features an AI agent powered by Hermes and includes a powerful clipboard manager that gives you features no other Windows clipboard manager provides.

The goal is simple: Find everything on your PC from one shortcut.

Why is OmniSearch better than Windows Search and other popular launchers?

- Free and open source

- Local-first

- Lightweight

- Designed to run easily on low-end Windows PCs

- Image OCR text search

- Blazing-fast search of content inside files, supporting 50+ extensions

- Blazing-fast search over centralized PC history, including browser history, Git commit history, clipboard history, and file history

- Hermes agents for local Windows tasks and long autonomous tasks

Links

Free and open source.

GitHub: https://github.com/PranshulSoni/omnisearch

Website: https://omnisearch-windows.vercel.app/

Feedback

I am currently maintaining OmniSearch, and honestly, I cannot find and fix every bug alone because building a launcher like this on Windows is genuinely hard.

I would love feedback from people who use Windows every day.

If OmniSearch solves a problem for you too, please consider leaving a star on GitHub.

If you have ideas, find bugs, or want to improve something, feel free to open an issue or contribute to the project.

Your feedback is always appreciated.

u/Big_Biscotti_4664 — 16 hours ago
▲ 3 r/buildinpublic+3 crossposts

built a tool that scores your CV instead of just saying "looks good!"

Solo dev, been building this for a few months on nights/weekends. got tired of how bad CV feedback usually is: either a friend skims it and says it looks great, or you pay $50/month for a tool that spits out a vague score with no real explanation.

cvcheck.app does one thing: paste a portfolio link or GitHub profile, or drop a PDF, no signup, and it scores your CV out of 100. tells you what a recruiter notices in the first 7 seconds, whether it survives an ATS parse, red flags ranked by how bad they actually are. paste a job description too and it matches your CV against that role and shows what keywords you're missing.

Free tier is the real score, not a teaser. €1.99 once, not a subscription (still don't get why every competitor here is $50/month), unlocks the full report: rewritten bullets, a cover letter, a clean rewrite ready to download.

Built with Next.js, Supabase, and Claude for the actual analysis. still early, mostly fixing things people find rather than shipping big new features. if anyone tries it at cvcheck.app, would rather hear "this part is wrong" than "cool idea."

u/ByteYTGG — 7 hours ago
▲ 5 r/buildinpublic+1 crossposts

Should you validate your product before spending money on Google Ads?

I’ve been thinking about this a lot.
There are two completely different approaches:
Approach 1: Build an MVP, validate demand organically, talk to users, iterate, and only then start spending on Google Ads, Meta Ads, X Ads, etc.

Approach 2: Launch quickly, spend money on ads from day one, and let the market tell you whether people actually want it.
Which approach has worked for you?
If you’ve built multiple products:
Did you validate first?
Or did paid marketing become your validation?
At what point did you decide it was worth spending real money?
Looking back, what would you do differently if you were starting from scratch today?

reddit.com
u/crack-dev — 7 hours ago

I was in desperate need for a reddit marketing tool.

A few days ago I asked people here about what tools they use. While I did not yet publish a tool I made for myself to help me with the marketing/engagment on reddit, a few were ready to try it.

Its invite only and free now (BYOK). I would DM you the link if you want. It would be fun to discuss with you the pros and cons of it!

Keep building!!

reddit.com
u/Tall-Explanation-476 — 12 hours ago

Lessons I learned 6 months into building my SaaS (40 paying customers)

Six months ago I launched my SaaS. Today it has around 40 paying customers.
It’s still tiny by startup standards, but it’s enough to have made a lot of mistakes and learn what actually matters. If you’re building your own SaaS, maybe some of these will save you some time.
1. Don’t waste time on ads too early
I spent far more time thinking about paid acquisition than I should have.
Until you know exactly who converts and why, ads are just an expensive way to learn. Organic channels gave me much better feedback.
2. Do whatever you can to get real user data
Analytics are useful, but conversations are better.
Every support call, onboarding session and email taught me something that dashboards couldn’t. The goal isn’t just getting users—it’s understanding what people are actually willing to pay for.
3. Start with a lower price
Pricing is surprisingly emotional.
A lower price made it easier to remove friction while I validated the product. Once I understood the value customers were getting, increasing pricing became much easier.
4. Keep expenses painfully low
Early on it’s easy to convince yourself that every tool, AI credit or subscription will accelerate growth.
Most of the time, it won’t.
If you can build it yourself or solve it manually for now, do that. Every euro you don’t spend extends your runway.
5. Know what your brand stands for
One of the biggest traps is building features because competitors have them or because one customer asks for them.
Not every request should become a feature.
Your product should become better at solving one specific problem, not average at solving twenty.
6. Not every customer is your customer
This one surprised me.
Some users generate lots of support requests, ask for endless customisations and ultimately pay very little.
Others sign up, understand the product immediately and become long-term customers.
Finding more of the second group matters much more than trying to satisfy everyone.
7. Take the calls
This probably isn’t scalable.
Do it anyway.
Every call uncovers objections, confusing UI, missing documentation and new opportunities. Those conversations eventually become product improvements, better marketing and more revenue.
8. SaaS compounds
The first few months can feel painfully slow.
But every blog post, customer review, feature improvement and SEO page keeps working for you long after you’ve published it.
Momentum is hard to see day to day, but obvious when you zoom out.
9. Trust your own judgement
You’ll hear conflicting advice from customers, founders, Reddit, YouTube and Twitter.
Listen to everyone.
Copy nobody.
You’re the one who understands your product, market and long-term vision.
10. Put pen to paper
Writing forces clarity.
Whenever I felt stuck, writing helped me understand what I actually believed, what customers really wanted and what the next priority should be.
11. Ask for Google reviews
Happy customers usually won’t leave reviews unless you ask.
A simple request after solving a problem has generated far more reviews than I expected, and those reviews build trust for future customers.
12. Write lots of blogs
I underestimated content marketing.
Every useful article becomes another opportunity for someone to discover your product through Google months later.
Unlike social media, good content keeps working.
13. Learn basic SEO
You don’t need to become an SEO expert.
Just learn the fundamentals:
Use Google Search Console.
Add structured data (schema) to your articles.
Answer specific questions people search for.
Publish consistently.
SEO has become one of my favourite acquisition channels because every article can continue bringing visitors long after it’s written.
My biggest takeaway
Building a SaaS isn’t about one viral launch.
It’s hundreds of small improvements that compound over time.
Six months in, I have around 40 paying customers. That’s nowhere near where I want to be, but it’s enough to know that consistency beats shortcuts.
I’m curious—what lesson surprised you the most during your first year of building?

reddit.com
u/BoysenberryWhole8759 — 10 hours ago
▲ 50 r/buildinpublic+4 crossposts

+600 People Chose HabitRail ❤️

A few months ago, I had an idea.

I wanted a habit tracker where your habits actually belong to you.

No accounts.
No subscriptions.
No ads.
No cloud.
Just your data, stored on your own device.

So I started building HabitRail.

Today, I checked the Play Console and realized something that honestly made my day...

More than 600 people have installed it. ❤️

I know 600 isn't millions, but as a solo developer, seeing hundreds of people around the world use something I built is surreal.

One thing that surprised me the most is how many different countries it's reached.

To make HabitRail accessible, I translated it into 17+ languages, and now people from all over the world are using it to build habits, track streaks, and stay consistent.

Every download, every review, and every piece of feedback has helped shape the app into what it is today.

Some of the features users asked for have already made it into the app:

  • Local backup & restore
  • Streak Freeze
  • Calendar history
  • Detailed statistics
  • Custom reminders
  • Daily, weekly, and custom habits
  • Completely offline
  • No account required

And I'm not stopping there.

I'm currently working on home screen widgets, so you'll soon be able to check your progress and complete habits without even opening the app. They'll be coming in one of the next updates, and I'm really excited to share them.

I still have a long list of ideas I'd love to build.

If you'd like to support an indie developer, the biggest things that help are:

  • Trying the app
  • Leaving an honest review
  • Sharing feedback (good or bad)

It genuinely keeps me motivated to continue improving HabitRail.

Google Play:
https://play.google.com/store/apps/details?id=com.hzfapps.habitrail

Thank you to every single person who's downloaded HabitRail.

Here's to the next 600. 🚂❤️

u/Practical-Care-7408 — 12 hours ago

Should I look for ICP in other places? Or my ICP just doesn't exist

Hey developers, I launched a product a week ago and looking for beta testers, even provided service for free, but still no one willing to try.

Briefly describe the product: it's a "user instant thought capturer", in a cool way to put it. Normally, it involves having an AI team take over handling user feedback automatically.

the usual way of collecting feedback is an input box plus a 5-star rating. it's simple, and mostly passive — no follow up + typing cost effort + user forget the "feeling" when asked later, which makes users don't bother to engage and you get very little signal back.

So i did a proactive conversational AI chat bot widget. It can pop up programmatically at the correct moment and talk to users when their experience are fresh and backend summarizer.

some example moments where this actually kicks in:

  1. you're unsure about product direction, can use it to learn your users' real workflows.
  2. a user clicks upgrade, then bails halfway and closes the survey. Pop up and engate.

I searched and DMed ~20 indie founders(reddit and X) and provide free service, their users base from dozens to hundreds. No one seems interest, so I am wondering:

  1. The most urgent things for independent developers are finding users and marketing. My product is not the most urgent thing, so should I exclude them from ICP?
  2. Should I reach out to bigger developers with hundreds or thousands of users who are already in need of large-scale user feedback? Or did I just trying to solve a fake problem?

Really, sincerely want to hear your opinion on this. Thanks!

reddit.com
u/wrt418 — 9 hours ago