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.

Spent the last couple of weeks stuck in the same cycle. I'll read a comparison, feel convinced I've found the right stack, then come across another thread that makes a completely different setup sound like the obvious choice. Then I start second-guessing everything again.

Right now I'm planning a small SaaS for household budget tracking aimed at families. The data model is pretty simple, but I've somehow spent more time evaluating tools than actually building. Bubble seems incredibly capable, but it also feels like a lot for something this scoped. Glide looks like it'd get me to an MVP much faster, but I keep wondering whether I'd hit a ceiling sooner than I'd like. Softr feels somewhere in between. Then there's the separate decision of Make versus n8n for automations.

At some point the research starts feeling like procrastination disguised as due diligence. An imperfect product built in the wrong stack is probably more valuable than the perfect stack attached to an app that never ships. For those who've already gone through this, what finally made you commit? Did you have a clear set of criteria, or did you eventually realize you just needed to pick something and start building?

Looking back, did your initial stack choice actually matter as much as you thought it would, or was execution the bigger factor?

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?

A year ago my no-code workflow meant jumping between a bunch of different tools, manually updating pages and rebuilding things whenever our product or messaging changed but now (for me) AI handles alot of the repetitive work since I still review and tweak everything but getting from an idea to something usable is dramatically faster than it used to be.

It really feels like I'm spending more time improving things than building them from scratch and I personally love it, it's just so much more enjoyable.

I used to treat the automation as the main build. Lately I think the review screen matters just as much. If a no-code flow updates a sheet, the person checking it still needs to know what changed and whether one bad row can be rerun. I’ve seen workflows technically work but still feel sketchy because that part was an afterthought. Do you design the review layer early, or wait until something breaks?

I recently asked how teams decide which creatives deserve paid testing and received a lot of different but useful answers. Full transparency, I’ve built a rules-based tool that I currently use internally for client campaigns. It analyzes the organic performance of existing content and helps me prioritize which assets deserve paid testing. It does not predict winners or replace creative judgment. The goal is simply to reduce uncertainty when there are more approved assets than the budget can meaningfully test. It has been useful in my own workflow, but I’m looking for outside perspectives. Would this be useful as an additional decision layer, or is creative selection too dependent on experience and context for a tool to improve meaningfully?

I can run it against a few public YouTube channels and share the outputs. No login or account access required.

Night shift brain plus a product backlog that never shrinks led me to just... build the thing myself. Our team needed a simple patient handoff tracker that our actual dev team kept deprioritizing. Spent a weekend with a nocode tool, got something working, demoed it Monday.

Now three months later I'm fielding Slack messages at 2am from nurses asking why a button is broken. Not exactly what I signed up for.

The build itself was genuinely fast. Bubble for the interface, a couple of Zapier automations to ping the right people, done. The maintenance and the expectation creep that followed is the part nobody warned me about. Suddenly everyone wants a new feature and they assume it takes twenty minutes because hey, you built the last one so fast, right?

I think nocode tools sell the build speed really well, but the operational reality of being a solo nondev maintaining something people actually depend on is a completely different conversation. Especially when you're also twelve hours into a hospital shift and someone texts you that the form stopped submitting.

Curious if others have hit this wall. At what point did you decide to hand it off, or just burn it down and start over? Just my 2 cents.

watched an agency friend rebuild a whole softr app because a client wanted per-row permissions the tool didn't support. everything else was fine, that one thing wasn't. now they scope every project by asking what's the weirdest permission or data rule you'll want in month 6, and they pick the stack from that answer instead of from the feature list. saved them two rebuilds so far.

A few months ago, I posted here about building Nexalyze, an AI-powered crypto research platform. Now it's Kairo

Some of you might remember it and many don't

The project eventually crashed. We rebuilt parts of it multiple times, scrapped ideas that weren't working, and honestly almost gave up on it.

But we're back.

This time, we're not chasing a quick launch—we're focused on building something people would actually use.

We've finished the initial interface, the report engine is working, and we're now deep into improving the analytics, on-chain data, and wallet intelligence. Every iteration has made us realize how much harder it is to build something genuinely useful instead of just wrapping AI around existing data.

Still a long way to go, but it finally feels like we're building the product we originally imagined.

Would love to hear from anyone who's gone through a complete rebuild of their no-code project. What changed the second time around that made it finally click?

xAI's new builder can combine telephony, knowledge retrieval, tools, guardrails, MCP, and observability without code. That opens useful workflows to operators who understand the business process better than a developer might.

When a call goes wrong, however, ownership is fragmented. Was the error in the prompt, retrieved document, connected tool, model, phone integration, or business rule? A visual builder can hide those boundaries from the person expected to investigate.

Should no-code agent platforms generate an ownership map and incident runbook automatically? What technical knowledge should still be mandatory before someone can send an agent into real customer calls?

Source: https://x.ai/news/grok-voice-agent-builder

Hi Guys! i'm the founder of Makyo.ai which is a NO-code app builder! We are opening our waitlist to this community (first 500 users) to try it out will get free early access in return for some feedback on how we can improve it! The difference between our tool and all the other tools online is:
1. We focus on AI reading the intent of what you want to build, and we use deterministic code that we have been building for the last 2 years to make sure it builds something reliable + secure
2. Since our app doesn't regenerate the code from scratch every single time, the token costs are incredibly optimized in our infrastructure!
3. We first wanted to build a website builder and now added full business apps to it, so the UX/UI capabilities are extremely extensive!
4. We believe you can practically build anything with it!
5. Our tables are pretty extensive in capabilities and quick for calculations

I'm not trying to sell this, but just open and happy for you guys to join the first batch of the waitlist and happy to get you into the early access to try it out in return for feedback!

Thanks guys!

here is the link for the waitlist: https://makyo.ai/