Conference Tracker 2.7.2

Cons

• Requires an account/domain, user ID and password — the app is unusable without a configured Conference Tracker account; initial setup typically requires coordination with Engineerica/Sales.
• Onboarding/setup can be opaque: several user reviews indicate a lack of clear in-app guidance for first-time configuration and that contacting sales/support is often required to get a demo or credentials.
• App Store listing and in-app screens don’t fully document pricing, hosting options, or how to obtain the domain/account — can cause friction for new customers evaluating the product.
• iOS-only (designed for iPad) — limits deployment to Apple tablet hardware; organizations requiring Android or cross-platform kiosk hardware may need alternative solutions or extra hardware.
• Dependency on cloud connectivity — on-site internet issues could disrupt real-time syncing, badge printing workflows, or other cloud-dependent features unless offline workflows are provided.
• Printer and peripheral compatibility can be a pain point; while Bluetooth printers are supported, setup and troubleshooting may require extra time and technician knowledge.
• Some historically reported issues (push notifications, scanner bugs, layout/order bugs) — though many were addressed in updates, they indicate prior stability issues that some customers experienced.
• Limited public-facing self-serve documentation within the app/store listing — users may rely on support resources or vendor assistance for advanced configuration, integrations, or custom reporting.
• Pricing/licensing and demo access typically require contacting sales — this reduces transparency for buyers who want quick cost comparisons or trialing before engaging sales.
• Privacy/compliance considerations: attendee data is stored in the vendor’s cloud (Amazon); organizations with strict data residency or compliance needs should confirm storage, retention, and security policies before purchase.