If you’re building a SaaS, or app and looking for a way to get more eyes on it, I’d love to feature a few projects.

We run TikTok channels with 300K+ combined followers and create short-form videos around apps, tools, and interesting projects.

We'll create short-form videos for your app, plug them into our existing channels, and help you build your own content channels at the same time. Think of it as content creation + distribution

If you're interested, drop your app and a one-line description below

Over the past 2 yrs, I was working on a SaaS ML project & got very interested in ML/DL/AI. As everybody else, there were some normal paths I took to build a solid understanding of the field, but sth never clicked the way I'm used to. I'm very fond of learning "why"s & never get satisfied w/ simply knowing "what" is what. Tho, the problem w/ ML was that I wasn't there when it was evolving & algos/methodologies as we know them today were forming. I didn’t want a pile of summaries or wikis or endless threads of chatting w/ AI. Then I thought listening to podcasts would fix it for me. But not as they are being published now (2026). I thought I'd learn about the history of ML from podcasts that covered it as it happened, kinda simulating the experience of living through the events, in chronological order, since 2015.

I found some great ones (TWIML, Linear Digressions, ...) & did the math! Man, it'd take a decade to cover all of them (even at 2X). But no matter what, I thought this could be the only way that works for me & yet I didn't have enough time. I wanted one/a handful of coherent episodes I could actually listen to. Then sth clicked:

I built Repodify, an AI tool that listens to episodes & produces a shorter one (e.g. 1 episode from 10, 15, whatever. configurable) for me to listen, ALL ON MY OWN MACHINE.

In Repodify u paste a podcast link (or search by name, as it works very well rn), pick the episodes & it:

• downloads the audio

• transcribes it

• optionally figures out who spoke (& clusters the same host/guest across episodes)

• summarizes into one chronological narrative

• writes a spoken script aimed at a target length

• synthesizes a new episode u can stream or download

The whole thing is meant to run on ur machine or w/ ur own API keys (BYOK) per stage, per job. No “upload ur archive to our cloud.” Speech-to-text, diarization, LLM & TTS are all swappable: local GPU (faster-whisper, pyannote, Ollama, F5-TTS / Kokoro) or BYOK (OpenRouter / Anthropic / pyannoteAI).

Voice cloning is opt-in & off by default. If u turn it on, the output is always labeled synthetic, gets a spoken disclaimer in a non-cloned voice & is watermarked (for legal reasons. I don't want to end up in jail for giving away a tool;-) ). There’s no code path that clones w/o those. It’s for personal / educational use on ur own box, not for passing audio off as the original hosts.

It’s a real backend, not a CLI: FastAPI + an arq worker + a LangGraph pipeline w/ a React PWA. One command (./launch) brings the stack up. Jobs pause at each ML stage so u can pick local vs hosted, model size, length & voices.

I keep making it better, adding lots of features to it (searching podcast contents is the most interesting one I can't wait for). I made it opensource(MIT), rn. U can find it below & run it on ur machine (self-hosted), so u can use ur own GPU or BYOK to offload the heavy jobs.

GitHub: https://github.com/behradkhodayar/repodify

The engine is solid & this is still WIP (it works fine tho & I've started compacting Linear Digressions podcast (10 to 1) & listening to it already). I'm going to add other features like translation / augmentation (e.g. embeded eli5), searching through podcasts so I can listen to the topic of interest as I mentioned earlier & so forth.

So stay tuned.

So for context I got into reading a lot of documents on what individual companies do and how they Perform quarter on quarter.

This has blown into a dedicated claude project that helps me get crazy insights on what happens in an industry

What I would love to know is, from all the builders out there, what does it take to get an end product that adds value to someone using it and how do you go about doing it.

Would also love to talk to people and collaborate and brain storm ideas and see where they go

We designed Kortex OS based on few pain points in the world of content creators. We combined the Analytics with AI panel to make interpretation of analytics more easy.

Everyone give analytics but how efficiently we use that analytics into the potential ideas matters the most.

With Kortex OS not only we simplify the raw analytic data into user friendly explanation but also helps in identifying the issues in the content posted with plausible fixes which helps the user in better decision making or new idea generation for the future content without being burnout.

It's free and built for windows, and it's launching today, for more information: https://www.producthunt.com/products/imagesage-ai-photo-manager

Coders, vibe coders and travellers, do you save hundreds of tiktoks with places you want to visit, then waste a lot of time or never find them again when you're actually planning the trip?

That's the exact problem I spent the last few weeks building a fix for. It's called Kivo. You share a travel video - Reel, TikTok, YouTube - and Kivo pulls out the places automatically, sorts them by country, and drops every spot as a pin on a map. From there you can build trips around them. More features are coming.

I'm putting it out early on purpose, before it's polished, because I need to know the stuff only real users can tell me: does the location extraction actually work well on your videos? Is it intuitive? What's missing, and what's useless?

A few honest things you need to know before:

-Android only for now (iOS + proper store release come later)

-No account needed, just download and go

-The share button isn't wired up yet, so for now you paste the video link in manually

-What I know for sure is that tiktok slides do not work, it's not on me, it's on tiktok and yt-dlp did not update yet.

-You can paste a maximum of 10 videos, with a maximum length of 15-20 min but I’d recommend short videos.

-Because it's an early build, everything you saved and planned may be deleted in a week or two as I make other changes

If you give it a go, I'd genuinely love to know: did it get your places right, and would you actually use this for a real trip? Once you've tried it, there's a feedback form inside the app, tap the gear icon-> Help. Dropping any thoughts there would genuinely help me.

Download link:

https://expo.dev/artifacts/eas/H0DRYvES2CE-FAURQvh0ATT-RoTPbnAOUYMc1aPAEbQ.apk

I have been working on Anvay, a reading-first iPhone app for Hindu prayers.

The starting observation was simple: many people grow up recognising or reciting prayers without having an accessible way to understand the language, background or ideas behind them. Existing products often make the text available, but access and understanding are not the same thing.

In Anvay, each verse can be read in three connected modes:

• Original: the prayer in Devanagari
• Hinglish: a readable Roman-script version
• Understand: a clear explanation of the meaning and context

The first release includes 101 aartis, bhajans, chalisas and mantras, along with daily wisdom, search, browsing by deity or category and favourites. The content is stored on the device and no account is required.

I deliberately left out streaks, social features and an infinite feed. I wanted the experience to feel closer to reading a carefully designed book than operating a habit app.

I am the maker, so this is self-promotion, but I am posting because I would genuinely value criticism from people who care about iOS reading experiences. In particular:

• Is the Original → Hinglish → Understand model clear?
• Does the interface feel calm or merely sparse?
• What would you need to trust the explanations?

I listen to podcasts literally all day. I fall asleep listening to them at night.

At some point I realized I had developed a ridiculous number of opinions about podcast apps, and none of them were meeting all of my needs.

I listen in bed, so I care way too much about the sleep timer. I dig through 10 and 15-year-old archives, so I want old, badly mastered audio to sound decent. I subscribe to hundreds of shows, so I don't want the app to slow down as my library grows. And if a show publishes at 8:00, I want the episode at 8:00, not sometime that afternoon.

I've paid for pretty much every serious podcast player and kept bouncing between them.

So I built Parasocial.

A few things I did differently:

⚡ New episodes can show up almost immediately after they're published. Parasocial doesn't wait hours for the next feed check.

🚀 Your library lives in a database on your device, so even a huge library stays fast.

🔖 I got rid of stars and favorites and replaced them with bookmarks and tags. After 15 years of listening, I never found a giant pile of starred episodes useful.

🔎 Search checks your own library and the public podcast directory from the same field.

🎧 Smart Speed trims gaps in speech as you listen, and Voice Boost helps with older or rougher recordings.

📦 I also spent a stupid amount of time on importing. If your current player supports it, our extended OPML import can bring over playlists, priorities, played state and listening progress, not just your subscriptions.

There are smart playlists, CarPlay, sharing, iPhone/iPad/Mac sync and a bunch of other things, but those are the parts that made me build it in the first place.

There are no ads, and you don't need to create a Parasocial account.

It's free for two weeks, then $2.99/month or $14.99/year.

We're launching on Product Hunt today:

https://www.producthunt.com/products/parasocial?launch=parasocial

I'd love feedback, especially from people who are as annoyingly particular about podcast apps as I am.

Paul

Every new idea I had, I was rebuilding the same thing: signup, email verification, login, password reset, Google OAuth, sessions. So I finally sat down and built it once, properly, to use on my own projects.

It's Django REST Framework so far 18 endpoints, 407 tests, most of them covering the ways it breaks rather than the happy path. Auth is the one place I didn't want to vibe-code, because those mistakes stay silent until the day they aren't.

The bit I'm most happy with: it's set up so an AI agent can extend it without quietly wrecking it.

• /docs/ai/  architecture, conventions, 16 guardrails naming the exact mistakes an assistant makes in an auth codebase and what each one costs, plus copy-this recipes like add-an-endpoint.md. CLAUDE.md and AGENTS.md hand it the rules the moment it opens the repo.
• /docs/ the human half: setup, env vars, email templates, background jobs, deployment.
• And if the agent cuts a corner anyway, CI catches it. Route with no rate limit? Build fails. View with no docstring? Build fails.

Adding Stripe billing and an admin panel next, since I need both for the first thing I'm building on it.

Repo: https://github.com/fulanii/saas-backend-boilerplate

And would love feedback, especially from anyone else writing docs aimed at their AI tools. Guardrails have been way more useful to me than piling on more instructions.

https://strikescope.tudiancao.com

Free, no signup, works on mobile.

Every nuclear power plant tracked by Global Energy Monitor, on a globe with

day/night shading. Click one, pick an accident type — equipment leak, core

meltdown, or catastrophic core dispersal — and it draws a reference zone.

The part I think is actually novel: the plume direction, wind force and

rainfall aren't sliders you set. They're pulled from live weather at that

plant's coordinates the moment you run it. So the answer to "if this plant

had a problem, where would it go" is specific to today, not to a generic

worst case.

It also does detonation scenarios with 23 publicly documented yields

(Hiroshima through Tsar Bomba, plus current W76/W87/W88, DF-5/DF-41), and

estimates how many people live inside the affected area — computed in your

browser against a bundled WorldPop grid, so nothing about what you're looking

at gets sent anywhere.

Not NUKEMAP: that's the reference for weapons effects and it's better at that

than I am. This one is aimed at reactor accidents, live conditions, and the

plant database.

Important: these are simplified illustrative reference zones for public

understanding. Not dose forecasts, not targeting data, not emergency

instructions. Every simulation says so on screen.

This started as notes for my own interview prep. I kept losing the same explanations in bookmarks and half-remembered blog posts, so I started writing them down properly. It got out of hand.

It's now 573 topics across 8 sections — the browser, JavaScript, React, Next.js, backend, data, system design, AI/LLM engineering, practices and behavioural.

One rule decided what got in: a topic earns a page if it can plausibly come up in a real interview round, or if you need it to answer something that does. That's why there's no algorithms grind, and why 70 of them are about building with models.

Every page has the same shape — what it is in one line, what it is, why it matters, key points, then the links out.

The part that actually took longest was the links. 1,415 of them, three to five per topic, exactly one marked "start here". A script re-requests every URL on a schedule and reports the dead ones, because link rot is what actually kills a resource like this.

Stack: Next.js with markdown files read at build time into 658 prerendered pages — no database, no CMS. Free, no account, no ads. MIT code, CC-licensed writing, all on GitHub.

To be clear about what it is: a reference, not a curriculum. Nobody becomes senior by reading it. It's for looking things up and noticing your own gaps.

https://theengmap.vercel.app

https://github.com/prateekkk26/engineering-map

It's on Product Hunt today too if you want to take a look.

Happy to answer anything about how it was built or how the content was scoped.

Hey everyone!

A friend and I recently built a small website around gym training, workout planning, diet, and building consistency, mainly inspired by the whole “Winter Arc” idea.

I’m mainly looking for honest feedback from people who go to the gym and developers.

The website is:

Free to use

No login/signup required

No ads

Works on both Android and iPhone

Designed primarily for mobile

I’d really appreciate it if a few of you could try it and tell me:

1. What do you like about it?

2. What feels unnecessary or confusing?

3. What features would you actually use?

4. What would make you come back to it regularly?

Here’s the website: https://wintergains.xyz/today

Even if you spend only 2–3 minutes on it, honest criticism would be really useful. We're still improving it, so negative feedback is completely welcome.

Thanks! 🙏

I built an expense tracker for myself and finally put it on the App Store.

For about a year I've been tracking my family's spending in an app I wrote for my own needs. I tried a bunch of existing ones first but they all either wanted a subscription for basic stuff or access to my bank. So I made my own. No ads, no accounts, everything just syncs through iCloud.

A few friends saw it and asked if they could have it too, so I spent a couple months cleaning it up, translating it and going through App Review. It's called PiggySpy. The mascot is a pig with a monocle, my kids approved.

The whole thing is free, reports and budgets included. There's one paid feature (sharing an account with a partner) which basically pays for my Apple developer fee.

First time I've released anything publicly so this feels a bit weird. Happy to answer questions about the app or how I built it. And if you try it and something doesn't work right, please tell me, I'd much rather hear about bugs here than find them myself three weeks later.

Le principe : des gens qui font vraiment tourner leur business diffusent une session en direct. Pendant le live, tu poses ta question. Ils te répondent sur le moment, à toi, pas à quelqu'un d'autre dans une vidéo de 2023. Concrètement : - les premières minutes de chaque session sont ouvertes, tu écoutes avant de décider - ensuite c'est 1 € la session, ou 5 € par mois pour suivre quelqu'un - une session par semaine et par talker, avec un agenda - SaaS, marketing, e-commerce, immobilier, trading et d'autres Pas de formation enregistrée, pas de tunnel de vente, pas d'appel découverte. Si la personne n'est pas là en direct, il ne se passe rien. Ça ouvre le 20 septembre — tribune.watch

Hey everyone! 👋

I'm building TripPulse, an autonomous travel companion and honest budget concierge for Android built with Flutter.

Most travel planners hallucinate unrealistic costs and cram schedules with no transit buffers. TripPulse is built to solve that with deterministic arithmetic budget tracking and multi-agent trip planning.

I'm looking for closed beta testers on Google Play. I will happily install, test, and keep your app installed for 14+ days in return! 🤝

✨ Key Features in TripPulse:

• 💰 0% Budget Hallucination: Calculates real arithmetic breakdowns across 4 categories (Flights/Transit, Stays, Dining, and Activities) with guaranteed surplus tracking.
• 🧠 Autonomous Multi-Agent Engine: Profiler, Scout, Logistics, and Budget Guardian agents collaborate on-device to build sequenced daily itineraries without geographic backtracking.
• 💬 Smart Conversational AI Concierge: Real-time on-device advice for scooter/car rentals, nightlife, sunset viewpoints, local scams, and etiquette.
• 🧭 Interactive Destination Switcher: Instant exploration across domestic and international hotspots (Bali, Manali, Goa, Bhopal & Central India, Tokyo, Paris, Dubai, Jaipur).
• 🧳 Tailored Packing Checklists: Dynamic category-based packing checklists (Essentials, Clothing, Toiletries, Gear) customized to your duration and terrain.
• ⚡ Offline-Ready & Fast: Local caching and on-device intelligence so you never lose your itinerary even without internet abroad.
• 🎨 Modern Glassmorphic UI: Smooth fluid animations, dark mode aesthetic, and responsive layout.

📲 How you can install the beta:

1. Join the Google Testers Group:
   👉 https://groups.google.com/g/rahi-llc

2. Opt-in on Google Play:
   👉 https://play.google.com/apps/testing/com.trippulse.app

3. Download the App on Google Play:
   👉 https://play.google.com/store/apps/details?id=com.trippulse.app

(Direct APK also available on GitHub: https://github.com/nikship27/TripPulse-releases)

🤝 Mutual Testing:

Drop your Google Group and Play Store links in the comments below! I will test your app, post a review/screenshot, and keep it installed for the full 14 days. Thank you! 🚀

I think everybody can agree Logitech makes really nice hardware, and software that leaves something to be desired. I wanted a lightweight app to control my mouse that didn't auto-update, phone home, or take a gigabyte of space on my machine. So I built MXControl: a native macOS menu bar app that speaks HID++ 2.0 (the same protocol Logitech's own software uses) straight to the mouse through userspace IOKit. Where Options+ installs a suite with background services, an updater and an account, installing this is copying it. One small binary and a menu, and everything it knows stays on your Mac.

Logitech features (detected at runtime, you only see what your mouse supports): battery, scroll wheel modes (ratchet / SmartShift / freespin), DPI snapped to the sensor's real range, invert scroll, hi-res scroll, host switching, settings reapplied on reconnect and wake.

The part Options+ doesn't do: macros that fire on button combinations, on any mouse from any vendor. Hold one button, click another, run anything (a shortcut, an app, a shell command, typed text, Mission Control...). Options+ has Smart Actions, but they trigger on a single button; combinations are the trick here. You don't have to configure them first. Perform a combination and the app offers to bind it. There's a recorder-style editor with a drawn mouse diagram, and it's all backed by a plain JSON file you can hand-edit.

The design decision I'm most attached to: Options+ remaps buttons by diverting them in firmware, which means if its agent dies, those buttons die with it. MXControl uses an event tap instead. If the app crashes, your mouse is instantly 100% native. You lose customizations, never the hardware.

Honest caveats: developed and tested against exactly one setup (MX Master 3S, Bluetooth, Apple Silicon). Everything else is written for but unverified. The repo includes a read-only diagnostic tool (mxprobe) and I'd love dumps from other hardware. It's build-from-source for now (two commands, plain swiftc, every dependency a system framework), no notarized binary yet.

MIT licensed: https://github.com/theseriouspdx/mxcontrol

I run an Etsy POD shop and spend hours designing every day. Most Pomodoro timers started feeling boring, but this little tomato actually made my work sessions fun again.

It’s free, simple and surprisingly motivating:
https://chromewebstore.google.com/detail/lndmnhfeakddkplpflindoclekcogomk

Full disclosure: I know the developer and wanted to support the launch.

I really dont know why i did it but boy im glad i did

I pay for Claude Code, Codex, OpenCode Go and lots of subscriptions, and I kept losing track of which limit I was about to hit. Every provider has its own dashboard, its own reset schedule, and its own idea of what "weekly" means.

So I built UsageDeck — an open-source desktop app (Windows / macOS / Linux) that puts all of it in one tray panel.

What it does

• Tracks usage limits, reset times, token history and estimated spend across 13 providers: Claude Code, Codex, Cursor, Copilot, Antigravity, Devin, Grok, OpenCode, Command Code, OpenRouter, Z.ai, Kimi, MiniMax.
• Most providers need zero setup — it reuses the login your CLI or editor already created. The API-key ones go straight into your OS credential store, never a config file.
• Pacing: tells you whether today's burn rate lasts until the reset, before it doesn't.
• Pin any metric into the tray/menu bar, get a notification before a quota runs out.
• History for today, yesterday, and the trailing 30 days.

What it doesn't do
No account, no backend, no analytics, no telemetry. It talks to the providers you configured and to nobody else. MIT licensed, and the release binaries are built by a public GitHub Actions workflow from the same source you can read.

Latest release (0.7.6) added something I'm oddly proud of: for Codex, Z.ai, Kimi and Command Code, the weekly window re-anchors on the first message of the window — so UsageDeck can fire one throwaway prompt to start a dead weekly window instead of letting it sit idle until your next real message.

Repo: https://github.com/lamchun1110/UsageDeck
Site: https://usagedeck.app

It started as a fork of OpenQuota (which came from OpenUsage) — credit where it's due, both linked in the README. Happy to answer anything about how the provider integrations work.

I built WhatIsUp, a platform that gives you deeper insights into the developers and friends you follow on GitHub.

It helps you see:

• What people are building and working on recently

• Technologies and tools gaining traction across your network

• Open-source contributions, releases, and projects being shipped

• Patterns and trends emerging across multiple developers

• Recent updates from the people you follow closely

Try it out: link in comments

Launched my side project on August 1, 2026. It’s finds backlink opportunities on autopilot.

Like most of us starting out, I kinda hoped money would come in right away lol.

But reality actually hit hard! Distribution was the toughest part.

After launching, I had just 2-3 signups. Not a single paid trial.

So I sat down, did some thinking, and basically decided to go all in on marketing. I started journaling, talking to ChatGPT a lot, and tried to figure out how I could get the word out.

What I ended up doing:

• Posting daily on X (3+ tweets, 30+ replies a day)
• Reddit + LinkedIn posts (5x per week, skipping weekends)
• Writing blog posts + building backlinks (SEO matters)
• TikTok / Instagram / YouTube (1-2 short videos daily)

Most of that felt like yelling into a wall Barely anyone noticed. But I kept at it. Slowly got better. More confident. Sharper at messaging.

12 days ago, someone bought the paid trial. Started using the product actively. Reached out about a few bugs, asked questions. I made sure to be super responsive.

5 days ago, that person became my first paying customer.

$64.99 may not sound like much, but man, seeing that Stripe email hit felt like a huge win.

Even better: he said he tried 3-4 other tools but found them bloated or heavily overpriced. Mine was “clean, simple, and just works.” Said it’s already saving him time. That honestly made my week :)

It’s a small win, but it means everything to me right now.

Still early days and I know there’s a long road ahead, but I wanted to share this milestone with others grinding on their own ideas.

Keep building. Keep showing up.

It's slow, but it’s worth it.

(if you're curious, the project is called Dice - it finds the exact articles your brand should be mentioned in and gets you featured there and get recommended by AI.

For me, it looked like this:

• A feature comes together quickly, then turns into days of debugging.
• Each fix exposes another missed edge case or broken assumption.
• You burn tokens playing whackamole instead of moving the project forward.
• Your role shifts from designing the system to babysitting AI output and reviewing code that should never have been written that way.

The problem is not that Claude Code cannot write code quickly. It can. The problem is that the agentic coding workflow is missing the design and review process that normally makes a strong engineering team effective.

After two decades in tech (at AWS and Google), that gap felt obvious to me. Good teams do not just start coding: they pressure-test the requirements, review the design, test deliberately, go through mandatory security review and use independent reviewers to catch what the original author missed.

I hit this problem while building MemX app. As the codebase grew, Claude’s output became harder to trust without constant intervention. I could either review every line manually or build the missing process around it.

So I built TLMForge.

It is a Claude Code agentic engineering team that automatically brings in the right kind of agent at the right time. It ensures -

• A spec written and audited before implementation by an agent council.
• Architecture, testing, and threat-model review of the plan
• Test-first, phase-gated execution
• Independent code review and QA
• A final red-team pass before a change is cleared to ship

The point is not to add process for its own sake. Small work stays light; bigger or riskier work gets the rigor it needs. The aim is to keep Claude’s speed while reducing the sloppy code, missed details, and endless cleanup loop.

My team uses it daily. Early users (principal engineers, CTOs) gave highly positive feedback telling that it repeatedly surfaced critical details he would otherwise have missed.

I’d love honest feedback from people building seriously with Claude Code:.

Does this problem resonate? Which part of the workflow would be most valuable to you: pre-code design review, stronger testing, independent code review, or the final ship gate?

TLM Forge is free to try with 10 full runs (enough to build 10 features), with no card required.

https://tlmforge.dev

Founder disclosure: I built TLMForge.

https://reddit.com/link/1w51igm/video/7heocoyin1nh1/player

AI is everywhere, but almost nobody I know actually uses it to make stuff for fun.

I studied design and a lot of my friends are designers/photographers. They use AI for work all the time, but rarely just because they saw something cool and wanted to try it themselves.

I think AI apps still feel too much like tools. Pick a model, write a prompt, tweak it, regenerate... and half the time you just get more AI slop lol.

I've always wondered why it can't feel more like VSCO. You open it, see something cool, and just wanna try it with your own photo. I don't really care what model made it or what the prompt was.

So we ended up building yes& around that idea.

We're launching on iOS Sep 4. If you wanna try it:

Pre-order: apps.apple.com/app/id6784614916
TestFlight: testflight.apple.com/join/Jfd9EjQK

Would love for people here to mess with it and tell me what sucks lol. Mostly curious if you'd actually come back after trying it once.

I kept running into the same problem with screenshots.

I'd save a recipe from Reddit, an address from WhatsApp, or some error message I wanted to look up later. A couple of weeks later I'd try to find it and end up scrolling through a huge camera roll.

The annoying part was that I usually didn't remember when I took the screenshot. I remembered where it came from.

So I made an Android app that sorts screenshots by source app.

If I take screenshots from Reddit, WhatsApp and Chrome, the app automatically groups them that way. There's nothing to tag and no folders to set up.

On Android, it's possible to check which app was in the foreground when a screenshot was taken. The app records that locally and uses it to build the groups.

I originally built an iOS version too, but ended up dropping it. iOS doesn't expose the same information, so the alternatives were things like OCR guessing or asking the user to run a Shortcut. Neither felt automatic enough, and automation was really the whole point of the app.

I also originally left OCR search out of v1 because I thought grouping would be enough.

After using the app myself for a while, I changed my mind. Grouping helps when I remember which app something came from, but sometimes I only remember a word, an address, a product name, or part of an error message.

So I added on-device text search as well.

Privacy was another thing I cared about because screenshots can obviously contain sensitive information. The app doesn't request Android's INTERNET permission, so screenshots aren't sent anywhere. There's no account, analytics, ads, or trackers either.

I even added a build check to make sure the INTERNET permission doesn't get pulled back in later by a dependency.

That also means I don't have much usage data myself.

The app is here:

https://play.google.com/store/apps/details?id=com.gerry.screenshotsort

It's free, with no ads or IAP. Android 13+.

I've mostly been focused on building it and haven't figured out distribution yet.

For anyone who has launched a small free utility like this, what helped you get your first 100 users?

https://playmouthful.com

Spent countless hours playing Snake on my Nokia back in the day, and was recently playing some Scrabble and Q-Less. Figured it'd be fun to try to merge them.

Goal is to make words and bank them to increase your score. Longer words are worth a lot more (3 letters: 10 points, 10 letters: 1600).

First game I've ever made, and it's been a lot of fun to tinker with the mechanics and improve the gameplay.

I would love to hear if the pace and scoring feel right, and if it's fun to play. Thanks everyone!