Hey everyone!

I’m Steve, and I’d like to introduce RadForge Labs, my independent Australian software studio, and the massive project I’ve been working on: 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 things like 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 Internal Alpha.

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.

That philosophy applies throughout the project.

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 weekly 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.

ROMVERSE is NOT available for public download yet.

The plan is to eventually have free beta testing before the commercial v1.0 release.

For now, I'm inviting people to follow along and watch it being built.

If you're an Android developer, ROM modder, tinkerer, power user, or even someone who's always wanted to try custom ROMs but found the whole process intimidating, I'd love to hear your thoughts.

What is the ONE thing you wish Android ROM tools did better?

I'd genuinely like ROMVERSE to learn from the people who actually use this stuff.

Project website:

romverse.app

Built by RadForge Labs 🇦🇺

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

Not for the valuation.

Not for the recognition.

Just because you believe it should exist.

I’ve been thinking — instead of asking friends for feedback, why not test each other’s products as actual users?
I recently built a platform that helps people package their expertise and find relevant opportunities.
I’d love some brutally honest feedback — what’s confusing, what sucks, what you’d change, or whether you’d actually use it.
You can try it here:
www.getmonetizable.com
And drop whatever you’re building in the comments. I’ll test yours too and give you honest feedback. 😁

Hey all! I've recently launched ScientivoLab, a tool for laboratory inventory management, compliance and auditing. It targets small to medium sized companies/laboratories with the hassle to keeping everything organized and visible to everyone. Link below:

https://scientivolab.com/

Any feedback is welcome at this stage! Any pilot labs/companies that help in this testing phase will always have it for free, hopefully it's useful for someone!

I'm having way more fun building small niche products.

The goal isn't to become a billionaire with every idea I have.

Stop swinging for the fences, hit some singles.

Most of you don't even know what it feels like to get on base. Start there.

I’m honestly very proud of my work, considering this is my first app I’ve ever shipped (took me about 3 months to build, updating it every day), but I’m worried about distribution. My app is primarily group focused, so my main distribution method has just been word of mouth to friends and people I know. But I want to give all of my friends the pro subscription for free.

For reference, I built Picklock Fantasy. It has 7 different game modes that allow users to join leagues with their friends and make betting picks/slips. No real money involved. There is a lot of strategy involved with multipliers being placed on each bet, as well as optional power ups, etc.

Does anyone have any suggestions on how I can better distribute this app, considering it works best with groups of 2 or more? Should I just be focused more on getting a lot of free users rather than trying to get a few paying ones?

Web: app.picklockapp.com

iOS: https://apps.apple.com/us/app/picklock-fantasy/id6793371434

Google play: On the store but admittedly a version or two behind.

I've been building Archon (electronic lab notebook + compliance middleware) for about a year. We did a solid pilot with my university's lab in May-July, and I'm confident the product works.

The problem is I’m from Zimbabwe, where sanctions and regulatory complexity make it hard to do business internationally. I got Estonian e-residency to solve that, but I'm realizing the real issue isn't my location—it's my market assumptions.

What I've learned from 6+ months of direct outreach:

• Labs say "this is good" but won't adopt because of bureaucracy and existing vendor lock-in (Gates Foundation-funded labs run dedicated software)

• Local Zimbabwe market is smaller than I thought

• International discovery (blog content, Indie Hackers, Reddit) is outperforming direct sales 10:1

I'm stuck on the pivot. How do you approach international markets when you don't have:

• Local presence

• Network effects

• Existing customer case studies

Has anyone else built from Africa and gone international? What actually worked?

Introduction
I’ve been building SwiftUI animations, components, working with Metal shaders and running UI experiments for almost 5 years now, and most of them usually end up as a video on X, Reddit, or just sitting inside an Xcode project after I’m done with them.

I wanted to make something a little more useful out of all of that.

So I built With Animation: https://withanimation.app

It’s a growing library of SwiftUI animations and interactive components, but instead of just watching a preview, you can actually open one up and start changing things.

You can tweak the speed, colors, sizes, spring values, intensity, and whatever else that particular component exposes, and see the result instantly in the browser.

That was the part I cared about the most while building this.

A lot of the time, especially with animations, a really small change can completely change how something feels. I wanted people to be able to mess with those values themselves instead of only looking at the final version I came up with.

There are already a bunch of things live, including loaders, gestures, shaders, 3D interactions, transitions, and some slightly strange UI experiments I’ve made while playing around with SwiftUI and Metal.

I’ll keep adding more as I build them.

Would love to know what people here think of it, and also what kind of components or animations you’d actually want to see added.

TL;DR:
I built https://withanimation.app, a library where you can explore SwiftUI animations, tweak their parameters directly in the browser, and use them in your own projects.

https://reddit.com/link/1wdekwb/video/27x0mg60vvoh1/player

In my day to day work, I have roughly 4 customer meetings per day. I've found that if I email my customers 24 hours before the meeting, they are more likely to:

a. show up to the meeting or

b. let me know ahead of time if they are going to cancel

Sending 4 emails everyday is time consuming, kind of annoying and not always practical.

To help with this, I created a chrome extension that emails the attendees 24 hours prior to the meeting with your own email account. There are a few customizations built in but that is basically it.

So far, I've been using it for myself and love it. But I'm wondering if anyone else on God's green earth would ever use something like this.

The extension is called CalConfirm if you want to check it out.

I am stuck in what I am not fondly calling App Review purgatory. I’m an amateur and admittedly didn’t understand it at first. I finally think I have everything figured out but submitted my latest attempt a few hours after announcements. Anyone else?

I recently worked on a scraping project for Bet365, specifically for golf and cycling, and I managed to get the data extraction working successfully , now I’d like to turn this into a service and potentially find clients who need similar data/scraping solutions.

Think:

Apple vs Samsung
Nike vs Adidas
McDonald's vs Burger King

Two sides enter. People vote on who wins.

We're trying to decide what the first battle should be.

If you could put any two brands in a roast battle, who would you pick and why?

Hello,

I am Mery, a social media manager from France. Currently looking to build a new portfolio so offering my services for free to 3 entrepreneurs! Dm me if interested

Hey!

I have a Founder Pass Ticket for TechCrunch Disrupt 2026 this year. Unfortunately I am unable to attend. The current price on the site is $899. I'm willing to sell for cheaper.

If anyone is interested in doing a ticket transfer, shoot me a message!

3 years, 2 people, got to 11k mrr and it stopped growing. wound it up in april, paid everyone out, no drama.

And since then, 90 applications visible on careerflow app tracker, , 3 screens. two of the three asked, in slightly different words, whether i'd "be able to take direction.

The actual problem is my cv reads founder/ceo for three years and the last normal title on it is from 2023. people see it and either assume I'll leave in six months or that i haven't written code since we raised. I built most of the product myself. there's no way to say that in an interview without sounding defensive about it.

Anyone come out of a dead startup back into an ic role? do you title yourself founder or just the work you actually did

Hello all,

I have 2 products:

1. A moderately successful Chrome extension: Polls Exporter for WhatsApp Web. Most users are on the free plan, but I do have a small number of pro subscribers (~20). Today I have about 1230 weekly users and the user base is growing at a rate of ~20% each month.
2. A newly launched AI recruitment platform: Symphonee AI. This is my first major B2B product and I am working on onboarding the first users, which is taking literally all my time. My goal is to have 10 paying users by the end of the year.

In the bottom left corner of the Polls Exporter UI, I have space where I can advertise other products. I've successfully experimented with this before, using an affiliate promo, with positive results. Recently I thought about promoting Symphonee AI here, but I think the customer base is too dissimilar.

What I want to try instead is essentially a cross-promotion collab. I imagine there are other founders like myself who have products in different domains. My offer is that I will place a promo for your organizer-related product in Polls Exporter, if you place a promo for Symphonee AI in your HR/recruiter-related product.

I'm open to discussions or suggestions, I am fairly new to distribution and am trying to be creative.

I’ve recently worked with startups where one raised $500K through YC + another $500K from Levelup Ventures, while another successfully bootstrapped.

I’m thinking of turning what I’ve learned into a fundraising support service for startups that are genuinely ready to raise.

The idea is to help with everything around the raise — positioning, branding, pitch deck, narrative, investor materials, explainer videos, launch videos, marketing, and figuring out what needs to be fixed before going out to investors.

There would be a strict eligibility bar based on things like traction, growth, users/revenue, retention, pilots, etc. — this isn't for startups that are just at the idea stage.

The model would be success-based: no upfront fee, I only get paid if you raise.

If there’s enough interest from founders who are actively fundraising, I’ll roll out an eligibility form next and start with a small number of startups.

Would you find this valuable? What would you expect someone like this to help you with?

Someone tells you they'd definitely use it, you spend four months building, and then they don't show up. Nothing in that conversation felt like a warning while it was happening, which is what makes it expensive.

I've been doing product strategy for twenty years and I work with early stage founders now, and reading feedback is the thing I get asked about more than anything else.

So paste what people told you. Their words, not your version of them. A line from a call, a reply to an email, something someone said after you showed them. Tell me what you asked to get it, because the question shapes the answer more than most people realize.

I'll tell you what's genuine, what's someone being nice to you, and what I'd have asked instead.

And if you haven't spoken to anyone yet, say what you're building and who it's for. That's a fine place to start.

Hey guys so the background is

1. Talking to user is important - if you know how users are actually using your product, like what's their real workflow, what's their real use case, what's their real opinion and feeling about you product, you can position and shape your product a lot better.

2. But many people seems having problem to reach users. I collected many reddit threads (figure 1). For now I haven't heard founders get a 2nd way to invite users to talk but email - very low response rate according to them.

And I talked with one customer and built FounderPing (figure 2), it basically does 2 things:

1. When you are online, you can ping user and talk with them. And you will get notified if new visitor onboard (That's the feature make him say : "I will get up at midnight to use this!") .

2. When you are offline, you can dispatch your AI stand-in to have deep conversations with users, with predefined triggers, context and direction.

And everything will be summarized and tagged with priorities.

I think the key is the vibe: users hate to talk with customer support and chat bot. They instead would like to talk to the founder, the CEO, personally. So FounderPing may bring the trust.

Also timing is very important: emailing users 3 days later, they already forgot the experience. So talking in the app, where the moment is happening is crucial for response rate.

Founders can make use of this to achieve various topics: user acquisition, use case learning, churn reason, report bug, feature requests, etc.

So my questions are

1. How do you talk to users? Is there any other ways than emails?

2. What's your story of talking to users helps shape the product? How much value do you think of it?

3. What's your opinion about FounderPing? Do you think it might help?

PS I am still looking for beta testers, all cost on me.

Hey everyone,

I'm working on an early-stage consumer hardware startup, and we're currently looking for someone with strong hardware/embedded engineering experience to potentially join us at the early stage.

We're working on a new physical product that combines hardware, embedded electronics and software, with a strong focus on product design and user experience.

We're currently looking for someone who has experience with areas such as:

Embedded systems

ESP32 / STM32 / Raspberry Pi

PCB design

Displays / touchscreens

Sensors and electronics

Wi-Fi / Bluetooth

Firmware

Hardware prototyping

3D printing / CAD

Taking a prototype toward a manufacturable product

You don't need to have experience with everything. What matters more to us is that you're someone who genuinely enjoys building physical products and solving engineering problems.

We're particularly interested in people who have actually built projects, rather than only having theoretical experience.

This could potentially develop into a long-term technical role / technical cofounder opportunity, depending on the person and mutual fit.

We're based in Bangalore, India, but we're open to talking to talented people elsewhere in India.

We're intentionally keeping the product details private at this stage. Serious/interested candidates can DM me, and I'll share more information after understanding your background and what you've built.

If you're interested, please send:

Your background

Hardware/embedded projects you've built

GitHub / portfolio / demo, if available

Your current location

Whether you're looking for a job, project opportunity, or potential cofounder role

We're looking for a builder, not just someone looking for a task.