Just chipping in my thoughts here. Normally I’m always the first one to request a mobile app. In this one case, however, I would actually lean towards not being so adamant about it.
Here’s my reasoning (and speaking only from my own experience, I don’t have any insider knowledge on Fibery). What Fibery is doing really is in a “goldilocks” zone. It’s doing things that I’ve never seen, and I’ve seen (and used) nearly everything. There’s literally usecases being solved here that I’ve tried to solve for many years, and often I’m able to implement what I need in mere minutes. I’m thrilled to be implementing this slowly in multiple companies. A lot of the UI is very intuitive (formulas, etc.) and there’s a ton of features that are really nicely built out. That being said, IMHO there’s a very large UX debt because of how many (powerful) features have been built. There’s a lot of simple UX wins that need to happen really bad. There’s also many features that, while VERY groundbreaking, are in my view only ~75% delivered. Huge props and admiration to the whole Fibery team to have the vision and chops to pull off the impossible.
But here’s the catch: adding on native mobile from web-only is a huge lift, requiring much more resources, and demands splitting focus. It’s not at all merely an ‘additive’ function, it’s an exponential increase in execution challenges and resources. This would be even more pronounced given the power (and complexity) of Fibery. That’s not to say Fibery isn’t positioned for this already or doesn’t have the resources - I have no info at all on that.
If Fibery goes native mobile right now/soon, it’s very likely that all the other feature requests - that I believe are crucial not only for usability and existing adoption but more importantly for accelerated growth and operating runway - all those other feature requests would most likely take longer. Maybe some folks here using Fibery more for light biz or personal usecases wouldn’t be impacted as much, but fwiw I’d far prefer to see other areas in the platform addressed first.
Just my 23 cents
For background, I’m a product leader in various tech projects/companies, some client work, some internal products. And even thought those are all heavy biz usecases, I’m hoping to also use Fibery for personal too, moving completely off of Notion (LOVE the Fibery “feed view” for that!).