Table of Contents

  1. Assets
  2. Metadata
  3. Dashboard Previews


Most importantly, you need to import your Zooper assets into the dashboard. I won't go into detail how these assets are generated, but your bitmaps, fonts, IconSets, and templates all go into their respective folder within /src/main/assets.


Next, you'll need to fill out meta data which Zooper will use to recognize your pack.

First, you need to comment out this intent filter in AndroidManifest.xml. This is how Zooper finds your pack initially.

At the bottom of that same file, uncomment the template provider. This is how Zooper will pull your template files out of the dashboard. MAKE SURE you change the authority to something unique. If you used the same authority as another pack, the packs would conflict with each other and only one would be able to be intalled at a time.

Lastly for meta data, you'll need to fill out information in /res/values/dev_zooper.xml. The comments should make what they do self-explanatory. It's recommended that you at least put your name in zooper_pack_desc.

Dashboard Previews

If you choose to do so, Polar can display previews of your Zooper widgets in a page within the dashboard. The key is the boolean enable_zooper_page in /res/values/dev_zooper.xml:

zooper_widget_names should contain a list of names which are displayed under each preview. The previews themselves are pulled directly from your template files in /assets/templates.

In order to make sure Polar renders your previews correctly, you will want Zooper to create previews with transparent backgrounds. Polar pulls the previews generated by Zooper right out of your .zw files.

Here's the general flow of how it's done, and what the result will look like in Polar:

The third image above features Bayside by Travis Hall.