Tracup 
Keep your current release process
Continue uploading apps and using the app links and QR codes you already know.
Smart hardware companion app distribution
Help users find the right companion app from packaging, manuals and your website
Use PGYER’s existing upload, link, QR code and version management tools throughout device testing, delivery, user installation and future releases.
One app entry throughout the device delivery lifecycle
Packaging and manuals
PGYER link and QR code
User installs the right version
When you publish a new version, users can continue to visit the original app page.
Support multiple app platforms
Manage Android, iOS, HarmonyOS and other app releases.
Connect automated releases
Use the PGYER API with your existing build and release workflow.
Device delivery lifecycle
From team testing to every installation after device delivery
A companion app remains important after development. Packaging, manuals, reseller pages and support materials continue to generate installation demand long after a device ships.
Development and team testing
Upload test builds and let engineering, product and QA teams install them from a link or QR code.
Factory and channel delivery
Place the app entry on packaging, manuals, delivery materials or reseller pages.
First user installation
Give device users a clear app page with platform, version, update time and install status.
Future app releases
Publish new versions under the same app entry and reduce the need to reprint QR codes.
Device categories
Made for devices that depend on a companion app
Whether a device connects through Bluetooth, Wi-Fi, USB or a local network, PGYER can host and deliver its companion app.
Cameras and imaging
Cameras, thermal imaging, inspection scopes and capture devices
Wearables and health
Smartwatches, bands, health monitoring and fitness devices
Printing and labels
Portable printers, label makers, receipt and thermal printers
Drones and remote control
Drones, RC cars, models and wireless control devices
Locks and smart home
Smart locks, access control, home controls and security devices
Battery and energy
BMS, storage, power, charging and energy management devices
Long-term app entry
Reduce the impact of app updates on packaging and manuals
Use an app page link or QR code in device delivery materials. As long as the app remains available, future releases can continue to use that entry so shipped devices can still find the companion app.
- Use one app entry on packaging, manuals, websites and support materials
- Continue publishing Android or iOS versions under the same app
- Show version, update time, release notes and install status on the app page
- Use traffic and download statistics to understand changes in app entry usage
Device companion app
Current installable release
Entry
Link and QR code
Version
Continuous updates
Platforms
Android / iOS
The QR code on packaging does not need to change with every app release
Existing PGYER capabilities
Deliver device software with proven app distribution tools
The smart hardware workflow reuses existing product capabilities, so your team does not need to learn another system.
App hosting and download pages
Upload an app and create a clear download page with app and version details.
Download links and QR codes
Place the app entry on packaging, manuals, websites, reseller pages or support materials.
Versions and release notes
Publish later releases under the same app and keep update times and release notes.
Multi-platform app management
Manage Android, iOS, HarmonyOS and other supported app packages.
API-based publishing
Connect uploads and releases to your existing build, test or delivery workflow.
Traffic and download statistics
Review page visits and downloads to support regional and release maintenance.
How it works
Create a companion app delivery entry in four steps
Start with your current release workflow. No device changes or new hardware platform integration are required.
Upload the companion app
Create an app and upload an Android, iOS or other supported package.
Review the app page
Check the app name, icon, version, release notes and install status.
Place the link or QR code
Use the entry on packaging, manuals, your website, reseller pages or support materials.
Keep publishing under the same app
Release future versions and use statistics to review visits and downloads.
Common questions
Common companion app delivery questions
These questions often appear after devices have shipped and packaging QR codes can no longer be reprinted.
Do we need to reprint the packaging QR code after an app update?
Usually not. Publish the new version under the same PGYER app and continue using the original app page entry.
Can we publish both Android and iOS apps?
Yes. You can host packages for different platforms and provide the appropriate entry in delivery materials.
Can one vendor manage apps for several devices?
Yes. Create separate apps for different products and maintain their releases within the same team account structure.
Can we place the QR code in manuals and on our website?
Yes. App links and QR codes can be used on packaging, manuals, websites, reseller pages and support materials.
Can this connect to automated builds and releases?
Yes. Use the PGYER API to upload apps from your existing build or release workflow.
What can users see on the app page?
Users can see information such as the app name, icon, platform, version, update time and install status.
Create a lasting app entry for your next device
Start by uploading your existing companion app and keep using the PGYER links, QR codes and version workflow your team already knows.
