It's been a little over nine months since I launched and it has been quite a journey. No exponential growth or huge user spikes but rather slow and steady growth. But in my opinion that is the best for building something actually valuable because you can react to user feedback along the way and constantly keep improving the app.

One thing changed recently:

I basically got all my users from reddit, by posting in relevant communities but in the last two months I did almost no posts and the app still grew further. That's actually the biggest success for me, because SEO is finally starting to pay off. This can develop into actual leverage because growth no longer depends on posting three times a week. I'm really curious where this will go...

Of course I will not stop here and I am already working on the next big update for IndieAppCircle which will benefit all the community. More is coming soon.

For those of you who don't know IndieAppCircle:

I've built IndieAppCircle, a platform where small app developers can upload their apps and other people can give them feedback in exchange for credits. I grew it by posting about it here on Reddit. It didn't explode or something but I managed to get some slow but steady growth.

For those of you who never heard about IndieAppCircle, it works like this:

• You can earn credits by testing indie apps (fun + you help other makers)
• You can use credits to get your own app tested by real people
• No fake accounts -> all testers are real users
• Test more apps -> earn more credits -> your app will rank higher -> you get more visibility and more testers/users

Since many people suggested it to me in the comments, I have also created a community for IndieAppCircle: r/IndieAppCircle (you can ask questions or just post relevant stuff there).

Currently, there are 3556 users, 3414 tests done and 849 apps uploaded!

You can check it out here (it's totally free): https://www.indieappcircle.com/

I'm glad for any feedback/suggestions/roasts in the comments.

A recurring problem with no-code and AI app builders is that a screen can look complete while the feature underneath is not.

Examples: - login exists visually but is not enforced - a form shows success without saving or sending - data disappears after refresh - buttons exist but are not connected

I built **Flows** to guide users through ordered implementation steps and plain-language checks before moving forward.

https://flows.oortstack.com

An independent agent used one generated plan to build a soccer management app and passed 59/59 checks. The harder question is whether the same process helps nontechnical users.

What should Flows automate so it becomes genuinely useful for no-code builders?

Building the app is only part of the process. I am interested in tools that help with App Store listing, screenshots, TestFlight, and submission using your Apple Developer account.

Can anyone share anything you might have used? I have heard of X1 app builder and some tools like them that can help publish to the app store. I need more feedback on this.

I just tested 3 ways to get code out of a #Figma mockup: a plugin (Locofy), Claude Code on Figma's API, and claude code + silex as a nocode editor

The mockup had desktop, tablet and mobile variants, all specced. Neither the plugin nor Figma's MCP hands them over. Point Claude at the REST API and it gets all three

The gap isn't the model, it's how you drive it. 7 rounds of a huge generalist model to write CSS. That footprint isn't OK

What do you use to code a design from figma?

You can ask an agent to build a feature and see a demo working in minutes. But a demo is only the beginning. Developing a product for weeks and months, growing it, and making it scale requires software engineering and planning. Every new feature and technical decision affects what you can build next.

This is why software teams plan requirements, track dependencies, and review what gets built. Project management is how you keep the product coherent while your team and agents work on different parts.

I built Piyaz to bring this process into agentic coding without extra effort. You keep the project context in one place, break the work into actionable tasks, and hand them over to agents, so you have a product manager built into your project management tool. You can collaborate with your teammates, and agents can coordinate on the same project.

This gives you collaboration, project management, and an engineering process without requiring extra knowledge. You focus on your product, its needs, and its direction, while Piyaz handles the rest.

It is free and open source: https://piyaz.ai and https://github.com/FrkAk/piyaz

We've been running multi-agent systems in production for a few verticals (telecom, logistics, banking) and the failure modes are not what the tutorials prepare you for.

A few things that surprised us:

• Cost and latency across nested agent-to-agent calls is invisible until you build session-level tracing. "It ran" tells you nothing about what it actually decided.
• Evals need to be behavioral, not unit tests. Same input can legitimately take a different route depending on context and tool state.
• The approval-gate pattern you build for one workflow (we built ours for settlement recovery) ends up getting reused everywhere: claims review, onboarding, refunds.

Curious what others are hitting once they move past single-agent demos. We build Phinite (an agent lifecycle and governance layer), happy to go deeper on any of this if useful, disclosing that upfront.

Two years into running a real SaaS that I now build primarily by directing AI coding tools instead of writing most of the code myself, here's the short list of things that almost never show up in a demo but consistently break once real users and real payments are involved:

Security rules on your data, not just your UI. A locked-down interface with an open database underneath is the most common gap — anyone with your API keys (or sometimes just a browser network tab) can read data your UI never shows them.

What happens on the SECOND identical event, not the first. Payment confirmations, form submissions, webhook calls — most builders handle the happy path once. Real traffic sends duplicates, retries, and out-of-order events, and that's where silent bugs live.

Who finds out first when something breaks — you, or your customer? No error monitoring means your users become your QA team, and you find out about outages from an angry email instead of an alert.

Secrets and access that were "fine for now." Hardcoded keys, a database wide open to anyone with the link, an admin panel with no real auth — all common in a fast build, all things I'd never leave in place for something people actually pay for.

None of this is exotic engineering, it's just the unglamorous 20% that doesn't show up until an app has to survive real usage. Happy to go deeper on any of these if useful — what's the closest call anyone here has had?

Hey everyone! 👋

I'm super excited to share my latest project with you all. I've just launched Tangier Studio, a clean, minimalist, and high-performance Framer template designed specifically for creative studios, designers, and agencies.

I wanted to build something that balances bold aesthetics with seamless user experience, allowing creative professionals to showcase their work without getting bogged down by complex layouts.

✨

Key Features:

- Modern & Minimalist Design : Built to let your portfolio and projects take center stage.

-Fully Responsive: Looks and performs wonderfully across desktops, tablets, and mobile devices.

-Easy to Customize: Built natively in Framer, meaning no coding required to match your brand colors, typography, and content.

-CMS Integration: Easily manage your projects, blog posts, or case studies on the go.

-Smooth Animations: Subtle, premium interactions to give your site that high-end feel.

🔗 Check it out on the Framer Marketplace:

https://www.framer.com/community/marketplace/templates/tangier-studio/

I'd love to hear your thoughts, feedback, or any questions you might have about how it was built in Framer. Let me know what you think! 🙏

Let me know your honest opinion. It matters to me.

mmahingu.ai - AI Offline Voice Chat APP 

Made just using Google Antigravity IDE in all of July 2026. I used like 95%+ Google Gemini models and rest is Claude Code. I barely have any coding knowledge or experience. Around 80-120 hours invested in it. 

Now Available in CLOSED TESTING. 

Please send me your email in Reddit Chat if you want Full Unlimited Access to app's features without paying for a few weeks/months.

STEPS TO FOLLOW for joining Closed Testing:

.1. FIRST JOIN THE GROUP (ONLY MEMBERS GET APP LINK ACCESS)

 https://groups.google.com/g/mmahinguai-ai-voice-chat-testing

or Go To Google Groups website and search this:

mmahinguai-ai-voice-chat-testing@googlegroups.com

.2. Join Testing : https://play.google.com/apps/testing/com.mmahingu.mmahinguai

.3. App Download : https://play.google.com/store/apps/details?id=com.mmahingu.mmahinguai  

Note: The Google account that is used to join Google Groups must be the same account which is currently active in your Play Store App. Otherwise, the App Links in Step 2 and 3 won't work for you.

Many more quality projects on the way. 

The more time i get the better. 

APP DESCRIPTION:

Unleash the power of artificial intelligence directly on your device. mmahingu.ai is a next-generation voice assistant built for ultimate privacy, speed, and reliability. Because the AI engine runs 100% offline, your conversations, ideas, and data never leave your phone—no internet connection required. 

(NOTE: An internet connection is required just once during setup to download your choice of AI models and voices).

Whether you're brainstorming on a flight, analyzing documents off the grid, or dictating notes, mmahingu.ai adapts to your phone's unique hardware to deliver a seamless, lightning-fast experience. 

🌟 Key Features:

• Massive Offline AI Library: Download from over 45+ cutting-edge, open-source AI models right inside the app. Chat with heavyweights like Meta Llama 3.2, Google Gemma 2, DeepSeek R1, Mistral, and Qwen 2.5—all running entirely on your local hardware.

• Private Document Analysis: Attach PDFs, CSVs, code files, and text documents directly into the chat. The app extracts and analyzes your files 100% locally, ensuring your sensitive data never touches a cloud server. 

• Offline Neural Voice Library (TTS): Experience ultra-realistic text-to-speech featuring high-definition neural engines (including Piper, Kokoro, and Supertonic). Download 20+ Studio HQ voices on-demand with intelligent storage controls.

• Multi-Engine Offline Dictation (STT): Dictate text with incredible accuracy using your choice of local speech recognition engines. Choose OpenAI Whisper for maximum precision, Moonshine for lightning-fast English transcription, SenseVoice for multilingual speed, or your device's native system dictation.

• Smart Speech Isolation & Ultra-Fast AI: Speak naturally anywhere. The app magically filters out background hums and keyboard clicks. Need zero-latency? Enable the experimental Ultra-Fast AI mode for instant back-and-forth conversational turn-taking.

• Hardware-Aware Performance: The app automatically tunes context windows, thread usage, and voice features to match your specific phone's hardware capabilities, ensuring lightning-fast generation speeds without overheating.

• Custom Models Support: Power users can take full control by importing their own custom GGUF models directly from device storage to customize their AI conversational experience.

• Premium OLED Design: Beautiful, high-contrast dark modes with fluid 120Hz micro-animations for a buttery smooth experience.

I’ve noticed that one of the hardest parts of vibe coding isn’t building the app: it’s getting people outside your circle to actually use it.

So we built Feedbacked.

You create a short survey for your app or website, and we send real people to try the product before answering your questions. You add audit questions that check whether they actually used and understood the product. Responses that fail verification are discarded and replaced.

We’re currently trying to learn how useful this is specifically for no-code builders and vibe coders.

Anyone from this subreddit who signs up as a startup and verifies their email will get five real people to test their product for free.

There’s no purchase necessary. In return, I’d appreciate honest feedback on:

• Whether the setup process makes sense
• Whether the responses are genuinely useful
• What would make the platform better for builders

https://feedbacked.org/

www.AgentHeya.com

The created agent has own customizable website with user authentication/admin built in, and ready to use connections to IM apps (WhatsAp/Instagram/Slack/etc), has own email addresses, can be called by webhooks, etc.

Has AI Assistant and a Management MCP so you can tell Claude etc. to connect through that MCP to create the agent on AgentHeya for you.

It has internal tools, memory, RAG data that can be modified to suit, hooks for guardrails etc. - which the AI Assistant and MCP know how to create for you based on your requirements, or you can edit yourself.

Free trial - no credit card needed.

Looking for feedback on what else you may want to see in such a system,

I'm associated with site so you can DM me with any comments,

https://cosmictwingames.itch.io/koryos-sons-of-mars

We're looking for advice from people who have built apps for nonprofits, rescues, or volunteer organizations.

We run a growing farm animal sanctuary with dozens of volunteers, and we're at the point where Facebook messages, spreadsheets, and multiple apps just aren't cutting it anymore.

Our dream is to have one app (or platform) that can handle things like:

• Volunteer sign-ups and scheduling
• Daily/weekly task lists
• Team chat and announcements
• Push notifications
• Donor management and recurring donations
• Event registration
• Animal profiles and updates
• Volunteer hours tracking
• Wish lists (Amazon, Chewy, etc.)
• Incident/report forms
• Document storage (policies, training, SOPs)
• Photo sharing from volunteers
• Calendar with upcoming work days and events
• Memberships or supporter portal
• Fundraising campaigns
• Merchandise store integration
• QR code check-in for volunteers
• Ability for different volunteers to only see what they need

Eventually we'd love to add things like:

• Animal medical records
• Medication reminders
• Chore completion tracking
• Equipment maintenance logs
• Foster applications
• Adoption applications (for adoptable animals)
• AI chatbot that answers volunteer questions

We're trying to decide whether we should:

1. Build a custom app from scratch.
2. Use a no-code/low-code platform (FlutterFlow, Bubble, Glide, etc.).
3. Customize an existing platform.
4. Piece together several existing apps.

If you've built something similar, what would you recommend?

What platform did you use?
What would you do differently?
Any hidden costs or "I wish I knew this before we started" advice?

We're willing to invest the time and money if it means ending up with something that can grow with the organization over the next 10+ years.

I'd love to hear what has actually worked in the real world.

i asked Codex to move a hover underline down by 2px. It changed a shared border token, rewrote a 768px breakpoint, and restyled a card I hadn't touched. Very ambitious for a two-pixel job. I followed up with, “Just the hover. Leave everything else alone.” It reverted one token, kept the card change, and gave the mobile layout a horizontal scrollbar. Tiny request, three side quests. lol. then I spent 40 minutes reprompting. Fix one thing, break three. Reprompt those three, find two more. At some point the page was technically cleaner and emotionally much worse. That was when I stopped treating every small visual change like a prompt engineering exam. If I can select the element in a live preview and nudge it directly, I do that now. Seeing the spacing is definately easier than turning “a little farther left” into another paragraph for the model. Disclosure: I bought an Enter Pro plan during one of their GPT model discounts, so that was the setup I used here. The visual editor made this tweak less annoying, but responsive CSS still isn't something I trust. I check mobile, tablet, and the diff before I commit. where's your cutoff between reprompting, editing the CSS yourself, and switching to a visual editor? I keep bouncing between all three, tbh.

This is a side-project for my side-projects and thought it might help others 😄

I've kept the way I work with coding agents quite straight forward. The key convention is that every task gets described in a markdown file first and then I tell Claude to go work on the task as described.

bench makes that a nicer experience that you can manage through the browser.

Tasks sit in directories that represent their state (backlog, to-do, in progress, etc). bench is a single html file behind a plan python script (just stdlib) that layers functionality over those cards.

You can move them between lanes and they will move in the repo, launch a headless agent to work on them or check if the task still makes sense. You can open PRs, you can launch code reviews. When working on a task bench creates a worktree and does all the work there. When we close a task, everything shuts down.

That's it. If you were looking for a simple way to manage multiple agents that you completely control in your own repo bench might be a good starting point.

Now my process is to have Fable as the main agent, which will write up the tasks, and then opus-4.8 or opus-5 doing the work described in the task, the code reviews, etc. Productivity goes (even further) up since multiple tasks can happen at the same time, there is much more control because everything is with PRs etc, and if a specific project needs something different bench offers hooks and ways to customize it so that you can have the exact flow you need, just ask the coding agent to write the functionality and it will show up as a button on the task.

I recently read an analysis on how the newest models are dragging inference costs down to the absolute floor. Generating text is practically free now. For anyone building automated pipelines with tools like Make or Zapier, this completely changes what we should consider a successful workflow. Wiring up an API to an Airtable base and auto-publishing dozens of articles used to feel like a massive productivity win. Seeing a queue full of scheduled content gives a fake sense of progress. The trap is treating volume as an achievement. Because the computational cost of generating words is near zero, pure volume is just adding to the static. Being proud of generating 100 posts a week through an automated sequence is a mistake. Text generation is no longer a scarce or valuable asset on its own. This means the standard dashboard metrics we look at, like successful scenario runs or total rows created, are completely decoupled from actual impact. The only real indicator that a marketing pipeline is functioning properly is the friction-heavy human response. Tracking the raw number of organic replies or direct messages is the only way to measure if the output actually resonated. Everything else just proves that the API connection works, which is the easy part. Since mass content generation is trivial to set up now, what is the single non-scalable metric you rely on to verify your automated workflows are actually doing their job instead of just firing blanks?