Recent searches
Search options
So, how would I go about packaging something for use on Linux phones? (@linmob, @postmarketOS). Flatpak on flathub?
@zerodogg that depends on the target. Flatpak is surely the popular choice for convergent apps lately (and most of us use apps from Flathub on Linux phones), but not the lightest if it's more like a small utility
@tuxdevices It's rather small, but it's written in dart and uses flutter (initial target was Android, with iOS and now Linux proper added later) so it has some heavy build dependencies.
@zerodogg I would go for flathub for simplicity and reach to many distros (apart from some annoyances in the packaging it's fairly well documented), did you test if Flutter apps work on ARM Linux though?
@tuxdevices Haven't tested it myself, and don't have any ARM device, but the SDK has prebuilt tarballs for x86_64 and ARM so I would guess it does (and there are flutter apps on flathub with arm-builds).
@zerodogg @tuxdevices Flutter works just fine on Linux ARM, no issues there. Flutter is a pain to package though, so almost no distribution has it available for apps.
You can package it natively for pmOS/Alpine though (we have some Flutter apps already), and I would definitely recommend Flathub yes, no matter how small.
@bart @tuxdevices Not that worried about distros if I can get it on flathub. Don't want to maintain more packages than necessary.
@bart Are there any guidelines on how it should behave? Ie. should it maximize itself on phones?
@zerodogg No, that's up to the DE's/compositors to decide. It should just be a responsive application, the same as on Android and iOS. Nothing extra should be done for mobile specifically.
@bart Right. Since it's a windowed thing on Linux though, I need to provide a default window size (which is basically just a sort-of portrait-phone size), but the compositor can just override that.
@zerodogg I've never given a Flutter application a default window size 
It just let's the compositor decide a default size. On desktop that's something like a 800x600 window, on mobile that would be a maximized window adjusted to whatever the resolution of the screen is.
@bart 800x600 was hardcoded into the *.cc that flutter generated, so I edited that, since 800x600 looks pretty bad for this app right now, it’s made for phones, with only some minimal adaptations for tablets. Was actually kind of surprised flutter didn’t expose *any* windowing APIs, had to implement a MethodChannel for localizing the window name.
Anyway, thanks for the hints. I’ll get to digging into how to get the thing on flathub once this release is ready.
@zerodogg Ah that makes sense. Still, a compositor will force it down to whatever is available. I personally don't think applications should manage their own window size anyway.
@bart Aye, I agree. Was just uncertain about the conventions :).