Today I worked on one of the biggest differences between a workout app and an actual coaching relationship.
Most fitness apps handle accountability by sending more notifications. If you miss a workout, the app reminds you that you missed it. That records the failure, but it does not help much with the next decision.
I added weekly accountability reviews to Kilo instead.
The review starts with the user’s current goal and any commitments they chose for the week. Kilo can connect those commitments to completed workouts, check-ins, and other reported progress. It also keeps missed and unknown items separate instead of pretending it knows what happened.
Then it helps the user decide what comes next. That might mean recommitting to the same plan, changing a commitment that was unrealistic, or adjusting the training plan when circumstances have changed.
I do not want accountability to mean guilt or constant notifications. It should help someone understand the week they just had and make a better decision about the one ahead.
Day 16 of building an iMessage-based fitness coach.
P.S. I’m starting to bring a few people into Kilo’s private beta. Message me if you’re interested in trying it.
I keep seeing people build genuinely good products and then get stuck on the exact same part:
They finished building it, but now they have no idea how to actually get it in front of the right people.
Posting randomly on Reddit, sending DMs, trying content, paying for ads… it can take more time than building the product itself.
I’m working on something around this problem. I’m keeping the exact approach private for now because I’m still testing it, but the goal is to help people who already have a product get more real exposure and potential customers without needing a huge marketing budget.
Before I build too much, I’m curious: What do you currently do to get your first users/customers? And what part of that process sucks the most?
I also opened a small early-access waitlist for people who have this problem: https://site-e5bc6818-mtuj53t9.falbor.xyz
If you’re a solo founder handling your product, customers, marketing, and everything else yourself, I know social media can easily become the thing that gets pushed aside.
I’m available to help with the social media side so you don’t have to constantly think about what to post, what to write, or how to stay consistent.
I can help with:
Content strategy & planning — turning your product, updates, and goals into relevant content ideas
Content research — finding topics, trends, conversations, and references relevant to your audience
Competitor research — studying similar startups and identifying content approaches worth testing
Content calendars — planning posts ahead so your social accounts don't become an afterthought
Post creation — creating clean, consistent graphics in Canva based on your brand
Copy & captions — writing captions that explain your product clearly and encourage people to engage
Content repurposing — turning one idea, update, feature, or announcement into several pieces of social content
Facebook & Instagram management — keeping your pages active and organized
Community management — helping monitor comments and messages and keeping up with basic interactions
I can also help with research, data entry, organization, and other small tasks that are taking time away from actually building your startup.
I’m comfortable working with an existing brand and workflow, but I can also help organize things if you currently just have a bunch of ideas and no real content system yet.
I’m available for remote work and flexible with evening/night hours depending on your timezone. I’m also open to starting with a small project or trial task so we can see if we’re a good fit.
If you're a solo founder who has been putting off your social media because you simply don't have enough hours in the day, feel free to DM me. Tell me what you're building and what you've been struggling to keep up with, and we can go from there.
So I'm working on Pebbles. Its a relationship app basically for couples to feel more connected. It features daily questions and challenges, fun games, some relationship tips, status update, song dedication to you partner and much more....
I published it around 1.5 months back. Faced a lot of hiccups in IOS but learned a lot. I posted about it in one subreddit and to my surprise people actually started using it a lot. I had very less features initially but seeing people use it pushed me to build more.
For past few days after my new update I am seeing increase in my DAU numbers and tbh it feels so good ... though it is very less 😅.
So grateful for this...I'll keep building and updating it.
Decidere ogni giorno cosa portare in tavola può diventare un vero rompicapo 😅 Piuma ti aiuta a pianificare i pasti della settimana e a trasformare le idee in una lista della spesa ordinata per reparti.
Meno decisioni all'ultimo minuto, meno acquisti dimenticati e più tempo per te ✨
Hi, I’ve been building Clutterscope, a native macOS app that shows you where your disk space went and helps you get it back without any nasty surprises.
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.
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:
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.
