Keep Your App Up to Date
Easily manage app updates, new features and improvements – with minimal disruption for your visitors.
- Dynamic Content Refresh
- Managed Release Workflow
- Minimal Visitor Disruption
- Seamless Updates
- New Features
- Minimal Disruption
- Better Experiences
A simple path from feature update to instant visitor delivery
Prepare, deploy, and notify your visitors about new features in 3 simple steps.
- Step 1
Prepare
Test and prepare updates using administrative tools
- Step 2
Deploy
Release to app stores or via instant dynamic app updates
- Step 3
Notify
Keep users informed of what’s new with release highlights
Everything you need to keep your venue app fresh and reliable
Compact, powerful feature capabilities designed for real venue needs.
Version Management
Track releases, manage software builds, and maintain platform stability.
App Store Support
Seamless publishing and release management for iOS and Android app stores.
In-App Updates
Deliver real-time content, event, and exhibit changes without full app re-installs.
Release Notes
Communicate new capabilities, exhibit additions, and improvements clearly to guests.
Why venues choose Pigeon Suite App Updates
A simple journey. A better day for every visitor.
Keeps Your App Current
Ensure visitors always experience the latest venue content and feature enhancements.
Adds New Capabilities
Roll out seasonal interactive trails, new exhibits, and capabilities smoothly.
Improves Performance
Optimize speed, fix minor issues, and maintain OS compatibility over time.
Enhances Visitor Satisfaction
Deliver seamless, bug-free, and delightful experiences on every visit.
Related features
Frequently asked questions
What are app updates in a visitor experience platform?
App updates include the processes used to keep visitor-facing content, configuration, and software current. Some changes can be delivered dynamically through the platform, while changes to native application code may require a new app-store release.
What can be updated without an app-store release?
Supported dynamic content and configuration can often be updated through the platform without publishing a new native binary. Examples may include descriptions, images, events, schedules, alerts, and other managed content. The exact items depend on the application architecture.
When is an Apple App Store or Google Play release required?
A store release may be required for changes to native application code, operating-system compatibility, permissions, certain SDKs, or functionality that cannot be delivered through dynamic configuration. We choose the right release path for each change.
How quickly do content changes appear for visitors?
Publication timing depends on the configured content-management workflow, caching, offline behavior, and synchronization rules. We confirm with you how quickly each type of change reaches visitors in your setup.
What happens when visitors are offline?
Visitors using offline-capable experiences may continue to see the content already available on their device. Updated content can be refreshed according to the application’s synchronization behavior when connectivity becomes available.
How are app updates tested before release?
Software and configuration changes follow the testing and release process established for your deployment. We document the exact QA, UAT, approval and store-submission steps for your project.
Can venue teams see what changed in an update?
Release notes, change logs, or administrative update history may be provided depending on the workflow and tools used. If you need formal change tracking, we confirm the reporting available for your setup.
Who is responsible for maintaining the app after launch?
Maintenance responsibilities depend on the service agreement. We agree with you up front who handles content updates, software maintenance, store releases, operating-system changes, integrations and support.
Explore by venue type & related capabilities
Keep exploring
Stay Ahead with Easy Updates
Keep your app fresh and engaging.
