How we used our own problem to build a new product
In our previous projects, we always had the same problem: We didn’t know what was actually happening in our project. Did someone new sign up? Did someone upgrade to the premium plan? Has someone left feedback or even reported a bug? We had no clue.
Our solution for this, at the time, was to check the database for new records every 10 minutes. We both knew that this was not a permanent solution and that we’d need something to solve this problem.
Then we got the idea of simple push-notifications. Whenever a user did something we’d like to be informed about, we would receive a push-notification to our phones. We quickly figured out that the information in the headline just wasn’t enough for most events, so we added a data-field to it. This was supposed to contain more detailed, but still short information about what had happened.
After testing and loving it, we wanted to give others, who also encountered the same problem, a chance to use it so we created a website and polished everything a bit.
Now we are ready to show you guys the first version and would really appreciate it if you could take 5 minutes to try https://rufbit.com/
Awesome service @Mansuro ! I just tried the API using my REST API client and it was cool :) Also, about app error related notifications, how do you think rufbit compares to Sentry https://sentry.io/ ? :)
Thanks for testing :) Do you feel like rufbit would be something you'd use in the future?
I haven't used Sentry before so I can't really compare it. Sentry seems to be focused on error reporting while rufbit is meant to be used for all kinds of notifications, including error reporting.
I think both tools are suitable for error reporting but considering that Sentry specializes on it, they are probably the better choice in that particular area.
Rufbit sounds nice. For a small service I could use it, but if things scale, I might go for my own custom service or an open source one, which can notify me on a platform like slack if not web push notifs or mobile notifs. For eg alertmanager, a component in prometheus ecosystem does something similar for prometheus alerts.
I think I saw that graphic with the 2 people and the desk, 3rd time , on IN products, you should at least give unlimited notifications, or higher numbers, we takling about rest requests, db-rows, not manually handled ecommerce orders or so.
Yes, unfortunately these graphics have become quite popular here.
You are right, the numbers aren't that high but we purposely chose to do so. If you think in terms of notifications on your phone, these numbers are pretty big actually. Lets take 2500 notifications / 30 days and you get 83 notifications a day. I don't know about you but if I got 83 notifications on my phone every singe day, I'd probably freak out.
@Mansuro
Cool app. You really nailed the USP with your Title.
Congrats.
Thanks @greenflow
Hi,
I would like share a real story of how a problem give rise to a new product.
Two founders started a company caled 8iCreations for web design & development work. It works fine and they were earning a huge profit but they faced fall down due to cash flow mis-management. And to solve this kind issue for other entrepreneurs, they have created a software named ProfitBoard.
This software help startup business owners in cash flow management, budgeting, Financial Analysis, Project Management, Project Profitabillity etc. https://www.slickaccount.com/profitability/index
They also provide free trial option. Go for it..
Thanks