The 1st version was a chatbot app, think of it like an accountability coach that you text with to track habits and stay accountable.
Rithm landed as the #4 product of the day on ProductHunt, had some good initial traction which proceeded to fall off a cliff.
Here are the 8 lessons for a failed version 1, see video and blog post.
Hope this helps some makers out there!
> There are a million and 1 habit and goal apps out there and I made the mistake to think that just because there are a lot of products in this space, doesn’t mean that there is a lot of businesses in that space.
I think you were thinking of two different ways to phrase that, mixed them up, and the result is that it says the opposite?
As in, either remove 'I made the mistake to think that', or 'doesn't mean that'.
Until that happens, it would be a huge waste of time and money for the developer to build an Android version, since it too would fail as a product, just like the iOS version.
Multiplying 0 by 2 is still 0.
The situation might be different for an app whose success depended on the user's ability to use the app to communicate with all of their friends, some of which had Android phones.
There are of course frameworks out there to help you build one codebase for multiple platforms, but if you go down that route, if you aren't familiar with the framework, you have to learn it. There are going to be quirks in them that you're not aware of. Maybe framework version X only works with iOS version Y and Android version Z. It just goes on and on. Frameworks aren't perfect either, and things don't work exactly the same across platforms even with the framework.
Think Clubhouse only moving to android when it was working on iOS.
Combine a Tamagotchi with your app, have the user "feed" them with his "habbits". At least you would combine two things.
With the chat bot? Move on.