
Neverinstall
Your browser is your operating system.
We have come a long way since our launch in just 2 months, we have now more than 3000 signups and 250 active users using the platform for more than an hour daily.
We are improving our platform and adding new features every day. With the great community we have established in the last 2 months, we want to add more and more features to make our users more efficient.
A quick sneak peek of our roadmap -
- More servers are being added across various regions
- More pre-installed stacks to devtools
- Improved performance and reduced latency
We have grown to a team of 5 people in the last 6 months and are looking to hire more people to help us grow the community. We are looking for anyone interested in building neverinstall with us!
We decided to show our platform on Hacker News as it was our first time there and we thought we'll give it a try. The results blew our minds: we were trending on HN for 2 days straight.
It was the first time our little platform saw so much traffic. We got a lot of interesting comments on HN (some hate as well :P), some were even truly helpful. We learned a lot about the areas where we need to improve our UX, pricing, and performance. Most importantly, we got a lot of signups.
Overall it was a pretty engaging discussion and we received super valuable feedback.
Here is the link to HN - https://news.ycombinator.com/item?id=27904254
1 Like
Comment
We launched the platform on Product Hunt and we were super excited about it. We all know that PH can be a great source for users and traffic, but in order to get there, you need to know how it works.
I have to admit that we knew very little about Product Hunt and had no prior experience whatsoever.
We all were curious how the platform would be perceived by a large audience.
Despite a busy Wednesday on PH and with the launch of some great products, we made it to the top 5 products of the day :)
We also made it to the PH newsletter which we wanted, it was a successful launch for us. we learned a lot about PH and most importantly we received pretty good reviews and feedback.
All 9 reviews with a 5-star rating!
1 Like
Comment
After a month of spending our nights and weekends building, we had 25 daily active users. We had a rough idea of what users liked and didn’t like about the platform. We decided to sit together and do a quick analysis of the beta user feedback and design a plan of action for addressing the key needs of potential users.
We were getting users from all over the world who were actively using the platform for hours. This was a good sign for us.
For the first time, we felt like we were going to succeed in creating a product that could solve a problem.
1 Like
Comment
We finally launched the platform to the public and gave access to all our early access users who signed up.
This was a big milestone for us, and we were more than ready to share our project with the public. We had a lot of interest from early access users, but now we wanted to see how far it will go with the general public. We also wanted to make sure the product is matching the user expectations and we see what we need to do to improve it.
We’ve made a lot of changes to our platform since we launched on the private beta and the early access users helped us test the platform and gave us feedback on how to improve it further
1 Like
Comment
It all started by asking people on Reddit what they think about using their memory-intensive desktop apps like - Android Studio, IntelliJ etc. on the cloud through a browser with additional features like
- Real-time collaboration
- Access desktop apps from any device
- Fast internet virtual browsers
It was amazing to see their interest in using such a platform.
Here are the links to subreddits -
https://www.reddit.com/r/androiddev/comments/j0o51v/introducing_android_studio_on_the_cloud_request/
1 Like
Comment
About
We wanted to solve some key problems that users face while running resource-intensive desktop apps. These include dependency on limited hardware resources, lack of real-time collaboration, and accessibility issues.

Comment