Turn Your Device Into an App Store

As we’ve touched upon in previous blog postsĀ  the Google Play model of application distribution has some disadvantages. Google does not make the Play store universally available, instead limiting availability to a subset of countries. Using the Play store to install apps necessitates both sharing personal information with Google and enabling Google to remotely remove apps from your device (colloquially referred to as having a ‘kill switch’). Using the Play store also requires a functional data connection (wifi or otherwise) to allow apps to be downloaded. Often there is a need to quickly bootstrap users during training sessions in countries with unreliable/restricted data connectivity, or in extreme cases, no internet connectivity at all.

F-Droid addresses many of these concerns, but still requires a functional data connection in order to access the repository housing applications available for install. Wouldn’t it be great if there was an easy way for users to share applications amongst themselves, in absence of a reliable data connection? Today we would like to announce initial steps the Guardian Project is taking to enable this exact functionality. We’ve been working on a prototype application capable of building F-Droid repositories on-device, allowing users to share apps they already have installed to other users through F-Droid. In this way savvy users can quickly and securely share applications they already know and trust with friends and family without requiring a central market/repository or a reliable internet connection.

To start, we’ve built a stand-alone prototype application we call “Kerplapp” (as in Kerplop for Apps). Using Kerplapp an established user can select applications already installed on their phone that they wish to make available to other users. Using the selected applications Kerplapp builds a simple binary F-Droid repostiory on the user’s device. The local on-device repository is then made available over a WiFi connection to other users on the local area network. Kerplapp will even display a QR code with the information required to add the local Kerplapp repo as a source repository for an F-Droid client running on another device. We hope to eventually merge our work back into the official F-droid Android client, but while we work out the kinks the Kerplapp application operates side-by-side with the F-Droid client app.

Sharing access to a Kerplapp repo with a QR code.

Sharing access to a Kerplapp repo with a QR code.

Building on top of F-Droid has a number of advantages. First, we can directly benefit from the tremendous effort and success of the F-Droid project! We’ve been actively contributing improvements back to both the F-droid client and the F-droid server, making it easier for everyone to set up new F-Droid repos and share connection details. Secondly, by using a binary F-Droid repository we can ensure that when users share apps between each other that the apps will continue to receive updates through other channels. That is, if I share an app with you through Kerplapp you will be able to install updates to the app from other F-Droid binary repos and other Kerplapp users – wherever the app and its updates are available with the same APK signature. The F-Droid client will do the hard work of determining what updates are available and compatible with your device

There’s a lot of work left to be done! One of our short term goals include enabling Bonjour support so that the F-Droid client can find repositories on the local network without requiring them to be added manually. We’re interested in supporting device to device app transfer over a number of channels, starting with HTTPS and eventually adding support for bluetooth and NFC. Building on the success of ChatSecure we’re actively working on supporting F-Droid app transfer over OTR-Data, the ChatSecure proposal for in-band OTR encrypted file transfers. With F-Droid as an OTR-DATA endpoint we can support peer to peer app transfer over a trusted, authenticated, and encrypted channel. We’re also exploring how we can use the OTR keys your contacts already trust to sign the F-Droid repository metadata index, providing greater trust in the accuracy of the metadata provided by peer to peer repositories.

If you’re curious you can follow Kerplapp’s development on our project tracker. We’re also looking for adventurous users to install the Kerplapp prototype application to provide feedback and testing.

4 comments for “Turn Your Device Into an App Store

  1. daithib8
    2013/12/05 at 12:05 pm

    If you’re struggling with jmdns maybe this topic will help: http://code.google.com/p/clementine-remote-android/issues/detail?id=28. Long story short: the latest version is ropey, the version on sourceforge has a different layout and a wrong build.xml, it needs to be used as a jar and the jar needs to be repacked.

    • n8fr8
      2013/12/10 at 3:09 pm

      Thanks for the pointer!

  2. Hans-Christoph Steiner
    2014/08/06 at 11:46 am

    FDroid 0.71 was just released, it is the first stable version that includes these features: https://f-droid.org/repo/org.fdroid.fdroid_710.apk

  3. theom
    2014/10/28 at 6:51 am

    Is there anny possibility to run the fdroidserver on the device as https and where can I finde the repo on the devices filesystem?
    I addet somme aplication to try out the feature, but sommetimes new apps are not addet, or deletet from the list, when I changed the settings in fdroid. Also the url is changing sommetimes…

Leave a Reply to Hans-Christoph Steiner Cancel reply

Your email address will not be published. Required fields are marked *