Since this is primarily about mobile (with Offline as a component of that), there is already a pretty highly-voted request here: Native Apps (Apple, Android, etc.)
Perhaps this will get merged there? Or would you prefer separate discussion on some particular aspect?
I do find myself wondering if there would be some commonly agreeable set of minimum features that would meet the most basic, core needs of a majority of people and could help Fibery team focus on a more manageable implementation. Several other PKM apps I know have gone this route, starting with a simpler mobile app and potentially expanding later. Tana did, and I believe maybe Obsidian too. In both cases from my recollection it was more of a “capture-oriented” approach. For Fibery maybe the key things are some simple approach to “capturing” and “reference” (find and read info). What sacrifices could be made to facilitate this? Would they be useful removals of complexity that could make it easier for Fibery team to implement?
I know for example if I look at the current Fibery mobile UI there are probably 10 things I would just remove right-off (icons, functions, etc.; great example is the field manager!). Now I know the current mobile view is the way it is probably because it did not take a lot of work to just put “Fibery as it is now but formatted for mobile”, i.e. they did not have to deal with removing things. It’s just a reformatting of the existing web UI. But when reimplementing stuff in a native mobile app I suspect it might be the opposite problem, and having fewer things to add could be advantageous. And even if that’s not exactly the case, the design and UI/UX decisions and work needed to accommodate all existing functions are certainly burdensome and challenging. Mobile constraints often dictate some creative solutions and creating entirely new approaches to things that a desktop app doesn’t require at all. The less Fibery team needs to do that the better.
Anyway, just something to think about and perhaps discuss further. If those who want a mobile app can collectively decide on some reasonable subset of functionality that would make a “minimum viable” mobile app, that might move the initiative forward and allow it to move up Fibery’s internal priority list. Just keep in mind: it needs to be minimum viable! The absolute fewest functions it could have that would make it useful to you. 