Setting up your apps - for Pugpig Express

Before setting up your apps and submitting to the stores you will have been provided a login to Pugpig Express (a hosted, Pugpig enabled Wordpress instance) and will have gone through the process of creating and editing your content.

If you haven’t got that far yet, take a look at our Pugpig Express documentation, which gives you a complete overview of what you need to do to create, style and publish your content.

Once you are happy with your content and have tested your pages (using the Express preview tool) you are ready to get started with your Pugpig app containers.

The steps below detail the process and supporting documentation to set up your Pugpig apps.

You can look after the app setup yourself, or if it’s all sounding a lot like hard work, and you would rather we help, we have created a special Pugpig Starter Pack package priced at £2,000 to get you up and running (further information here).

So, for those keen to get stuck in...


Step 1. To kick off… please provide us with some further information

Please fill out your Pugpig Distribution document (provided by our sales team) marking cells green when they are complete. This gives us the information we need to:

  • configure the distribution service
  • theme your Pugpig apps

If you require design assistance with themeing for your application and/or templates and content we also offer Creative Services further info available here.

Step 2: Setting up your third party accounts

You will need to set up the following third party accounts if you don't have them already, some are optional but we recommend them all:

  • Apple iOS Developer account
    Sign up here - $99 a year
  • Android - Google Play and / or Amazon Developer Account (if applicable)
    Google sign up here - $25 a year / Amazon sign up here - free
  • Google Analytics - free
  • Push Notifications
    • As of February 2016 Parse has announced they will end their services so at the moment you can't create free Parse accounts. At the moment we recommend using Urban Airship (they have a free tier). If you wish to use Urban Airship please email and we can introduce you to their team for more information on features and pricing. We offer integrations with other Push Services but these are typically more expensive. In meantime we're looking at a low cost/free replacement to Parse and should have more details on this in March.
  • Quantcast Measure Data - free


Step 3. Setting up your third party authentication

Note: If you are offering your content free there is no third party authentication required and you can ignore Steps 3 and 4, update your Pugpig Distribution document with this intention and skip to Step 5. 

If you plan to offer paid content you can do so with in-app purchases through the app stores (explained in Step 4 below) and with a third party subscription service of your choice but we will need a bit more information about what service you use. Some are already supported on Pugpig, others may require some additional work. If you can provide a workable authentication API then we offer a Pugpig Authentication Pack priced at £3,500 (further info here). Please contact us with further information about your subscriptions service, i.e. custom built/third party provider and example test users.


Step 4. Setting up in-app purchases

Note: If you plan to offer all your content for free this step is not necessary, please skip to Step 5. 

If you plan to offer paid content in your app you will need app store purchases set up. These are usually referred to as ‘in-app purchases’. Set up can vary across iTunes, Google Play and Amazon stores but they follow the same fundamental concept; A user can buy a single issue or a auto-renewable subscription (from a set of supported durations) in your app via the store and their individual store account. The transaction is between the user and the store and you will get proceeds from the sales. Pricing is usually based on a tier model and Amazon and iTunes control the different territory pricing and conversions. Google Play do offer a price override option for territories however this is rarely used in practice and most customers opt for auto-conversion.

Before you complete this step you should read and complete Step 6 which involves setting up the app store listing (i.e. adding meta-data, categories, screenshots etc). For more information on in-app purchases read here, and for more info on setting up purchasing in iTunes here and Amazon here. More detailed step by step instructions are also available in the corresponding store documentation:

Note: None of the references to technical implementations of purchasing APIs are required, this is all handled for you in the Pugpig app container and testing for this is mentioned further down this page. At this step all you need to do is:

  • agree a naming convention for your in-app purchases
  • set them up in the different stores correctly and agree with someone in your organisation to manage this in future
  • share the detail of what you’ve set up with Kaldor in the Pugpig Distribution document - we need the subscription product IDs and durations and for single issues the prefix for your ID’s with one or two single issue examples that you’ll submit and launch with.

When you create editions ensure you set them up as ‘paid’ in your CMS, you need to make sure the Prefix and Key matches your store setup or the purchases will not work - explained in the ‘Create Edition’ post in our Express documentation here. You must keep ahead of your publishing timelines so you are never in a position where you publish a paid edition that hasn’t been set up in the store yet. We recommend batch setup for 6 months in advance of publication.


Step 5. Building your app containers

You can view our Pugpig for Magazines app design guide here and Pugpig for Continuous publishing here. These documents show all the app views and theme options available so should help you specify how you want the app to look.

Our team will provide you with an initial theme of your app for review. Included in our product support we will provide you with branded app containers for your required platforms, using your fonts, colours and logos. In addition to the first app container build we offer an additional two rounds of changes.

Any changes beyond this will be billed for on a time and materials basis. The allocated support should be sufficient to get the app ready for submission, assuming all guidelines below have been followed. In order to set up your app container we will need: 

  • A vector or high-res .png asset of your logo (or variations of logos)
  • A 1024 px square app icon
  • Any brand colour hex references and guidelines 

Optional design extras you may wish to provide include:

  • Background images - some of the native app views can support a background image as well as a flat colour. You can use this to add gradient or textures - *See some live apps for ideas*
  • Icon sets - we supply a default icon set on iOS and Android however if you prefer to use your own set of icons you can.

Please supply all assets via email or wetransfer. Please update the Pugpig Distribution Document with colour refs and detail on how assets were sent and when.


Step 6. Submitting your apps to the stores

Before you submit your apps you should carry out checks and tests, see Step 7 below for more information, however to get to the stage where your app is ready for testing you will need to complete the following set up for submission first: 

  • Confirm your Bundle ID and App Title - for bundle id we assume a convention like com.companyname.apptitle however if you have your own naming convention you can specify something different just ensure you add it to your Distribution Document so we know.
  • Sign your iOS & Android Builds  

If you already have an iOS developer account setup you may already have generated a private and public (.pem) key pair. To complete an iOS build for submission you need this key pair and to create:

  • development and distribution certificates (2 x .p12 files and passwords to use them)
  • development and production push certificates (2 x .p12 files and passwords to use them) named 'APNs Development iOS' and 'APNs Production iOS'
  • a development provisioning profile and two distribution (ad-hoc and app store) provisioning profiles (signed by the certificates above)

Further information can be found in Apple’s documentation here.

For Android it’s a little simpler, you just need to generate an Android keystore file more info here and here. 

  • App listing in store - along with the signed build your app listing will require you to add metadata like title, description, keywords, icons and screenshots of the app.
    • For Apple you set up the app listing in the iTunes Connect portal, further information here
    • For Google Play you use the developer portal, further information here 

We have some further detail about account setup and store submission on our Pugpig docs here


Step 7. Testing

It’s important you test your app container and content before submission to the app stores. Below is a list of areas testing should focus on:

  • Content - you need to submit with real content published, if edition-based we recommend a minimum of two editions. The content should look finished although the edition doesn’t have to be complete, as long as it illustrates the content you offer well. Apple will reject your app if there is obvious dummy or placeholder content. You should check content looks correct and scales nicely across different devices and orientations. Common issues around content include super large images which can make devices sluggish or even crash, snapshot issues if using javascript/custom code, use of custom fonts. Troubleshooting and info on how to resolve some of these issues can be found on Zendesk here. Be sure to check content with device offline as well. All the downloaded content should remain unchanged.

If you have specific issues you can contact - please include as much detail as you can along with links to the content and feed 

    • App Container - smoke test running your apps on a couple of devices and make sure it functions as you would expect. Test features like sharing, scrapbooking, buying, downloading, reading and archiving an edition. Buying an edition via the store requires some specific set up to be able to test - more info of Purchasing and Authorisation for Testing iTunes, Testing Amazon and Testing Google Play.
    • Double check you are happy with app icon, splash screens, theme and colours used, and all copy in the app (Settings, Accounts views etc). 
  • Third party providers: 
    • Google - check you are seeing data being sent to the correct account and key.
    • Quantcast - not easy to test until exceeds 100 users so this is one you should make a note to check once your app has been live and marketed for a few weeks.
    • Push notifications - test a message and background download push via your chosen provider - they should have detailed information in their own documentation on how to do this (Parse and UA).
    • Authentication - test logging in with an active subscriber code and then test you can successfully download and read a paid for edition, you should ideally test inactive and lapsed login states too and confirm you are happy with all the messaging around the signin including the ‘Need Help’ contact number and/or address is correct.

Step 8. Go Live

Once your app is approved the heavy lifting is done and you can go live. Like most things in life you’ll find that your Pugpig app functions best when updated and maintained. And with that in mind, we’ve put together a Pugpig Express support package priced at £300 per month or £3,000 for a year so you can rest assured we'll be around to help as and when you need us (further info available here).

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk