Overview

This document provides a step-by-step guide for setting up and delivering a Proof of Concept (POC) app. It explains how to create the required accounts, configure assets, set up the CMS, and prepare the app for testing. The goal is to provide a clear process that others can follow to replicate or continue the setup efficiently.

1. Distribution Account

Follow the process outlined in the distribution account setup document here.

2. Branding Assets

Clients may provide assets such as app icons, logos, and tab bar icons.

If not provided, install their current app from the store to reference branding.

Dom usually purchases a subscription, so you’ll be given login details ahead of time.

When creating placeholder icons/logos, use clean, simple designs (e.g., from Google) unless the client specifies otherwise.

3. Express Account

Create an Express account.

For POCs, we usually use the production Express instance.

Format: account-publication.express.pugpig.com.

4. Distribution Add-ons

Add-ons depend on the initial requirements Dom shares.

By default, you should enable the common distribution add-ons.

5. Express Add-ons

In most cases, required add-ons are now pre-activated.

To confirm, compare the setup with a previous POC instance to ensure nothing is missing.

Reference past POCs such as Buffalo, Nordjyske, and JF-Medier for guidance.

6. Store App IDs

Use the format: com.kaldorgroup.poc.(AppName).

iOS: Ask Nick/Matt in the #ios Slack channel to add the identifier.

Android: No need to request—debug builds can be used.

Debug password: android

7. App Tabbar setup

Dom will usually provide an Excel file listing the agreed tab bar items and timelines.

If not available, take inspiration from the client’s site.

Follow Dom’s guidance for setup where applicable.

8. App Theming

Base theming on the client’s current app where possible.

For clean starting points, review past POCs such as Buffalo, Nordjyske, and JF-Medier.

Aim for a simple, clean look that FE (Front-end) can build on.

9. Content Integration

Clients may not always provide RSS feeds during POCs.

If not, manually upload content to Express:

Pull 30–50 articles from their site across different sections.

Ensure collection tags, sections, and contributors are included.

This is especially important if the “follow” feature is requested later, as it avoids duplicate work.

10. Creating the Config/Build

Once setup is complete and content is in place, create the configuration.

Deploy the following versions: Bolt Search, Smart Banner, Bolt Timeline, and Bolt Reader.

Create and upload an iOS build to TestFlight (ensure external TF is enabled).

Create a debug build for Android.

Create a simulator build if required.

11. FE Ready

Once you’re satisfied that the app base and content are in place, tag Dom.

At this point, the app will be resourced for front-end development.

That's it! 🤗