An Argument Against Cross-Platform Development: Lessons From an Augmented Reality App Prototype for Rural Emergency Responders
Bibliographic record
Abstract
BACKGROUND: Mobile augmented reality (MAR) apps offer potential support for emergency responders in rural areas. OBJECTIVE: In this report, we described lessons learned from the development process of augmented reality (AR) Farm Mapping to Assist, Protect and Prepare Emergency Responders (MAPPER), a MAR app that provides emergency responders onsite information about the agricultural operation they enter. METHODS: Cross-platform frameworks were used to create AR MAPPER to accommodate budget constraints and overcome issues with markerless MAR technologies. Although the single codebase and Web technologies streamlined development, cross-device hardware limitations impacted location accuracy, lengthened the development cycle, and required regular updates to third-party libraries. RESULTS: A hybrid development approach of using Web-based technologies with native tie-ins for specialized components and enhanced performance cut time and costs. This also led to consistency across multiple platforms and ensured that there is only a single set of source files to modify for Android and iPhone operating systems. Meanwhile, active development was delayed by some major hurdles. Apple and Google both released new versions of their operating systems, and the Wikitude framework issued four major updates, each of which brought with it some important enhancements and also led to some new issues. CONCLUSIONS: Developers should consider single platform native development to benefit from platform-specific MAR implementations and to avoid development, testing, and maintenance costs associated with cross-platform implementation. Emergency response organizations may be more likely to utilize a single platform across the devices used by their command staff. This also reduces the benefits of cross-platform development. Furthermore, providing map-based, non-AR cross-platform apps for landowners, farmers, and ranchers would help improve and maintain data quality, which is crucial for the utility and user experience of MAR apps.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".