Rcherz Suite

Problem

Rcherz needed rich mobile products for individual archers and competition communities, plus dependable scoring terminals that could keep events operating across unreliable outdoor Wi-Fi, mobile data, device restarts, and long sessions.

My Contribution

Built and continue to evolve the native iPhone/iPad and Android products and the dedicated Android scoring terminal, combining deep archery workflows with platform modernization and operational safeguards.

Technical Work

• checkImplemented practice recording, arrow placement and target keyboards, shooting-condition and equipment data, competition discovery and participation, qualification and elimination results, awards, profiles, photos, comments, and social activity.
• checkDelivered a universal Objective-C iPhone/iPad product with adaptive portrait and landscape scoring and results UI, maps, cached REST data, image workflows, push behavior, and current iOS compatibility.
• checkDeveloped and modernized the main Java Android application around a large competition and results domain, current Android tooling, Firebase crash reporting, camera and location workflows, and reusable Rcherz modules.
• checkSeparated event scoring into a focused Android terminal with QR and PIN setup, target assignments, archer loading, foreground synchronization, boot recovery, wake behavior, and offline-aware result handling.
• checkCombined push and polling with command identifiers and pending-message recovery, allowing organizers to remotely start, stop, clear, load, or reassign competition devices without double execution.
• checkMaintained Google Play, App Store, Firebase Cloud Messaging, Amazon Device Messaging, CocoaPods, Gradle, REST, and platform compatibility across a product family spanning more than a decade.

Outcome

The iOS app and both Android listings remain public and maintained, and separating community features from operational scoring keeps event-day risk contained at real competitions.

Highlights