We know that our customers spend a lot of time innovating, trying new things and exploring how they can better engage and serve their audiences. One of our goals with Pugpig Bolt has always been to allow you to bring those ideas to your app audience in way that's both easy and powerful.

Naturally, a lot of these endeavours currently manifest themselves in the form of AI-powered experiences such as chatbots or reimagined ways of searching. Getting these in front of your most highly-engaged audiences is critical both in terms of validating their impact and leveraging that impact to better serve your users. 

Where can they live?

Pugpig Bolt is well-placed to bring these experiences to the fore. At their core almost all of them take the physical form of a webpage. We support hosting nigh-any webview as a custom tab, which can appear on the app's tab bar (ideal for high-impact, oft-used destinations) or hidden tabs linked to from elsewhere (better for contextual use cases or secondary functionality). For that all we'd need is the URL of the page and where you'd want it to live. This should then function just as it does elsewhere. 

We find that, in these cases, HTML solutions are much better than writing native code. As said, these are often (but of course don't have to be) experiences you're using on other platforms so embedding your existing work means you only have to build it once, and are free to iterate on it as much as you wish. Secondly, most of the work and investment here usually lies in what's happening behind the scenes, so providing a fast way for you to get into your users hands means you can continue to focus on what matters. 

Optimisation

If these pages are part of your website or other property you might want to optimise how they appear in the app, for example by hiding headers and footers that would look duplicative or otherwise out of place in the app. This can be achieved through a query string on the page URL which your team can use to serve the optimised UI. 

Authentication

We also know that these experiences are often locked-down to subscribers only. We support this in all webview tabs by passing the user token into the webview, meaning the authentication implementation you have on that page should be able to pick it up and grant or deny access as necessary using your existing mechanisms and UI.

More information about the capabilities of webview tabs, including analytics can be found in the dedicated documentation for that feature.

If you're unsure whether a given experience will work in your app, how it can be tailored to do so or just want to share some ideas, please get in touch with your CSM or email support@pugpig.com. We'd love to help.