I don't think that's a platform or software problem but rather an issue where the feature-to-bug ratio isn't worth it.
I'm not saying that Firefox for Android is perfect or that no further development is needed, but using the desktop version of Firefox to guide the development of the Android version is a waste. It needs better feature integration with the platform rather than a 1:1 copy of its desktop variant.
The software you are suggesting are in my honest opinion not worth the squeeze. it's like asking Bicycle with engine and complaining about it not being efficient as the motorbike. Just use the bike while making bicycle better in it's own way.
I was talking about the community extension integration, now about editors, I was easily able to switch between them. The one I was having the most difficulty with was Logseq."
Nope, Documentation + LLM misses the big chunk what we call human errors, commonly x y problems, LLM are good until you need to get deep then they start giving surface level answer it's possible to point them toward the right direction by refining but at that point i would prefer reading Documentation.
I don't think that's a platform or software problem but rather an issue where the feature-to-bug ratio isn't worth it.
I'm not saying that Firefox for Android is perfect or that no further development is needed, but using the desktop version of Firefox to guide the development of the Android version is a waste. It needs better feature integration with the platform rather than a 1:1 copy of its desktop variant.
The software you are suggesting are in my honest opinion not worth the squeeze. it's like asking Bicycle with engine and complaining about it not being efficient as the motorbike. Just use the bike while making bicycle better in it's own way.