HivePulse.app: Financial Transparency Report update before launching

The Hive Pulse aims to offer real time insights and intel on user activity on the Hive blockchain. The project is development on my own (@behiver) and all the costs are supported out of my own pocket. The only revenue streams foreseen in the near future is through content creation and engagement on the project with communities and users from the Hive blockchain. I intend to present periodic financial reports about the costs and revenues that the project will involve or attract.

While I am still laying down the infrastructure for the app, I already have associated costs. I will start with them as the project evolves and also keep an eye on eye revenue coming my way. I don't have big hopes in the beginning, but maybe in time things will improve. And if this initiative or experiment proves itself - who knows, maybe this will open doors for additional projects in the Hive ecosystem. So let's start and see some financial data even before launching the app.

There are two people actively involved in this project, but for now (and maybe forever) the time and work put will imply $0 (zero) costs. One is an OG developer, the other is myself which I am managing the app and putting things together from my own experience in this ecosystem (since 2017), but not limited to it. We are both well anchored in software development, so some hustles will be easier to overcome than for some people without background in the industry.

This is the first Financial Report for the hivepulse.app project. I intend to make it a weekly report in order to see how feasible it is to run it on my own, even if considering that I put my time for free maybe doesn't full reflect the associated costs. But this can be maybe a starting point and an inspiration also for others that might want to start a project and see what it takes to launch a product on the market. At the moment I think that by having the domain name, VPS hosting and initial development put in place, it should be a good starting point. But I still need to do some work on infrastructure until I will be launching the app (like TLS certificates, Load Balancer and/or Web server that the app will be deployed on) and others around that.

And while the scope of this article is to track the financial overhead of such a project, as a teaser I've put also a screenshot from the app. Hopefully this week I will be able to advance more on it and lay down the full infrastructure for it... and maybe even deploy it. That's all from my side, see you with further updates soon.

Posted Using INLEO