Direct answer

Test App My Community as a publishing and service channel, not as a feature list. Run one realistic stay through the native and web routes: arrival, map, alert, activity booking, request, purchase and reservation change. Record the source, editor, personal data, integration field, failure signal and fallback for each step.

Before signing, obtain the configured scope, current integration map, privacy and security documents, accessibility evidence, support route, app-store ownership, export format and termination plan. Public pages do not establish the result for a future property.

Relationship boundary

The show listing opens a file; it does not close one.

App My Community appeared in the official 2026 Glamping Show Americas directory at booth 211. Its exhibitor profile describes custom-branded mobile apps for outdoor hospitality. UNIKOST has no documented partnership, reseller relationship or project role with the company.

The company's product pages describe activities, maps, notifications, forms, booking, purchases and named reservation integrations. Those statements are useful demonstration inputs. They do not prove package scope, accessibility, security, uptime, adoption or operating performance.

Own the content

A guest app creates a publishing job for the property.

A single place for maps, activities, rules and emergency information is useful only while it is accurate. Build a content register with an owner, source, review interval and emergency update route for every page or data set. State which version wins when the same fact also appears on the website, in a booking message or on a room card.

App My Community says calendars may be built or imported and notifications may be scheduled or sent to groups. Ask whether an import is one-time or synchronized, who may publish, whether approval is available and what history remains after a correction. The reviewed pages do not publish that administrative detail.

This profile is narrower than the guest-operations handoff guide. That article tests reservation, room release, access and housekeeping. This one asks whether a branded guest channel stays accurate, accessible and recoverable through an ordinary stay and an exception.

Keep a browser route

Do not make a native download the only way in.

The feature page describes a browser-based version shared by link or QR code. Test the same stay through both routes. In the native app, check installation, sign-in and permissions. In the browser, check small-screen navigation, weak connectivity and what happens after the tab is closed.

Send the link at the same point in the booking journey planned for guests and do not coach the tester. Count the steps to find check-in, quiet hours, help and the first booked activity. Keep a printed or otherwise independent fallback for essential arrival and emergency information.

The FAQ suggests pre-arrival email plus QR codes on property and offers a demo builder. Use that demo to test navigation and content structure, not to assume the final app or integration has already passed.

Map guest data

Every enabled feature adds a data decision.

The privacy policy identifies Armstrong Software, LLC as the company behind App My Community and covers its white-labeled apps. It says information submitted through a customer app may be shared with that customer depending on configuration. It also describes account data, devices, analytics, forms, purchases, messages, photos and optional precise location.

The policy says location may support maps, geofencing and notifications, including background operation when enabled. It says historical location is not retained, while a current on-property or off-property status may be kept. Ask to see the exact permission prompt, default, purpose, retention and deletion behavior. Essential information should still work when location is declined.

If guests can submit photos, decide whether the feature is needed. The policy describes access by the customer or location and a license for operational, social or marketing use subject to the customer's own notices and law. A property enabling the feature needs a plain notice, access rule and deletion route.

The policy names Firebase and Google Analytics and provides a contact route for access, correction or deletion requests. The contract file should still name who handles a request, what the property can delete, what remains in logs or backups and how data is returned or removed after termination.

Test integrations and exit

“Integrated” is the beginning of the acceptance test.

App My Community publishes pages for RMS, Newbook, Staylist, CampLife and Firefly Reservations. The described functions vary. Some pages mention reservation history and stay-timed alerts; others describe charges, booking, payments or check-in. The order should name the exact connection and fields available now.

Create a test reservation, change the dates, move the unit, cancel it and restore it if supported. Check when the app receives each event, what the guest sees, which messages stop and how the error appears to staff. For purchases, identify the merchant of record, receipt, refund and reconciliation path. Do not use real guest or payment data.

Read support and exit terms beside the sales page. The public terms describe an annual license, a renewal notice window and a two-business-day support response. Compare that with the property's operating hours and define severity levels for an arrival-blocking failure, incorrect alert, payment issue, broken integration and outage.

Identify whose developer accounts and app-store listings are used, who owns the property content and what happens after termination. Request usable exports for content, forms, requests, transactions, notifications and analytics. Test one export before launch. The operating-stack guide provides the wider system map around this channel.

Demonstration

Run one stay and one failure day.

On the ordinary stay, have the guest use native and web access, find arrival instructions, open the map, book an amenity, receive an update, submit a request and view a receipt. Have staff correct one item and verify the change.

On the failure day, move the guest, withdraw notification and location permissions, lose connectivity, publish an incorrect activity time, cancel a booking and request an export. Score each step pass, conditional or fail. A conditional step needs a named employee, written fallback and acceptable response time.

Buyer file

Keep these records together before launch.

  • Contracting entity, plan, locations, term and renewal date.
  • Native, web and app-store responsibilities.
  • Content owners, staff roles, approval and change history.
  • Integration fields, sync timing and error handling.
  • Privacy, security, retention, deletion and incident records.
  • Accessibility evidence and a non-app route to essentials.
  • Payment, refund, receipt and reconciliation ownership.
  • Support coverage, escalation, exports and exit steps.

FAQ

Is App My Community a property-management system?

The public site presents it as a custom-branded guest app with content, communication, forms, mapping, booking and purchase features plus integrations with named reservation systems. The buyer should define which records remain in the PMS and which are copied or acted on in the app.

Can guests use it without downloading a native app?

The official feature page describes a browser-based web app available by link or QR code. Test that route with the actual property content and preserve a non-phone fallback for essential arrival and emergency information.

Does the app use guest location?

The privacy policy says precise location is optional and may support maps, geofencing and notifications. It says historical location is not retained, although a current on-property or off-property status may be kept. Confirm the exact configuration and guest controls for the proposed app.

Which reservation systems are integrated?

App My Community publishes pages for RMS, Newbook, Staylist, CampLife and Firefly Reservations. Functions differ by connection, and some pages distinguish current capabilities from future ones. Require a current field map and acceptance test.

What should be verified before signing?

Verify the package, term, app-store responsibility, content workflow, web fallback, integration fields, personal-data flow, accessibility evidence, support coverage, export and exit plan. Use a test stay and a failure-day script rather than a feature checklist.

Sources

Project review

Place the guest channel inside the actual stay.

Record the stay, staffing, service and connectivity assumptions, then bring the demo script and unresolved ownership fields into a project review.

Review the guest-app plan