@LucyWildboots 🏳️‍🌈 @clacke post fosdem 🇸🇪🇭🇰💙💛 @Chris Trottier @Kevin Davidson @Sarah Brown @IceCubesApp @Mona app I'm not sure if it's wise to give mobile apps for the #Fediverse direct access to all features of all Fediverse projects.

At first glance, it sounds convenient. You install one app, and you can do everything with it on every project.

But imagine some poor sap who has just migrated from Twitter to Mastodon, who loads a Fediverse app from the app store, and who ends up with an outright monster of an app with a UI cluttered with greyed-out options and menu items.

Why is it so cluttered? Because the devs also included full #Hubzilla support. And I mean full support for all features of Hubzilla channels with all apps activated, including full access to all account and channel options and settings, including a post editor with buttons for the whole extent of Hubzilla's bored-up #BBcode implementation, including article, webpage and wiki page editors (which partly support #Markdown and #HTML on top of BBcode), including connecting your phone to the #WebDAV, #CalDAV and #CardDAV servers included in your channel, including even support for creating and managing nomadic clones.

And Hubzilla is something that's even cumbersome to handle in a desktop browser. Now imagine all this packed into a mobile app.

Such an all-in-one app would also confuse people to have access to multiple separate calendar systems through the app. One is a public calendar as available on #Friendica, Hubzilla and #Streams. The second one is a CalDAV-equipped engine for private calendars which Hubzilla has in addition to the public calendar, and which in itself supports multiple calendars, not to mention calendars on other channels which gave you write access. The third one is a collaborative calendar as offered by #Mobilizon.

Oh, and it'd of course support #OwnCast as well as the live stream feature included in #PeerTube to the point of enabling you to live-stream through one of these projects how you use the self-same app to handle another Fediverse project.

Last but not least, every update on every Fediverse project that comes with new or changed features will require an upgrade for the app.

@Kevin Davidson @aethervision :ziltoid: @Fediverse News I think if someone made a mobile app for #Hubzilla alone that harnesses its full power and grants access to its entire set of features, maybe minus hub administration, it'd be so bloated that you'd wish for an external 30" touch screen for your phone.

That said, I'm not even sure if it'd make sense to include all of Hubzilla's features, even those that are optional apps per channel, in one mobile app. You wouldn't want to write a blog-like article with embedded pictures with your two thumbs on the 6" touch screen of a hand-held device, much less a bunch of interconnected wiki pages. This also makes mobile apps for blogging on #Plume or #WriteFreely questionable. (Then again, people might have Bluetooth keyboards.)

Now imagine squeezing the feature sets of all other #Fediverse apps into the same app. I mean, the UI would have to change, according to whichever project you're using. And you can't operate all your logins on all projects you use from the same surface. The various calendars with different functionality which will be displayed when logged into Hubzilla and #Mobilizon at the same time may be confusing.

In fact, you'll have to be able to switch between logins. Having four Mastodon logins laid out on the same screen already requires a curved ultra-wide desktop screen. Now imagine being "able" to operate four Hubzilla channels on the same account on a 6" smartphone.

Besides, one central Fediverse app would have to catch up with both innovations on existing projects and newly-launched projects.