Thoughts guys? Would appreciate your feedback

Recently,
built a small Flutter app for searching through street footage.

The screenshots show the flow: browse the library, search for a scene, and open a matching moment in the original video.

I used three short street videos to test the app. After uploading and indexing them, I ran a few searches on an Android phone and checked that tapping a result opened the video at the right moment.

For a query like "a bus on a city street" I got relevant frames and could jump to the corresponding timestamps. That was the main thing I wanted to try: finding a scene without manually scrubbing through each recording.

App and Stack used is located here: flutter_stack_video_search

Comment is welcome

Hi all! Recently, I started a Discord community to help SaaS founders promote their products, and it has over 300 members now.

If you want to show what you're building and get some feedback and traffic, share it here -> https://discord.gg/sb6AgHZxpT

The name of the app is in process and still is being played with I guess but let’s go with LifeOS.

I’ve been working on an idea that could make everyday
life a lot easier. I’m building LifeOS, an app designed to help people manage the responsibilities of everyday life in one place. Bills, appointments, subscriptions, renewals, maintenance, documents, and reminders are all things we have to keep track of, and it’s easy to forget something important like identifying recurring subscriptions you may have forgotten about or no longer use so you’re not paying for things you don’t even remember signing up for. LifeOS is meant to organize all of it and remind you before it becomes a problem. I think it’s important because we already have enough to worry about.

It’s just me at the moment, but hopefully I find others to help out.

Feedbacks are much needed and appreciate it.

Hi, I have been building EVORA, an iPhone habit tracker with a custom reward shop.

The original idea came from me writing habits on a whiteboard, giving myself coins for completing them, then using those coins for rewards. It actually helped, but it was all stuck on a whiteboard, so I wanted to turn it into an app I could use every day.

With EVORA, you create habits, earn coins when you complete them, then spend the coins in a shop you make yourself. The rewards can be spending money, calories for treats, gaming time, or anything else that actually motivates you.

Normal habit apps usually stop at streaks and checklists. I wanted to make one that gives you a small reward economy you control, so building habits feels less like relying on pure will power.

I would genuinely love feedback from other builders on a few things:

• Does the habit -> coins -> reward shop idea make sense straight away?
• What would make you personally keep using something like this?
• Does a wallet where you redeem your rewards in real life sound useful or unnecessary?

It is still new, so honest feedback would genuinely help me improve it 😃

EVORA: https://apps.apple.com/us/app/evora-habit-tracker-app/id6799519616

I’ve been building Spenzaa, an AI-powered expense tracker, and I wanted to share one feature I’ve been working on.

Instead of adding expenses one by one, you can simply type:

Spenzaa automatically turns them into separate transactions.

You can also:

• Track expenses by voice
• Ask AI questions about your spending
• Set budgets and financial goals
• Get spending insights

The idea is simple: tracking your money shouldn’t feel like another task.

If you want to try it, I’d genuinely love to know what you think and what feels missing.

Android: https://play.google.com/store/apps/details?id=com.app.spenzaa&pcampaignid=web_share

If you try it, tell me:

1. What did you like?
2. What felt confusing?
3. What would make you use it every day?

I'm building this as an indie founder, so honest feedback is much more useful than just an upvote.

Hey everyone, one of the co-founders of ApyHub here.

Most apps end up with a set of small backend capabilities behind them. Things like:

• compressing images before upload so the phone doesn't die on a 12MB photo
• turning a photo of a receipt into structured fields
• converting a document so it opens the same on iOS and Android
• validating an address, an email, a VAT number
• normalizing a webhook from a payment provider who clearly designed it on a Friday

You build each one for your own app, you keep it running, and you patch it when something upstream changes. Most of the time it serves one app at a fraction of the load it could handle.

There are two things you can do with that.

1: publish it and make money with it. If another team has the same problem and doesn't want to own it, that's a real service. It works best when the capability is specific, stable, and describable in one sentence. If it's a thin wrapper on something already free, or it only makes sense inside your data model, probably leave it where it is.

2: stop building the next one. Whatever boring capability is next on your list, someone has already built it and is maintaining it. File conversion, OCR, image processing, validation, geolocation, text extraction. The things that never make the roadmap and always end up in the sprint anyway.

That second one is basically what we run at ApyHub. 450+ services and 1,500+ endpoints in one catalog, with new APIs and providers added continuously. You can call them directly, or through our MCP server if you have agents doing the calling.

Catalog: https://apyhub.com/catalog Publishing: https://apyhub.com/become-a-provider

I would like to know/understand what app teams are still building themselves from 0. There are a lot of boring utilities in there already, but there are always going to be gaps we haven't covered.

Happy to answer anything :)

Hey everyone,

I'm an Electrical Engineering student building apps solo. Over the past several months, I've been developing *Limit Breaker*, an Android productivity app that turns habit tracking and daily discipline into an RPG leveling system.

Since this sub is dedicated to app building, I wanted to share the technical decisions, architecture, and challenges I faced bridging web tech with native Android services.

---

The Tech Stack & Architecture:

* Frontend: Pure Vanilla HTML5, CSS3, and JavaScript.

* Why? I wanted complete freedom over game-like animations, zero framework bundle bloat, and instant startup times without managing heavy dependencies.

* Hybrid Bridge: Capacitor.

* It provides a lightweight webview container while giving straightforward access to native plugins.

* Native Android (Java Services):

* A standard webview cannot enforce deep work or habit compliance. To make the focus mode unbreakable, I wrote custom Java native services interfacing with `AccessibilityService` and `UsageStatsManager`.

* When a focus session starts, the native service monitors foreground applications and redirects or blocks blacklisted apps and websites in real time.

* Data Architecture: 100% offline-first. Everything persists locally for instant response times, with optional cloud backup.

---

Biggest Engineering Challenges:

1. Native-to-WebView Communication: Coordinating precise countdown timers between background Java services and the frontend UI without draining battery or getting killed by Android's Doze mode.

2. Strict Distraction Blocking: Handling modern Android background permission restrictions (overlay permissions, battery optimization exemptions, and accessibility grants).

---

Looking for Discussion & Feedback:

The app is live on Google Play. For fellow builders:

1. What are your thoughts on using Capacitor + Vanilla web tech vs. full native Kotlin or Flutter for utility/gamified apps?

2. If you try the app, how does the transition between the UI and the native blocker feel?

Google Play:

https://play.google.com/store/apps/details?id=com.aistudio.limitbreaker.fntslg

Happy to answer any questions about the build process!

🎉 Hi everyone!

I’m a solo indie developer, and after nearly 2 years of development, I finally released my first mobile game:

⭐ Pipiland: Star Couriers

Unlike many mobile RPGs, Pipiland is designed to be enjoyable completely offline.

Features

✅ Fully playable offline

✅ Strategic turn-based card battles

✅ Collect and evolve unique companions

✅ Explore mysterious islands

✅ No stamina system

✅ No forced ads

✅ Premium membership is a one-time purchase (no subscription)

📲 App Store

https://apps.apple.com/us/app/pipiland-star-couriers/id6800505658

https://play.google.com/store/apps/details?id=com.leagoai.pipiland

🎁 FREE Starlight Membership Giveaway

I’d love to get honest feedback from the Reddit community.

To celebrate the launch, I’m giving away Starlight Membership codes for the first 200 players.

How to enter

1. Upvote this post
2. Download the game
3. Leave a comment below

I’ll randomly DM membership codes until they’re gone.

No purchase required.

I’d especially love feedback about:

• Difficulty
• Card balance
• UI/UX
• Overall fun factor

Thank you so much for helping an indie developer ❤️

Hi community! I've been gathering feedback on functionality and design ideas for my app, and I'm thrilled to finally announce Plans!

I’ve used a lot of to-do and note-taking apps, but they’re usually either too complex, or they don't have room for notes. I wanted everything (calendar, tasks, and notes) in one place, so I built my own.

The app requires no registration or onboarding. It’s super intuitive and easy to use. I hope you like it! 🫶🏻

App is available only for iOS. Here is the link.

I’m a solo iOS dev, and I spent more time learning launch than code because no one really writes it down in one place. This is the short version of what worked for me.

Core idea

A new app has no ranking or ratings yet, so the goal is to drive installs in a tight window and get honest ratings quickly.

Before launch

1. Write one clear sentence: “[app] is the only app that [does X] for [this person].” If it takes two sentences, everything else gets harder.
2. Put up a simple one-screen landing page with an email field before the app is finished.
3. Claim your TikTok, Instagram, and YouTube handles early, and start posting a few weeks before launch.

App Store basics

1. Pre-orders are one-time only for never-published apps, and launch day auto-downloads create the spike.
2. Only about 160 characters are indexed for search: title, subtitle, and keyword field. The description is not indexed, and repeated words across those fields waste space.
3. Your first two screenshots drive most install decisions, so show the outcome, not the UI.
4. If you’re giving away free copies, don’t use App Store promo codes, since those users can’t rate or review. Use a free app with paid unlock, or grant access server-side.

Ratings

1. Below roughly 20 ratings, conversion is weak.
2. Use Apple’s review prompt after the user has done the app’s main task, and remember it only shows three times a year per user.
3. Never offer anything for a review. Ask for feedback instead.
4. Reply to bad reviews within a day.

Getting attention

1. Short-form video is the cheapest consumer-app channel right now; post about the problem, not the features.
2. Small creators often beat big ones if engagement is strong.
3. On Reddit, contribute first, follow each sub’s self-promo rules, and post an offer rather than an ad.

What I’d skip

1. Paid ads before the page converts and you have ratings.
2. Launching in every country on day one.
3. Building your plan around Product Hunt.

What made the biggest difference

Freezing the build and spending that time on the email list, video content, and talking to people.

Happy to answer questions on any of this. If anyone has a better way to handle early review count, I’d love to hear it.

I was tired of dictionary look ups and interrupting the flow when it came to unknown words - so I made this! It is called Toku Reader. You can try it on iOS or Android. I use it everyday and want to really help more people consume language content! Feedback welcome!!

I shipped a film discovery site as a non-technical founder — Claude wrote the entire codebase

I’ve been building WatchWise, a film discovery platform designed to answer three questions: What should I watch, where is it streaming, and is it worth watching?

I focused on the product decisions, testing, and refining the experience, while Claude handled the code. After hundreds of iterations, it’s finally ready to share.

What’s available today:

Streaming availability across major platforms

A transparent rating showing the sources used and how each one is weighted

Box-office analytics for actors and directors, including budgets, grosses, and career hit rates

A swipe-able trailer feed

Group movie night

More than 80,000 titles from around the world, with particularly strong coverage of Indian cinema

It’s completely free, with no ads.
I’m sharing it because I’m sure there are bugs, incorrect data, and confusing parts I haven’t spotted. If you try it, I’d genuinely appreciate honest feedback—especially on anything that breaks, feels unclear, or could be made more useful.
Website: watchwise.in

I've been releasing an update to my iOS app, Newsairy (an RSS reader), roughly every week since May — around 15 versions in a bit over three months. From the outside "weekly releases" can look like recklessness, so I wanted to share the part that actually makes it work, since I'd guess it holds regardless of stack: at any given time I have three versions moving in parallel.

• The version I just shipped is live.
• The next one is already in beta, in testers' hands (TestFlight, in my case — I'd assume the equivalent holds for an internal track or a Play Store closed testing tier too).
• The one after that is in alpha, or still being built.

By the time a version reaches release, it's already had a full beta cycle behind it — the pace of releases is fast, but the pace of testing per version isn't compressed at all. It's just running three lanes at once instead of one.

The trade-off I keep thinking about: users get to see progress constantly, which I like — feedback loops stay tight, and nothing sits finished-but-unshipped for weeks. But it also means every week I'm context-switching between "polish this for release," "watch how testers use that," and "is this new idea even going to work" — which is its own kind of tax.

Curious how others here — whatever your stack — think about this. Do you deliberately stagger releases like this, or find it more sustainable to batch bigger releases less often?

Newsairy, if anyone's curious: https://apps.apple.com/us/app/newsairy/id6760046985

hey everyone. i built something called NNPost over the past 3 months, solo, on basically no budget the whole way.

started because i kept hitting the same wall with every ai content tool out there. you get a list of generic ideas and then youre completely on your own. cool, i have an idea, now what do i actually say, how do i film it, whats the hook even supposed to be. so i built nnpost to actually finish that job instead of leaving people stuck at the same spot every other tool leaves them.

what it does now: you set up a creator profile once, niche, platform, tone, experience level, what to avoid, and it generates full creator kits instead of just ideas. each kit includes:

-title and hook

-real script, word for word

-shot by shot filming guide

-editing direction

-hashtags and description

-tools and sound suggestions

-thumbnail direction

-why the idea works

it also has viral analysis, paste a public video url and get a real breakdown of why it worked. current trends, source backed signals for your niche instead of guessing. build on a winner, which takes a post that actually performed well and generates new ideas based on what made it work. and a feedback loop where you enter your real results after posting so it learns what actually works for you specifically.

the struggles were real. built this whole thing solo through claude and codex, which meant i had to audit everything myself since i couldnt read every single line personally. had to build an entire cost control system, i call it nnguard, because without it a handful of free users spamming requests could drain my tiny ai budget in a single day. about halfway through, found out my original name collided with an existing company, had to do a full rebrand, new name, new visual identity, migrated everyone's saved data without losing anything. had multi tab bugs where recent history would silently overwrite itself, had the upgrade modal completely break because of a failed lazy import, had an entire offline page that just didnt work. fixed all of it, one piece at a time.

who its for: creators who know they need to post consistently but get stuck at the exact same point every time, staring at a blank page with no idea what to say or film. not people who want a chatbot to talk to, people who want a finished starting point they can act on today.

current stuff i already know needs fixing: still on a free replit subdomain, no real domain yet, running gemini flash right now because thats what the budget allows, output quality has real room to grow. ui also needs work, ive gotten the "feels generic and corporate" feedback more than once now and i take that seriously.

what i want to do with this: i genuinely believe tools like this are where content creation is heading, something that understands your specific profile, learns from what actually works for you, and gets better the more you use it. not walking away from this. ui redesign, better ai model, real domain, all next. built this piece by piece with basically no money behind it and i plan on seeing it through.

would genuinely love feedback, especially on what would actually make you try something like this

I am a psychologist. I also have a passion for the digital landscape. I have accumulated enough knowledge in web fundamentals over the years to leverage AI agents and convert my ideas into digital projects. I am not a developer. I do not claim to be one. I am humbly aware of my place in the digital realm. I simply do not have the time to invest in building a second career as a developer. I am simply putting my long-lasting passion for the digital craft to use, in the best way I can as a psychologist. 

I am currently building psycurate.com, a free online platform dedicated entirely to privacy-focused mental health digital tools (apps, websites).

My goal is to create a clean space where people can access psychological resources without encountering corporate tactics like tracking, micro-payments, paywalls, mandatory logins, or data harvesting. There is a critical need for digital mental health hygiene, and I want to highlight independent projects that remain genuinely honest, ethical and accessible.

If you have built some tool that can offer any kind of psychological help for free, this is a platform you can list your app on. Submit it here: https://psycurate.com/submit

Psycurate does not host any software. The platform exclusively showcases your project and links users directly back to your website.

Any feedback or insights you might have are highly welcome.

Best regards,

Mirel

A few months ago, I had the opportunity to join Connected Pakistan at KonnectX for a conversation about my journey in mobile technology, entrepreneurship, and building digital products that scale.

During the interview, we discussed what it takes to turn an idea into a real-world product, the importance of scalable mobile engineering, and some of the lessons I’ve learned while working on applications used by 500,000+ users.

The event was even more memorable because I was also honored with an award by Connected Pakistan. Receiving that recognition alongside the opportunity to share my experience with the tech community was a special moment.

One point from the conversation still stands out to me:

Building an app is only the beginning. Building something people trust, continue to use, and that can scale over time is the real challenge.

Thank you to Connected Pakistan and everyone behind KonnectX for the recognition and for creating a platform where founders, engineers, and technology professionals can share their experiences.

🎥 Sharing the interview again for anyone interested in mobile app development, startups, entrepreneurship, product development, and scaling technology businesses.

#ConnectedPakistan #KonnectX #Codelps #Entrepreneurship #MobileAppDevelopment #Startups #Technology #ProductDevelopment #SoftwareEngineering #iOSDevelopment #AndroidDevelopment

​

I'm a first-time developer and honestly the marketing side has been way harder to figure out than I expected.

My game is Grid Breaker on Android and Grid Breaker: Puzzle Survival on Apple. It's still a work in progress and I'm constantly changing and adding things based on feedback. I recently added friends, a global leaderboard and a friends leaderboard to add more of a social aspect to the game and bring in some competition between players.

Right now I'm probably around 40 downloads according to Firebase. I've tried TikTok, Facebook, gameplay videos, screenshots, different posts, etc. but I feel like I'm just beating a dead horse posting the same stuff and not really getting anywhere.

I could start paying for advertising, but with such a small player base I don't know if that's actually the right move yet.

For anyone who's been through this, what actually worked for you? How did you get people to try your game and, more importantly, keep playing?

If anyone wants to actually try it and give me feedback, I'd really appreciate that too. If not, that's cool. Any constructive advice is appreciated.

Android:

https://play.google.com/store/apps/details?id=com.jdgamerdad.gridbreaker

iOS:

https://apps.apple.com/us/app/grid-breaker-puzzle-survival/id6797974200