Links

.appStore Context

Customize your .appStore
The context of a .appStore is defined by four parameters:
  1. 1.
    Registry: The set of .apps in your registry
  2. 2.
    Specific Metadata: .app metadata custom to your .appStore
  3. 3.
    Sections: Featured groups of .apps that you want to highlight.
  4. 4.
    Categories: Specific categories in your .appStore.

Registry

The Meroku registry boasts over 5,000 apps. As a .appStore operator, you may often wish to curate a specific selection of these .apps, creating a subset. There could be several reasons for doing this:
  1. 1.
    You may want to create a themed app store, showcasing only .apps that fit a particular category.
  2. 2.
    You might want to avoid offering similar services, as many providers often deliver comparable functionalities. You can opt to display only certain .apps in your .appStore to avoid this repetition.

Registry Context Strategy

To accomplish this, you will need to define the .app selection criteria, for which there are two strategies:
  1. 1.
    Whitelisting: This method involves specifying the .apps that you wish to include in your .appStore. Opt for this if you want to handpick .apps to display.
  2. 2.
    Blacklisting: Conversely, this method requires you to list .apps you wish to exclude from your .appStore. Select this approach if you prefer to omit certain .apps.
Once you have decided on your strategy, you can either;
  1. 1.
    Select the individual .apps from the drop-down list. You need to search for something for the list to appear.
OR
  1. 2.
    Populate a list of chosen .apps to the Meroku team in CSV format. The template can be downloaded from the UI.
You will need a storekey to use in making API requests. This will enable the APIs to serve within the context of your .appStore. The storekey is your .appStore ID. Example if your .appStore NFT name is myCool.appstore, your storekey will be mycool. This is case insensitive.
curl --request GET \
--url 'https://api.meroku.store/api/v1/dapp/search?search=nft&storeKey=app-store-key' \
--header 'Accept: application/json' \
--header 'apikey: YOUR_API_KEY'
Scroll down and click on "Publish" to save the data on chain.

Specific Metadata

As an .appStore, you can override certain metadata fields for .apps.
You can download the template CSV, and update it. Once you have the relevant CSV ready, upload it to this section. Note that any CSV uploaded will override any previous CSV information you have uploaded.
Scroll down and click on "Publish" to save the data on chain.
You can define as many featured sections as you want. Following are some examples of how app stores have been using sections.
Screenshot from unstoppablemarketplace.com showing a featured section
In order to define sections, you need to name the section and select the .apps for that section.
You will note the section key value corresponding to each section. This key should be used along with the featured sections API to get the section and its apps.
The "get featured section" call will return elements in the same order in which they were added. Sometimes, you would want to rearrange them. You can do this via UI. Once you have arranged them in the order you want, make sure to click on "Publish" to save this on chain.
Scroll down and click on "Publish" to save the data on chain.

Categories