From kde-community  Wed Jan 10 18:12:03 2024
From: Volker Krause <vkrause () kde ! org>
Date: Wed, 10 Jan 2024 18:12:03 +0000
To: kde-community
Subject: Re: Why (some) KDE software are not available in Android stores?
Message-Id: <4890807.31r3eYUQgx () vkpc5>
X-MARC-Message: https://marc.info/?l=kde-community&m=170491029416538
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart4540013.LvFx2qVVIh"

--nextPart4540013.LvFx2qVVIh
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; protected-headers="v1"
From: Volker Krause <vkrause@kde.org>
To: kde-community@kde.org
Date: Wed, 10 Jan 2024 19:12:03 +0100
Message-ID: <4890807.31r3eYUQgx@vkpc5>
Organization: KDE
In-Reply-To: <3206215.5fSG56mABF@daneel>
MIME-Version: 1.0

On Mittwoch, 10. Januar 2024 15:44:27 CET Ingo Kl=F6cker wrote:
> On Mittwoch, 10. Januar 2024 15:22:50 CET Filipe Saraiva wrote:
> > Just a doubt, KDE has several interesting mobile software which support
> > Android but they are not available in Android stores, like Neochat,
> > Tokodon, Alligator, Kasts, etc.
>=20
> Those apps are available in our F-Droid "stores":
> https://community.kde.org/Android/F-Droid
>=20
> But I guess you mean the Google store (and maybe other proprietary Android
> stores).
>=20
> > Why? Is that some technical reason related to our stack, person-power
> > hour to work in provide these releases, or other thing?
>=20
> The lack of person-power is the most important reason. The technical proc=
ess
> is pretty straightforward nowadays, but someone needs to check if the apps
> comply with the store policies.
>=20
> No. Wait. For new apps there's also a technical reason. For new apps Goog=
le
> Play requires application bundles (AAB) instead of APKs. We can build AAB
> (at least for Qt 5) on invent, but we cannot sign them yet. Shouldn't be =
to
> hard to add given that it's mostly identical to APK signing. I'm going to
> work on this once signing of Windows binaries is done.

Related to that: we probably want to use a new key for the AAB signing, as =
we=20
have to hand that one out to Google when publishing AABs to their store AFA=
IU?

Regards,
Volker
--nextPart4540013.LvFx2qVVIh
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQQAnu3FVHA48KjZ07R/lszWTRLSRwUCZZ7d8wAKCRB/lszWTRLS
R1SZAJ9ytZO/Hxp1FQD5p+A4jc5770QG9QCcCegZl1WnUgOMXe3My2hpNTXQJCo=
=S5Sy
-----END PGP SIGNATURE-----

--nextPart4540013.LvFx2qVVIh--