Skip to main content

Submitting A New Package Or Update

  • Updated

First off, you need to be a seller on Packix to do this - if you are not yet a seller, read here.

Submitting A New Package:

  1. Go to https://developer.packix.com/#/developer/packages
  2. Click Screenshot_2020-08-26_at_09.14.10_2x.png and upload your .deb file 
  3. Give your package a title
  4. Write a short description
  5. Add the minimum and maximum iOS version support. 
  6. Add a package icon
  7. Add a detailed description for the package. See here for some tips on how to write a good description.
  8. Add screenshots of the package - for themes, please show a variety of icons.
  9. If you plan on making this a free package, you are done. If you plan on making this a paid package, read below.

Once all the above is done, you have the option of making the package Free or Paid. 

  • To set a price, click NEW next to the "Download Restrictions" section.
  • Then choose the "Plus" payment model
  • Next, set your price. It needs to be a $0.50 USD minimum. Be sure not to set a ridiculous price as you won't get many sales that way.  
  • Press Save

Other Restrictions you can add:

  • Cydia store package ID
  • Previous purchase - This means that if a customer bought X package, then they can download this package for free.
  • Patreon tiers

Additionally, you can add discounts for previous purchases and Patreon tiers in the form of:

  • Percent based
  • Amount off original price
  • Override price

Submitting An Update:

  1. Go to https://developer.packix.com/#/developer/packages
  2. Click Screenshot_2020-08-26_at_09.14.10_2x.png and upload your .deb file
    • NOTE: IN ORDER FOR THE SYSTEM TO KNOW IT'S AN UPDATE, IT NEEDS THE SAME IDENTIFIER
  3. Add a changelog - DO NOT PUT IT IN THE DEPICTION. Go to: Versions --> Find your update --> Edit --> Add your changes, 1 per line --> Press Save

Approval Process: 

Once you submit the package, it goes to Packix Admins to review. 

You can see the approval status of your package by clicking the "versions" tab

mceclip1.png

For new packages, once the package is approved you will need to manually make it "go live."

For updates, once it's approved, it automatically goes live. 

 

If a package is declined, you will see the status says Denied and you can click on the Screenshot_2020-08-26_at_09.53.07_2x.png to see the decline reason. 

mceclip2.png

There are a variety of reasons for why your package may be removed, some examples:

  • Low-quality packages - Packages that don't look visually appealing or are very small feature-wise.
  • Low-effort packages - Packages that look like not much time was spent creating it.
  • Piracy - Either your package enables piracy or we suspect that elements of the package were stolen from another developer/designer.
  • Bad version number - If your package version has "debug" in it, we will automatically decline it.
  • No change log - If there is no changelog submitted for an update, after a few hours we will decline the update.
  • For themes - new packages need a minimum of 100 icons and each update needs a minimum of 15 icons. 
  • No description or screenshots - All packages need to have a description and most* packages need screenshots. (*The exception to that being developer tools/libraries and tweaks where it's functionality is not possible to show in a screenshot.)  

Related articles