From IndieWeb

A store (or marketplace) is a service for discovering and then installing applications. Applications can reside on a mobile device, a local device or a remotely hosted web server.

Examples of application installation locations are

  • mobile device - your phone for example
  • a local device - IndieBox
  • a remote web server - applications installed via yumm or apt-get
  • a hosted web service - Dreamhost


As the number of IndieWeb related apps grow, so will the job of choosing which apps you want to install and what is compatible with your server. The goal is to create an easy to browse "App Store" like experience for an indieweb site, both for installing apps on that site, and for publishing app stores themselves on indieweb sites.

App Store Examples


There are proprietary client app stores for installing proprietary clients:

Open source app stores:

And open or curated web based app stores for discovering and installing web apps:

These stores enable mobile devices to install client-side proprietary apps that usually upload data to remote web services or [silos].


In its first many iterations and use cases The Indie App Store will likely not be installing "native" apps on a mobile device, but rather server-side apps on a cloud server, laptop, Raspberry Pi, or personal computer. The goal is to make the setup process as easy as modern client-side app stores. Current examples:

  • Cloudstore, operated by Johannes Ernst already does this for user-owned, or shared virtual servers. It is currently in beta, but registration is open to the public.

App Store Specifications

W3C Manifest for web application

The W3C Manifest for web application is in actively open development. It supersedes "Open Web App Manifest".

Open Web App Manifest

Open Web App Manifest is implemented in:

  • Firefox OS 1.0-1.1 (to present)


The goal of making an open data format that is shareable from app store to App Store has multiple advantages, the benefits of doing so will differ depending on what type of person is interacting with this data and in what way. The three types of entities in the app eco system to benefit from this will be stores, developers, and users.

App Stores (Platforms)

It will require much less work gathering & organizing information (media assets) of the various apps they allow to be installed on their platform. Should a given platforms app store reach scale beyond 50 or so apps, they won't need to create an entire new platform or CMS that allows developers to easily submit their app. This is especially if much of the app store code itself is open source, and perhaps static HTML, CSS, JS interface that is served to the end user.

App Developers

To app developers, this is helpful because, they won't need to waste time creating multiple sets of logos, assets, different length summaries, screenshots, etc... in order to submit apps to multiple platforms / app stores. The developer creates one JSON manifest file or a microformats marked up HTML page that multiple platforms then consume to generate their app stores.

App Users

The end user will benefit from a more seamless user experience from device to device or platform to platform where the marketing media and app information will more likely be identical and up to date.

Key Features

There are numerous aspects that make app stores the most successful method of software distribution to come along, this section provides a list of the functionality that we should aim to incorporate into the Indie App Store.

Rating & Feedback

Most app stores have a method of rating apps & leaving comments that are publicly viewable. This user feedback is essential to the health of an app store and the larger software eco system as it provides app developers with feedback to improve their software, and enables users to make the best choice they can when installing software.

Free and Paid Downloads

Despite the Indie App Store being aimed at primarily Free & open source software, it is not impossible to envision people wanting to sell apps that the end user must purchase. Creating methods of securing software purchases (licensing, install keys, etc...) are out of scope of this project, it is worth exploring integration of simple "fixed" or "pay what you want" payment methods that pay money directly to developers or platform providers.

Updating Apps

The updating of apps for the end user is via a single interface is a considerably better user experience than browsing to each individual app and clicking update. Additionally, by moving this aspect of software distribution to an Indie App store would remove much work from developers of apps.

This is also an aspect of the IndieWeb that can really shine- by allowing updates of app data to be polled from a project (apps) website whereby the data is marked up in [microformats]. This way the data does not have to be manually passed around and will always be up to date.


In following the UNIX philosophy of "have one small application / component do one thing really well, it might make sense to explore the idea of bundles which are something that would allow multiple "apps" to be installed together, such as [Bridgy] + [Idno] which allow for a more robust POSSE / PESSO / Webmention integration. Of course this would be tricky and require apps to use similar data exchange standards, but consider how UNIX system write email to disk and multiple apps can then access it later!


Quite common in existing app eco systems are Accessories things like themes, plugins, add-ons or in app purchases. Often app developers need to create their own miniature theme or plugin store within their app to facilitate this process.

Perhaps some of this process can be handled by Indie App Store by using a standardized manifest & install process similar to the main app installer.


It would be a greater good for the user of such a store to have access to a one click migration feature. This would allow the user to be free from the store and/or from the web Hosting provider.


To make progress on the store concept, there are three crucial aspects, Apps (projects, that will be listed in the store), Platforms (that support installing of said Apps), and the App Store codebase itself that needs to be developed and iterated upon.


The following apps / projects have expressed interest in creating data in the shared format for this purpose


The following platforms have voiced an interested in working towards a shared app data format & perhaps installer store experience.

Development Stages

Developing the Indie App Store will undoubtedly be a long and challenging process involving outreach to existing projects, development of new software (installer clients), and many parties working towards a unified standard of data. It makes most sense to iterate on this incrementally through the following steps:

  • App Download & Install instructions for humans
  • App Download & Install instructions for machines
  • Tools that enable machines to processes these instructions and install apps
  • Expand upon these tools from platform to platform (Raspberry Pi, Ubuntu, smart phones, etc...)
  • Develop original "installer" clients for different operating systems

Store, Requirements & Instructions

It seems there are 3 discreet aspects of app information that are needed for the entire install chain process of displaying and installing apps from an app store, the Store, Requirement, and Instructions for a given platform.

1. Store - info (name, logo, description, screenshots, website) that is visible in the GUI to the end user

2. Requirements - and other technical things that a platform consumes to determine if it can do something with said app

3. Instructions - this is the technical instruction set that a give platform consumes, this is unique from platform to platform (IndieBox, ArkOS, MacOS, Jolla phone, etc...). Some of these platforms already have app stores of their own, some more walled & closed than others.

The following are values that an App Store SHOULD have discoverable or recorded in the apps manifest.

  • Name
  • Logo
  • Screenshots
  • URL
  • Short Summary
  • Summary
  • Content
  • Categories
  • Version
  • Cost
  • Developers
  • Platforms
  • Protocols
  • Code Language
  • Dependencies


Vocabularies related to describing a Web App:

  • h-product - microformat
  • DOAP - "Description of a Project"
    • Looking at that git repo I cannot find simple examples, list of properties, or examples in the wild --Barnaby Walters 08:41, 11 June 2014 (PDT)
      • see
      • list of properties: - all the rdf:about names.
        • anon-root
        • ArchRepository
        • ArchRepository
        • audience
        • BazaarBranch
        • BKRepository
        • BKRepository
        • blog
        • browse
        • bug-database
        • category
        • created
        • CVSRepository
        • CVSRepository
        • DarcsRepository
        • description
        • developer
        • documenter
        • download-mirror
        • download-page
        • file-release
        • GitRepository
        • helper
        • HgRepository
        • homepage
        • implements
        • language
        • license
        • location
        • mailing-list
        • maintainer
        • module
        • name
        • old-homepage
        • os
        • platform
        • programming-language
        • Project
        • release
        • repository
        • Repository
        • revision
        • screenshots
        • service-endpoint
        • shortdesc
        • Specification
        • SVNRepository
        • tester
        • translator
        • vendor
        • Version
        • wiki
    • examples in the wild:


The following are examples of some of these install manifest files by various projects creating these sort app store / installer experiences on user controlled hardware.


The w3c and Google agreed on the following manifest standard which we will adhere to for all the values that exist.

  "name": "Super Racer 2000",
  "icons": [{
        "src": "icon/lowres",
        "sizes": "64x64",
        "type": "image/webp"
      }, {
        "src": "icon/hd_small",
        "sizes": "64x64"
      }, {
        "src": "icon/hd_hi",
        "sizes": "128x128",
        "density": "2"
  "start_url": "/start.html",
  "display": "fullscreen",
  "orientation": "landscape"

There is also the competing FireFox OS manifest which is oddly a bit different than the w3c standard. It is worth noting the FF OS manifest has a lot of documentation for various other features like language support. Hopefully this will get adopted by the w3c.

  "name": "My App",
  "description": "My elevator pitch goes here",
  "launch_path": "/index.html",
  "icons": {
    "128": "/img/icon-128.png"
  "developer": {
    "name": "Your name or organization",
    "url": ""
  "default_locale": "en"

Since both the FireFox OS and w3c manifests are missing things that a "store" like experience demands, as well as server side dependencies and licenses. Indie App store will forge on and add additional values as needed, then hopefully this can be adopted by the w3c at a later date!

PrismBreak - [1] is an open source directory of open source applications geared towards privacy, encryption. The following JSON snippet is how they render their static HTML site, it was a lose starting point for the app manifest idea that is becoming the store concept. This is very much Store data.

    "description": "A modern, fast web-mail client with user-friendly encryption and privacy features",
    "license_url": "",
    "logo": "mailpile.png",
    "notes": "",
    "privacy_url": "",
    "source_url": "",
    "name": "Mailpile",
    "tos_url": "",
    "url": "",
    "wikipedia_url": "",
    "protocols": [
    "categories": [
        "name": "BSD",
        "subcategories": [
          "Email Clients"
        "name": "GNU/Linux",
        "subcategories": [
          "Email Clients"
        "name": "OS X",
        "subcategories": [
          "Email Clients"
        "name": "Windows",
        "subcategories": [
          "Email Clients"
    "slug": "mailpile"

OUYA store

Example of

    "app": {
        "uuid": "ae95483b-2421-4706-bffe-1903376362b2",
        "title": "Acid Trip",
        "supportEmailAddress": "",
        "supportPhone": null,
        "website": "",
        "mainImageFullUrl": "https:\/\/\/apps\/08c0336f-7792-47ae-885d-cff339631f15\/com.SmithereensGames.AcidTrip\/ae95483b-2421-4706-bffe-1903376362b2\/ouya_icon.png",
        "founder": true,
        "apkFileSize": 43262213,
        "firstPublishedAt": "2013-07-31T14:10:33Z",
        "publishedAt": "2013-08-12T17:43:29Z",
        "versionNumber": "1.1",
        "likeCount": 143,
        "overview": "Released in August 2013 by Smithereens Games.",
        "filepickerScreenshots": [
        "contentRating": "Everyone",
        "latestVersion": "ae95483b-2421-4706-bffe-1903376362b2",
        "md5sum": null,
        "publicSize": null,
        "nativeSize": null,
        "ratingAverage": 3.6,
        "ratingCount": 262,
        "developer": "Smithereens Games",
        "description": "Acid Trip is an intense ride through a twisting and turning colorful tube. Challenge your friends and family to see who can get the highest score possible. Your speed slowly increases throughout playing, do your best to get the highest score possible.",
        "premium": false,
        "videoUrl": null,
        "promotedProduct": null,
        "primaryProduct": null


Here is an example of the current plugin metadata structure that arkOS is using as taken from their github repo

# Plugin metadata
NAME = 'WordPress'
TYPE = 'webapp'
ICON = 'gen-earth'
DESCRIPTION = 'Open-source CMS and blogging platform'
LONG_DESCRIPTION = ('WordPress started as just a blogging system, '
    'but has evolved to be used as full content management system '
    'and so much more through the thousands of plugins, widgets, '
    'and themes, WordPress is limited only by your imagination. '
    '(And tech chops.)')
        "primary": "Websites",
        "secondary": ["Blogs", "Websites", "CMS"]
VERSION = '3.8.1-1'

AUTHOR = 'arkOS'
APP_AUTHOR = "Automattic"
LOGO = True

        "name": "MariaDB",
        "binary": "mysqld",
        "ports": []
        "name": "PHP FastCGI",
        "binary": "php-fpm",
        "ports": []

# Plugin parameters
MODULES = ['main']
PLATFORMS = ['any']
    "any": [
            "type": "app",
            "name": "MariaDB",
            "package": "mariadb",
            "binary": "mysqld"
            "type": "app",
            "name": "nginx",
            "package": "nginx",
            "binary": "nginx"
            "type": "app",
            "name": "php",
            "package": "php",
            "binary": None
            "type": "app",
            "name": "PHP FastCGI",
            "package": "php-fpm",
            "binary": "php-fpm"
            "type": "app",
            "name": "PHP xCache",
            "package": "php-xcache",
            "binary": None
            "type": "plugin",
            "name": "MariaDB",
            "package": "db-mariadb"
            "type": "plugin",
            "name": "PHP",
            "package": "php"

# Webapp metadata
WA_PLUGIN = 'WordPress'
DPATH = ''
PHP = True
SSL = True


The Indie Box Project aims to make an easy to install great Free software / Indie applications on a user owned piece of hardware. They have a package for installing [Nextcloud] on on a Raspbery Pi. The full instruction set is in the ubos-manifest.json.

Interface Guidelines

Platform creators will most likely want the App Store experience of installing things to be as branded and cohesive to the rest of their user experience as possible- this only makes sense, and is in fact a better user experience.

That said, creating a serious of user flows and interface guidelines seems helpful as to this end goal, once a user learns the flows and processes (which are modeled after Apple's iOS & Google's Play app stores) users will be easily able to perform the action they are trying to.

Indie App Store Index


Random assorted ideas that could be used for different aspects of the Store idea.

See Also