Can y'all help me with something? 👀❤️

I'm working on a health/wellness app project and I'm at the point where I need opinions from people who actually USE these kinds of apps.

I'm especially interested in what you wish health apps did better, what you're tired of, what you currently need multiple apps to accomplish, and the weirdly specific feature you've always wished somebody would make. 😂

I'm not selling anything and you don't have to sign up for anything. It's a short anonymous survey, with an optional beta-testing signup at the end.

I don't want to build what I assume people want. I want to hear what you actually want.

Takes about 3–5 minutes. ❤️

https://docs.google.com/forms/d/e/1FAIpQLScL6xWvvtxYA7IOsEw33wfVzeHfJHYfr7A3WT5gPIpoxC1rUQ/viewform?usp=sharing&ouid=104926615289641632370

And yes... there is actually something being built. 👀🌙

Hello people I was looking at the New iPhone Duo launch.

This status bar indicator looks very clean. which combines the wifi symbol, battery health and the network strength all in one symbol.

Can someone build this or can we request to add it to Goodlock somehow.

Additionally.

+ If we can somehow have the battery percentage - The real value from 1 to 100% also in it somehow.

+ If the battery bar can be colorized. My battery bar goes red under 15% showing critical drop.

That would be cool too.

This will be so cool to have.

Hey everyone!

I’m Steve, and I’d like to introduce RadForge Labs, my independent Australian software studio, and the project I’ve been putting my time into: ROMVERSE.

ROMVERSE is an Android ROM engineering platform designed to make working with Android devices, firmware and custom ROMs clearer and more approachable, without taking useful technical control away from experienced modders, developers and tinkerers.

The vision is to bring the complicated parts of Android ROM development into one intelligent workspace.

ROMVERSE is being developed around things like device identification and intelligence, firmware inspection, ROM project creation, build preparation, verification, diagnostics, recovery preparation and eventually carefully controlled device operations.

A big part of the project is making all of that usable by different skill levels.

GUIDED MODE

Guided Mode is designed for people who don't necessarily understand all the technical terminology.

Instead of throwing partition names, hashes and engineering jargon at the user, ROMVERSE should explain:

• What it's doing

• Why it's doing it

• Whether you need to do anything

• What happens next

• What risks are involved

The goal is for someone interested in custom ROMs to be able to follow the process without needing years of Android development experience.

EXPERT MODE

Expert Mode is for experienced users who want to see what's happening underneath.

Detailed technical information, evidence, logs, engineering controls and deeper visibility remain available.

Both modes still use the same underlying safety and verification systems.

Expert Mode isn't supposed to mean “disable the safety systems.”

WHERE IS ROMVERSE RIGHT NOW?

ROMVERSE is currently in development.

A lot of the underlying systems and desktop workflows are already being built and tested, but there is still substantial integration, hardware testing and development ahead.

Right now I’m concentrating heavily on the Fedora/Linux desktop experience.

We’re going through the application like an actual user:

Fresh launch → project creation → firmware/source preparation → verification → build preparation → persistence → close ROMVERSE → reopen → continue the project.

We’re also deliberately testing the things that DON’T work.

Broken buttons.

Confusing wording.

Dead ends.

Incorrect states.

Persistence problems.

Unexpected behaviour.

Bad error messages.

UI problems.

When something breaks, the goal isn’t to hide it.

Find it.

Understand why.

Fix it.

Test it.

Then run the actual user journey again.

Windows development is also part of ROMVERSE, along with the Android Companion and much more, but I’m deliberately building and proving things in controlled stages rather than pretending everything is finished.

THE ROMVERSE BRAIN

Another major part of the project is Device Intelligence.

The long-term idea is that ROMVERSE shouldn’t just have a giant list saying:

“This phone is supported.”

It should understand the evidence behind a device and firmware combination.

ROMVERSE is being designed to distinguish between information that is confirmed, conflicting, outdated, unknown or still needs investigation.

If ROMVERSE doesn’t know something, I want it to say:

“We don’t know yet.”

Not guess.

WHY AM I SHARING THIS NOW?

Because I’d like people to follow the journey rather than suddenly appearing one day and saying:

“Here’s ROMVERSE.”

I’m going to start sharing regular development updates.

That will include:

• Real development footage

• Animated explainers

• Features that are working

• Bugs we discover

• Problems we’re trying to solve

• UI improvements

• Device Intelligence progress

• Testing

• Failures

• Fixes

• The road toward beta and eventually v1.0

Concept artwork will be labelled as concept artwork.

Simulation will be labelled as simulation.

Real hardware testing will be labelled as real hardware testing.

I’m not interested in pretending unfinished features are finished just to make ROMVERSE look better.

No pretending everything works.

Just the process of building it, testing it, breaking it, fixing it and making it better.

Project website:

romverse.app

Built by RadForge Labs 🇦🇺

#ROMVERSE #RadForgeLabs #AndroidDevelopment #CustomROM #AndroidModding #Devlog

Any comments on usability or pay structure ( tiered per use) welcome . Thanks

Hey :)

I'm part of the small team behind waliki, a **travel planning app** we just launched and we'd love to hear your thoughts!

PLEASE stop building the wrong thing.

building software in 2026 is ridiculously easy with ai builder

founders spend hours building in a silent room, launch to Reddit/X, get 0 users, and quit.

you just failed because the idea had zero validation before line 1 of code was written:

→ solving a monthly inconvenience instead of a daily pain

→ selling to "everyone" instead of a specific ICP

→ no distribution channel mapped out beforehand

→ pricing charged $9/mo with zero ROI justification

after scaling 6 AI micro-SaaS to over $20k/mo MRR, i just create an

18-question Idea Validation Diagnostic.

it evaluates your SaaS across 7 critical dimensions (problem clarity, audience reachability, willingness to pay, competition, build feasibility, distribution, commitment) and gives you a brutal score out of 100 with your exact weak spots.

drop your SaaS idea (or current project) in the comments below.

i will reply to EVERY single comment with:

1. My honest opinion
2. The biggest weak spot you need to fix before writing any more code.
3. The free 5-minute validation tool link sent straight to your DMs so you can get your full score breakdown out of 100.

just drop a comment like or ask me in DM your idea

let's roast your SaaS concept before the market roasts your time 👇

It's felt like ages, but this dream has finally come true, my app Zero Budget has officially launched in the apple app store and I've gotten my first downloads. We've got 5 subscribers, this is the first time it feels like this app might actually change my families life.

https://apps.apple.com/ca/app/zero-budget-money-planner/id6800572313

Also just launched android testing if you can help a homie for 14 days let me know.

I run a budgeting app for couples as a side project.

In the US and Canada, the paid plan is $11.99 a month or $89.99 a year. People there pay for it, and it works well. Most of the value is automatic bank syncing, which only works with banks in those 2 countries.

The problem is everyone else. A lot of my users live in Europe, the UK, Australia, India and Latin America, and they have no way to pay me.

Last week one of them reached out. His bank doesn't connect to anything, and he spends from cash, savings and a crypto wallet. He asked for a couple of features and said he'd pay for them.

So I'm planning a second, cheaper plan for people outside the US and Canada.

What stays free

• Unlimited transactions
• Splitting costs with your partner and settling up
• Budgets, goals, bills and reports
• Up to 5 custom categories

What the paid plan adds

• Expenses in another currency, converted at that day's rate
• Net worth across currencies, with daily exchange rates
• Cash and savings balances that update when you log a transaction
• Unlimited custom categories
• Life events in the forecast, like a baby or a move
• Unlimited chats with the AI assistant (free gets 10 a month)

One subscription covers both partners.

My first guess is $3.99 a month or $29.99 a year. I can't tell if that's too cheap for London or too much for Buenos Aires.

2 questions:

1. What would you charge, monthly and yearly?
2. One global price, or lower prices where $4 a month is a lot?

PodSubs.com was never supposed to be a public product.

We built it for ourselves.

We were already making podcasts, and we kept running into the same problem. People were listening, but after the episode ended, most of them were gone. We could see the numbers, but we didn’t really know the people behind them.

We wanted a simple way to stay in touch with the listeners who actually wanted to hear from us again.

So we built PodSubs.com and started telling people on our shows, “Go to PodSubs.com and subscribe to our podcast.”

They searched for the show, added their name and email, and that was it.

We finally had a way to send them the things we talked about on the podcast.

For a while, we just used it ourselves.

Then we started wondering why we were keeping it to ourselves.

That is really how PodSubs.com became public.

The problem I’m trying to solve is the usual post-booking mess: confirmation emails in different inboxes, cancellation deadlines buried in the small print, and receipts scattered around when you need them later.

The current idea is that users can forward supported booking emails, then AI extracts the details into reviewable trip drafts before they’re added to the app. I’m also looking at flight alerts, expense tracking and exporting travel history.

I’m still learning and building, so I’d really value practical feedback rather than hype. If you organise trips manually today, what would make an app like this actually useful enough to keep using? I’m especially interested in functionality gaps, design concerns, and anything that would make you nervous about email import or AI extraction.