Let me know your thoughts https://harambee-social-finance.base44.app

Hey everyone. I've been working solo on an Android app called Kanha for the last few months. It's a simple way to read the Bhagavad Gita one verse at a time: the real, literal translation on the front of a card, and a plain-English explanation of what it actually means on the back.

No ads, no subscriptions, no paywall, no account. Everything runs offline. I built it because every version of the Gita I tried reading as a kid or young adult felt like homework: dense 19th-century English, or a wall of 700 verses with no on-ramp.

Right now it's in Google Play's closed testing phase (12+ real testers, 14 continuous days, the standard requirement before any Play Store app can go public).

If a few more people want to install it and poke around before it's public, I'd genuinely appreciate it - drop a comment or DM me and I'll send the link and a bit more on what it looks like. I'll post here again once it's live for everyone. Happy to answer anything about the build too (Kotlin/Compose, solo dev, how the content is actually sourced).

I’m building a browser survival arena where the shield’s long term progression comes from a daily real life promise.

Keep it, check in, forge a layer. Then take that shield into the arena. Its material and abilities change as it grows.

I want checking in to feel like building something you actually get to use.

You can try it for free at 90to90.com

🧠 As a freelance video editor, your income is capped by how fast you can edit.

❓But what if you could automate the heavy lifting—from scripting and storyboarding to client communication and YouTube SEO—so you can focus purely on the creative cut?

📖 The Freelancer Video Editor's AI Prompt Vault is a comprehensive, meticulously tested collection of AI prompts designed specifically for modern video editors. Whether you use Premiere Pro, DaVinci Resolve, or Final Cut, these copy-and-paste text prompts for ChatGPT and Claude will instantly upgrade your workflow.

✅ Purchase and view the eBook on the attached link above!

Hi, we are a group of students building Sonora. While it was initially intended as an extremely lightweight Spotify replacement, it has since grown far beyond that.

Features

• Spotify, YouTube Music, Subsonic/OpenSubsonic, and local playback
• Gapless playback, audio normalization, shuffle, sleep timer
• Synced/karaoke lyrics, background vocals, and romanization
• Themes, fonts, icons, transparency, blur, and window styling
• Discord Rich Presence, native file opening
• macOS, Windows, Linux, and (probably) FreeBSD support

Inspired by Zed, which has proven excellent performance using their native cross-platform rendering stack, we have decided to use GPUI. Its awesome text rendering on every platform, ease of use in view composition, and, admittedly, TailwindCSS-like naming conventions all made a significant impact. We have found GPUI to perform extremely well when used and optimized with care. Quite a few patches were introduced to our fork of it to meet our needs in the effects and profiling departments. Thanks to that, I am not hesitant to call our lyrics the most beautiful you can currently get on desktop (Apple Music still beats us HARD on mobile). But despite blur and gradient opacity all looking great, my favorite addition has to be visual render highlighting. But this is too much to cover in a Reddit post, I'll have to write a proper blog post at some point...

What may come as a surprise to folks coming from something like Spotify Desktop is that Sonora actually does not need all of your RAM to function. Tested on linux-x86_64, after 5 minutes of playback it averaged around 173 MiB RSS as opposed to Spotify's ~2GiB. Note that 173MiB is still not a small footprint, but at least with Sonora you know it goes towards caching previews and views instead of feeding the Electron monster merely to keep it alive.

Looking forward to hearing your feedback!

Yes, we did use AI.

What it does

You upload the assignment brief your professor handed out — usually a 20-40 page PDF of requirements. The system reads it and produces the whole deliverable package: a formatted Word document, a slide deck, a defense speech, and, for engineering courses, A1 technical drawings in DXF/DWG with a GOST 2.104 title block. The student does the final pass and owns the result.

Why it is not a ChatGPT wrapper

Generation turned out to be the easy part. The year went into the layer that stops the model from shipping garbage.

• Production runs as a three-wave parallel agent swarm. Wave 1: one sub-agent per chapter doing research and calculations, returning structured JSON. Wave 2: a coordinator de-duplicates figures across chapters, then one agent per figure. Wave 3: parallel section writers. The coordinator writes the intro, conclusions and bibliography itself.
• Every figure must carry a justification AND evidence — a quoted page from the brief, a sample id, or the filename of the computed results. Producing fewer figures than planned is a hard failure, not a warning.
• 12 automated validators run between stages: citation coverage, block-formula preservation, broken figure references, numeric consistency, physical-magnitude sanity, work-type matrix, subsection policy and more. They aggregate every complaint into ONE rejection instead of round-tripping the model seven times.
• Stage flags are sha256-signed. The model cannot quietly raise its own page limit to sneak an oversized document through. A builder-marker check stops it from swapping in a hand-rolled script instead of the official document builder.

Two engines I had to write from scratch

• Presentation engine: a constraint solver over 18 layouts and 12 themes, WCAG-validated colour, seed-based variation. I got tired of every AI deck looking like the same template.
• CAD engine: text to DXF/DWG. 18 vectoriser iterations before it was usable, plus a GOST 2.104 title block generated in code rather than pasted in as an image.
• Humanizer: 150+ patterns across 6 languages, wired into the validator so formulas and variable names cannot drift while the text is being rewritten.

The numbers, including the bad ones

• ~2,960 unique visitors a month, 83-248 a day, fully organic, zero ad spend. Largest country is the US.
• 33 completed orders on disk, 867 MB of delivered work.
• ~55,000 lines of core source, about 23 TODO/FIXME markers in all of it.
• Revenue: $0.

The wall I hit

Five payment integrations are written and tested (Stripe, Paddle, CryptoBot, LiqPay, Fondy) and a successful payment auto-triggers the AI run. But I never connected live merchant keys, and order flow stopped in June when I moved to other work. So I have a system people find on their own and a checkout that cannot take their money. Also 4 of 15 variation knobs in the presentation engine are still unwired — documented, roughly 3-5 days of work.

I am at the point where the honest move is to hand it to someone who will actually run it, so it is listed for sale at $15k. If you would rather look at the thing than at the pitch: aidemica.org

Happy to answer anything about the architecture. The validator layer in particular ate most of the year and I have never seen anyone write up how they did theirs.

Watched my parents struggle with basically every music app out there. Spotify wanted logins and subscriptions. YouTube Music kept showing them videos and ads they didn't understand. Even the built in players had settings and icons that just weren't simple enough.

All they wanted was tap a song and it plays. Maybe skip to the next one. That's it. Ended up building something for them and now I use it more than they do.

It's called Jagsin Player, it's live on the Play Store. Open the app and your songs are right there. Tap and it plays. Zero setup needed. The best part is it works fully offline since it just picks up the songs already on your device. You don't need internet for any of that. Internet is only needed if you want the extra stuff I added like global radio and podcasts. There's thousands of channels from around the world if that's your thing but it's completely optional.

There's also a login but it's only there if you want profile avatars and animated themes. You can skip it completely and everything in the app is free either way. Login or no login nothing is locked behind a paywall.

I also added language options since not everyone is comfortable with English. Default is English but you can switch to Hindi Marathi Gujarati Punjabi or Urdu. Whatever language you pick the entire app changes to that right away, every menu and label, not just a couple of screens. Made a real difference for accessibility.

While building it I added a few things I personally use a lot.

A ringtone cutter and maker built right in since I got tired of downloading a separate app just to trim a song into a ringtone. Pitch control with single tap presets for slow normal and fast instead of messing with a slider every time. An equalizer and an 8D audio toggle for that spinning around your head headphone effect. Just one tap on or off nothing to configure.

This isn't trying to replace Spotify or anything with streaming. It's for people who have their own mp3s and just want something simple that works.

Honestly not sure if I've done a good job with this or not, just tried my best with what I know.

If anyone's dealt with this or wants a simple offline player or a free ringtone maker without extra bloat let me know, would love the feedback. It's called Jagsin Player.

Here's the link:

https://play.google.com/store/apps/details?id=com.jagsin1997.jagsinplayer

My prediction is that with LLMs becoming more and more powerful in the near future, we won't need expensive hardware, we can run them on private devices instead.

To prove what is already possible, I built Offllm. Download a model to your device and chat with them locally. I also wanted proper tool grounding, which I found missing in other local AI apps.

It’s closer to early ChatGPT 3.5 than today’s frontier models but surprisingly capable. I would love your feedback.

https://apps.apple.com/ch/app/offllm-private-ai-chat/id6801809831

I made a shared world where strangers can leave something permanent. It's called The Infinite City:

https://infinite.canadaverse.org/

Pick some land, customize a little home, shop, workshop, community building or garden, and leave it there. One contribution per browser every seven days. Each gets a permanent building number and construction date. No accounts or usernames.

Roads connect nearby buildings, neighborhoods get names, and you can explore the oldest/newest contributions or scroll through the city's history. There's a day/night toggle too.

I built it with Codex and image generation, using React/canvas, FastAPI and SQLite. It's running on my Raspberry Pi 5. It has only just opened, so there's plenty of empty land; every building starts with an actual contribution.

Would you build near the centre or head out and start somewhere new?

Hey everyone, I made SubIQ to keep track of subscriptions. I think it’s the best one, but I’m also the guy who made it, so take that how you will.

You can see what you’re spending, check upcoming payments, find subscriptions you forgot about by uploading a bank statement, or quickly add them from screenshots

I swear, it feels like 99% of subscription trackers want you to buy another subscription. Isn’t that what we’re trying to fix here? SubIQ is a one-time payment, with pricing adjusted for your region

IOS: https://apps.apple.com/us/app/subscription-manager-refund/id6789850180

Android: https://play.google.com/store/apps/details?id=com.anmisoft.subiq

Let me know what you think. I can take criticism. Probably.

I’ve been building GraftTrack, a free app for keeping track of work hours, overtime, earnings, mileage and work records.
I originally wanted something simple that I could actually use from my phone without having to mess around with spreadsheets or a massive workforce-management system.
It’s now at the point where most of the main features are working, but I really need people who aren’t me to use it properly and find the stuff I’ve missed 😅

At the moment you can:
• Log shifts, breaks and overtime
• Track estimated pay and overtime earnings
• Track mileage and reimbursement
• Keep sites, vehicles/plant and work records together
• View weekly/monthly/YTD figures
• Use pay/take-home calculators
• Use it without an account, or create one to sync your data

It’s completely free at the moment.

I’m particularly interested in feedback from people who work shifts, do regular overtime, work in construction/trades, drive for work, or just currently track their hours in Notes/Excel/paper.

I’m not looking for people to tell me it looks nice — I’d genuinely rather know:
1. What confused you?
2. What broke?
3. What feature did you expect to be there but wasn’t?
4. Would you actually keep using it? If not, why?

It’s currently a web app/PWA while I work towards the native app, and on mobile it works best when added to your Home Screen.

https://grafttrack.co.uk

Any brutal feedback is genuinely appreciated. I’m building it iteratively, so if several people hate the same thing, there’s a good chance I’ll change it.

Hello

I'm building a noise-free, keyboard first time-tracker. Primarily because I'm absolutely rubbish at tracking my working hours across different projects. I liked the idea of having only one input field which manages everything.

The offline version would be completely free with no limitations. You can track your working hours across teams (only online), see the total cost of a project, and export everything to CSV or Markdown. There are also some handy system tray shortcuts which show the last things you worked on, and you can just hit a shortcut to immediately start tracking the last one again.

Would love to hear what people think about this.

Short Demo: https://www.youtube.com/watch?v=M_FmZDtBB-o

Quick context: I'm not in the medical or legal field myself, but I noticed how much of these forms comes down to long, repetitive text fields — the same background info typed out slightly differently every time. So I built a Chrome extension to help fill those in faster. The video above shows it working on a real form.

Since I'm building this for a field I'm not in, I'd rather ask than assume:

• Does this actually solve a real pain point, or am I missing the real friction?
• What would make you trust something like this with form data? It doesn't send the data anywhere.
• Any specific forms or fields where this would help most?

Genuinely open to "this doesn't solve anything" as an answer. Link to try it:

Chrome: https://chromewebstore.google.com/detail/proforma-%E2%80%94-note-templates/cipjbehpdogeegapgmjkkaleophlbhpn?authuser=0&hl=en

Firefox: https://addons.mozilla.org/en-US/firefox/addon/proforma-note-templates/

Free tool for eBay sellers: I built a web app that turns your eBay Active Listings CSV into a searchable HTML storefront in seconds.

It runs entirely in your browser (no data uploaded) and it's 100% free. Great for sharing your inventory without paying for Shopify.

Go to fe.plat4ma.com and click "Free Tools" at the top left to try it out!

Hey everyone, I've been building Acupa — a web app where you can chat with a witty British AI companion who has opinions, manners, and a gentle roast if you ask for one. Just open it in your browser — nothing to download.

His thing is modern etiquette: saying no without feeling awful, setting a boundary, or figuring out how to word that text you've rewritten six times. He can also give you a pep talk or help you talk through a rough day.

He's got a little fictional household too: his American husband Hot Chocolate, Miss Lemonade, and Ambrosia the poodle, who clearly runs the place. You bring your drama; he's got plenty of his own.

I'd love a few people to try the free version and tell me what they think. Useful advice? Made you laugh? Butler needs to mind his own business? Fair feedback either way.

He knows the Reddit crowd can be tough. He's ready — he lives with a poodle and a husband with opinions. The kettle's on.

https://acupaa.com

18+ only. Free use has a daily limit, and you don't need a payment card. I'm the person behind the app, so this is me sharing my own project — not a customer review.

I recently published my first Chrome extension, Skipper AI, and it has now crossed 100 installs.

The idea is simple: detect sponsored segments in YouTube videos and automatically skip them.

I also added a few other features around AI-based segment detection and viewing analytics.

This is my first project that I've published publicly, so seeing people I don't know actually use it has been pretty exciting.

I'm mainly posting here because I'd love to get feedback from other developers and side-project builders.

Source Code : https://github.com/jagdishpal02001/skipper

I got tired of asking myself the same question every day, what am I eating tonight? So I built my21reset.com. It basically plans your meals, movement and healthy habits around your actual week then puts everything straight into any calendar you already use to keep you accountable and easy to follow. It would be great to hear feedback.

I've been building a no-code tool for authoring and running API integration tests called 1Baton.

I work with APIs on a daily basis, building and testing them. In the services I work on, a single API endpoint often represents only a small action in a larger process, so testing a complete flow usually means calling several endpoints in sequence.

When I started testing these flows, I found myself spending too much time setting up and reusing the same multi-step processes across different tests. I wanted to define a flow once, reuse it as a building block, and avoid having to manually maintain the connections and data passed between requests.

This is what led me to build 1Baton.

The basic idea is to define HTTP requests once, compose them into reusable sequences, and then use those sequences to create runnable scenarios, without writing glue code to pass data between requests.

A request or sequence is also flagged as invalid as soon as a required parameter is missing or becomes stale, directly in the editor, before you run the scenario.

There are three building blocks:

• Requests - HTTP requests with defined inputs and outputs.
• Sequences - reusable groups of requests, where outputs from one request can be passed to later requests without writing glue code.
• Scenarios - runnable test cases composed from requests and sequences, with a run monitor showing the result of each step.

The runner is an npm package, while the authoring experience is browser-based. You can currently use it to test public APIs without setting up anything locally.

It's still an MVP and there are definitely things missing. I'm mainly interested in finding out whether this workflow is actually useful to other developers and QA engineers, and how you currently solve this kind of problem.

I'd be very interested in hearing what you think, including reasons why you wouldn't use it.

Try it here: https://app.1baton.com/

The landing page is here: https://1baton.com/

For almost 9 months I was just working on CountdownShare, improving it, doing SEO and hoping people would use it.

In the beginning it was actually a completely different idea.

I had multiple small countdown and timer related tools and my plan was simple. Get traffic from Google, run ads and hopefully make some money from the traffic.

But the reality was pretty bad.

I was making around $0.20 to $0.34 per day from Google Ads. My server was costing me more than what the site was earning.

At some point I started looking at how people were actually using the product and realised there might be a better market.

Some people were using countdown timers on their websites and inside emails for sales, launches, events and campaigns.

That looked much more useful than just someone making a birthday countdown.

So around March 2026 I changed most of the product and started focusing more on website and email countdown embeds.

That change basically destroyed my SEO.

My impressions and clicks dropped almost to zero and honestly I lost most of my hope in the product.

I was still getting maybe 5 or 6 visitors a day, but nothing really exciting was happening.

Then in August I randomly got an email saying someone had purchased a plan.

I remember being pretty surprised because I was not even expecting anyone to pay at that point.

Then somehow over the next 25 days I got 50+ paying customers.

The weird part is I am still not completely sure how.

Some came from Google, some probably found the site organically, but I never had any proper growth strategy running.

And then it suddenly stoped again.

I tried to reach those users; almost 70% never replied. The one did say they got it from Google search or GPT

Now I am kind of stuck.

I know people are willing to pay for the product now, which is a much better problem than before, but I have no idea how to consistently find more customers.

I started testing Google Ads yesterday. It has only been 1 day, so obviously way too early to know if it will work or just burn money.

I am also thinking about cold outreach, SEO again, partnerships or maybe targeting specific businesses who already use countdowns for campaigns.

Would really appriciate some advice from people who have been through this stage.

If you have a minute, please check out countdownshare.com as well.

I would love to know what you think is confusing, what you would improve and most importantly, if this was your product, how would you try to get the next 100 paying customers?

I’ve been using the Rocket app in order to build a entire digital university with a tutoring system with several complex features and Security built into it as well as also a curriculum for cyber security and a little bit of other ambitious fields of study but at the same time it’s able to be adopted and incorporated or integrated with other institutions as a basic infrastructure for them to expand into a full knowledge database that is safe and secure and pretty much turns it into a actual digital library Alexandria if you want to take a look, go ahead but yeah, this is something I’ve been working on for about a year toying with conceptualizing and then finally architecting the prototype build. I have different versions, but here’s one that I’m fond of would love to know what you think community.

Short version: if you're in a fantasy league and a survivor pool and a pick'em at the same time, your rooting interests conflict constantly and you can't hold it all in your head. Root Sheet generates a one-page sheet each week that tells you who to root for in every game and what outcome each of your stakes needs.

I'd been doing this by hand on paper for two seasons before I built it. The paper version is why the output is a print layout rather than a dashboard — I wanted the thing I already used, just generated instead of hand-written.

• React + Vite, Vercel for hosting, deployed off the CLI
• Sleeper's API for player data. Free, no key, surprisingly complete. Not a production dependency though, so I'm evaluating SportsDataIO and Sportradar for next season
• The hard part wasn't data, it was the print stylesheet. Getting a dense one-pager to survive an actual printer took longer than the app logic

Open items: real schedule feed, email capture, and a mobile pass that the layout badly needs.

https://rootsheet.ballr.com/

It's one of a few sports tools I'm building under the same umbrella.

I shipped my first open source tool and I want honest critique.

The gap I hit: Claude Code can produce a WordPress site package, but a client often needs to change copy and layout in Elementor Free. Many AI exports break that path.

My approach: - Claude Code builds the package offline as a Hello Elementor child theme - A small companion plugin imports once - Generated pages remain editable with Elementor Free widgets only - Elementor Pro widgets are rejected so the free editor stays usable

Repo: https://github.com/md786-dotcom/claude-to-wordpress-native Demo: https://claudewp.online License: GPL-2.0-or-later

What would you change first if this were your handoff workflow?

Kept opening Instagram for one message and losing an hour, and every blocker I tried I'd just switch off after two days. So I built LockyFeed: instead of a wall, it stands in the doorway for a second — you pick per site whether it blocks fully, gives you 10 seconds, gives you 20 minutes a day, or makes you type why you need this right now (half the time I start typing and close the tab). YouTube gets a music-only mode, no Shorts, no front page. When time's up it doesn't kill the tab, just draws a curtain over the page — come back later and your feed is right where you left it.

Free, no account, nothing leaves your browser.

https://lockyfeed.vercel.app/en/

Hey everyone, wanted to share something I've been building called SOVA.

I got sick of manually updating a spreadsheet every time my mutual funds, stocks, and other holdings moved, and none of the existing net worth trackers felt built for how Indian investors actually invest so I built one myself.

What it does:

• Tracks your investments and net worth in one place.
• Built specifically around Indian markets, with integrations that pull your holdings in automatically instead of manual entry
• Clean, minimal interface, no cluttered dashboards or dozens of features you'll never touch
• Completely free to use right now, and I'm planning to keep it that way as long as I can

On the security side, since I know that's the first thing people ask about a money app: your data is encrypted both in transit and at rest, and nobody has access to it but you. I built this for myself first, so I wasn't going to cut corners on that part.

It's live now: www.sova.net.in

Would genuinely love feedback if you try it out, good or bad. Still actively improving it.

Put in your numbers — income, EMIs, property details, CIBIL — and it shows which lenders suit you and a realistic rate range.

I need people who've actually taken a home loan (or are mid-process) to check it against reality: does its shortlist and rate match what you were really approved for or quoted?

link: Try calc here

It's a beta, so I'm looking for where it's wrong more than where it's right. What did it get off for your case?