This week we posted a short survey for Micro.blog customers to provide feedback about the service. I was particularly interested in some of our extra features like bookmarks, bookshelves, and notes. These aren’t necessarily well-known and I’ve been thinking about how to better position them within the Micro.blog platform and companion apps.
We’ve gotten about 250 responses so far and they are still coming in. That’s enough to see some trends. I’m including notes after each chart.
Which operating systems do you use Micro.blog from?
![](https://cdn.uploads.micro.blog/10/2024/survey-os-chart.png)
No surprise here that Mac and iOS are the majority considering my roots in the Apple developer community. I’m happy that Windows and Linux are starting to poke into the stats, though. That’s a good indication that we should continue to prioritize the web platform as the most complete, primary interface for Micro.blog.
What plan are you subscribed to?
![](https://cdn.uploads.micro.blog/10/2024/survey-plan.png)
I included Micro.blog Teams as an option but we don’t even have a link to subscribe to that plan anymore, so no surprise effectively no one uses it. We have actual subscription data in Stripe, but I wanted to include this question because it tilts the data more to active users.
This price is:
![](https://cdn.uploads.micro.blog/10/2024/survey-price.png)
I’m happy with this. 97% think the price is just right or a great value. I wonder if some of the 3% who think it’s too expensive are from countries where their local currency doesn’t go quite as far against the US dollar, because I do hear from those folks. I wish I had thought to ask where people are located.
Do you use any of these companion mobile apps?
![](https://cdn.uploads.micro.blog/10/2024/survey-apps.png)
Our customers love books. Strata is still iOS-only but we have the Android version ready to release. We also have an update to Sunlit almost ready, with the new icon and some fixes.
What are you favorite services to cross-post to?
![](https://cdn.uploads.micro.blog/10/2024/survey-crosspost.png)
There were a few “none” answers here too that I edited out of the chart, and one Farcaster, which I’m keeping an eye on. These charts are from Google Forms, but I cleaned them up in Acorn to be more readable.
Twitter X is probably never going to die. Also, don’t read too much into Bluesky being more popular than Threads. Our automatic Threads cross-posting is still in beta, so not available to everyone yet.
What should be our most important priorities? Pick 2!
The chart was a mess for this because there was an “other” choice with lots of suggestions for what we should work on, so I’m not including it. The top responses were performance and stability, the text editor, finding new people to follow, blog themes, and timeline position sync.
How would you feel if the advanced bookmark features like highlights, tags, and archiving were split off into our app Strata?
![](https://cdn.uploads.micro.blog/10/2024/survey-strata.png)
I asked this question because these features are great and I use them every day, but they tend to get lost in the blog-focused interface we have today. I always worry about clutter in the UI. I think moving them into a separate “product” could help with both marketing and user experience. If we do this, there would be a bundle to subscribe to everything, and no prices would change for existing users.
For anyone worried about us always adding new features instead of making what we already have better, I consider Micro.blog feature complete now. Almost everything we do from here will be refining what we have. There will always be improvements, but I don’t think there will be huge new core features at the scale of photos, podcasting, bookmarks, notes, and bookshelves.
Any other feedback about Micro.blog? Features you like or things we can improve.
This freeform question was at the end for general feedback. Those responses were incredibly useful. I’m not going to share them publicly because they feel private-ish, but I’m reading all of them. There are some common themes such as not getting stretched too thin, making sure the service is robust, and improving the UI.
We’ll continue to keep the survey open for another week in case there are some late responses. Thank you, everyone!