There are a few core details we need before we get started, so that we can make sure everything is set up correctly and efficiently.
We strongly recommend you use a domain you control for all customer facing content. It gives you more flexibility and control, and you look more professional. You don't want your customers seeing Pugpig in a domain name in their browser, a newsletter or social media post. We only support a single vanity domain for each app.
These are usually a subdomain, along the lines of app.publication.com or reader.publication.com, so require a CNAME change. In order to do this, you will need to change DNS records to point domains to the correct place.
☑️ Point the domain to our CDN
You'll need to point this domain to our Fastly CDN (pugpig.map.fastly.net) using your DNS provider. An example entry would be:
reader.publication.com 300 IN CNAME pugpig.map.fastly.net
You can find more detail in our vanity domains documentation.
App Store Information
App Store Connect
If you're not already signed up to Apple Developer / App Store Connect, you'll need to do this. The can be done on Apple's Developer website. There will be a yearly fee, payable directly to Apple.
☑️ Add us to App Store Connect
We ask that you add your Pugpig Customer Success Manager as an Admin user to your App Store Connect account, so that they can give App Manager or Developer access to our support engineers as and when they need access. We work so that any of our support engineers can pick up a project or ticket, to prevent any delays in the event of sickness or annual leave. If you prefer not to have your CSM as an Admin on your account, they can provide a list of users for you to add as App Managers.
Please add your support engineer onboarder as an App Manager with access to with access to “Certificates, Identifiers & Profiles”.
This process is completed in the Users and Access section within App Store Connect.
☑️ Confirm iOS app Bundle ID and version number
To ensure we use the correct details, and are updating the correct app if one already exists, please confirm the Bundle ID. For existing apps, this will be found in the App Information screen for the app in App Store Connect. Please also confirm your desired version number for the initial release - usually the next whole number.
☑️ Send .p12 and details for existing iOS app
To build and distribute a Pugpig update to your existing app, we require your development and distribution certificates, packaged in a P12 file. We have a guide if you need a hand.
Google Play Store
If you're not already signed up to Google Play, you'll need to do this. The can be done on the Google Play website. There will be a yearly fee, payable directly to Google.
☑️ Add Kaldor account to Google Play Console
☑️ Confirm Android Package ID and version number
The Android equivalent of the Bundle ID, the Package ID is found in the apps list in Google Play Console and also under the app name when you navigate to the App dashboard. Please also confirm your desired version number for the initial release - usually the next whole number.
☑️ Securely share keystore details for existing Android app
We recommend using Google Signing. Once this is set up, you will need to securely share the Upload Keystore. Details can be found here.
Amazon App Store
☑️ Add Kaldor account to Amazon Developer
The Amazon developer console is a bit more basic than the Apple or Google Play systems. If you add email@example.com as an admin user, we should have all the access we need to build, test and release your apps.
Firebase & GA
Pugpig comes with a tried and tested integration with Google Analytics, which is collected from the apps using the Firebase SDK, and from the web reader using standard GA tags.
☑️ Add us as a Firebase Admin
In the Users and permissions section of Project settings (the cog in the top left), add firstname.lastname@example.org as a Firebase Admin.
Firebase can also be used out of the box to handle crash reporting, as well as push notifications and in-app messaging.
☑️ Add us as a GA Admin
Under Admin > Property > User Management add email@example.com with Administrator access. More details about GA4 set-up can be found in this guide.
Brand Guidelines & Assets
Finally, to help us get the first version of your app together, we'll need a few things to make it look like the real deal.
☑️ App name
Please confirm how you want the app name to appear in the stores and on a user's home screen.
☑️ App icon
A 1024px square png - usually your logo on a background.
☑️ App logo
This will appear in the toolbar within the app. It should be a high resolution png, with a transparent background. The more landscape it is, the better.
☑️ Brand colours
At a minimum we can work from 3 main colours in a hexadecimal format (e.g #FF0000, #FFFFFF, #0000FF for a red, white and blue theme).
☑️ Brand fonts
You will need to send us the .ttf or .otf font file for your brand fonts. It is also helpful if you have a guide for how you want these used - header, main body, subtitles etc. Please also provide digital font licenses.
☑️ Android push icon
96px x 96px single colour and transparent .png format.