Short answer
For AR applications requiring deep integration with device capabilities or serving niche, standardized user groups, opt for native development to maximize performance and user experience, rather than compromising with cross-platform solutions.
- Field
- User-Centred Design
- Source
- JMIR mhealth and uhealth (2019)
- Method
- Comparative analysis and prototyping
- Evidence
- Strong effect
Prioritizing native platform development for augmented reality applications, especially in specialized fields like emergency response, can lead to superior performance and user experience by leveraging platform-specific features, while cross-platform approaches may introduce unnecessary complexity and cost. This user-centred design research insight is drawn from a 2019 study published in JMIR mhealth and uhealth. Using Comparative analysis and prototyping, researchers explored how this design variable affects real-world outcomes. The key design takeaway: For AR applications requiring deep integration with device capabilities or serving niche, standardized user groups, opt for native development to maximize performance and user experience, rather than compromising with cross-platform solutions.
Native AR Development Outperforms Cross-Platform for Specialized Emergency Response Tools
Prioritizing native platform development for augmented reality applications, especially in specialized fields like emergency response, can lead to superior performance and user experience by leveraging platform-specific features, while cross-platform approaches may introduce unnecessary complexity and cost.
JMIR mhealth and uhealth · 2019
Key Findings
- 01Native platform development allows for better utilization of platform-specific augmented reality features.
- 02Cross-platform development can incur higher development, testing, and maintenance costs.
- 03Organizations with standardized device ecosystems may not benefit significantly from cross-platform solutions.
- 04Data quality in map-based applications is critical for user experience and utility.
Application
Design takeaway
For AR applications requiring deep integration with device capabilities or serving niche, standardized user groups, opt for native development to maximize performance and user experience, rather than compromising with cross-platform solutions.
How to apply
When planning a new AR design project, conduct a thorough analysis of the required features, the target users' technical environment, and the long-term maintenance strategy to determine whether native or cross-platform development is the most suitable approach.
Project actions
- 01When choosing between native and cross-platform development for your design project, consider the specific needs of your users and the complexity of the features you aim to implement.
- 02If your project involves advanced technologies like augmented reality, research the capabilities of different platforms to see if native development offers significant advantages.
Method & Evidence
Variables
Strengths & Limitations
Strengths
- +Focuses on a practical application of AR technology.
- +Provides a clear argument for a specific development approach.
- +Considers economic and maintenance factors alongside technical ones.
Limitations
The specific AR features and the target user group in this study might not be representative of all design projects.
Reliability & validity
The study's validity relies on the thoroughness of the prototype development and the clarity of the comparative analysis. Reliability would be enhanced by replicating the development process with multiple developers or across different AR features.
Think critically
To what extent do the specific requirements of an application's domain (e.g., emergency response vs. casual gaming) dictate the optimal development platform strategy?
Design Principles
"Prioritize platform-specific optimization for specialized augmented reality applications to enhance functionality and user experience."
This insight is crucial for design teams developing complex, performance-sensitive applications. By understanding the trade-offs between native and cross-platform development, designers can make informed decisions that align with user needs, technical requirements, and project constraints, ultimately leading to more effective and adopted solutions.
What This Means for Your Design
For special apps like those used by emergency workers, making the app just for one type of phone (native) is often better than trying to make it work on all phones (cross-platform). This is because you can use the best features of that one phone, and it's easier to fix and update.
How to use in your project
- 1.Reference this study when discussing the rationale behind your choice of development platform for a digital product, especially if it involves specialized features or user groups.
Add to My Project
Quick Cite
Paragraph starter
The decision between native and cross-platform development for digital products, particularly those leveraging advanced technologies like augmented reality, carries significant implications for performance, user experience, and project economics. Research suggests that for specialized applications, such as those designed for emergency responders, native development can offer superior integration with platform-specific features and potentially lower long-term maintenance costs compared to cross-platform solutions, which may introduce added complexity and development overhead.
Source
JMIR mhealth and uhealth
An Argument Against Cross-Platform Development: Lessons From an Augmented Reality App Prototype for Rural Emergency Responders
journal · 2019
View sourceQuestions About This Research
- What does the research say about native ar development outperforms cross-platform for specialized emergency response tools?
- For AR applications requiring deep integration with device capabilities or serving niche, standardized user groups, opt for native development to maximize performance and user experience, rather than compromising with cross-platform solutions. Evidence: JMIR mhealth and uhealth (2019).
- Why does "Native AR Development Outperforms Cross-Platform for Specialized Emergency Response Tools" matter for design?
- This insight is crucial for design teams developing complex, performance-sensitive applications. By understanding the trade-offs between native and cross-platform development, designers can make informed decisions that align with user needs, technical requirements, and project constraints, ultimately leading to more effective and adopted solutions.
- How can designers apply this research?
- For AR applications requiring deep integration with device capabilities or serving niche, standardized user groups, opt for native development to maximize performance and user experience, rather than compromising with cross-platform solutions.
- What were the main findings?
- Native platform development allows for better utilization of platform-specific augmented reality features.. Cross-platform development can incur higher development, testing, and maintenance costs.. Organizations with standardized device ecosystems may not benefit significantly from cross-platform solutions.. Data quality in map-based applications is critical for user experience and utility.
- What research method was used?
- Comparative analysis and prototyping.
- How strong is the evidence?
- Evidence strength is rated Strong effect, based on a 2019 journal from JMIR mhealth and uhealth.
- What should I do differently in my next project?
- When planning a new AR design project, conduct a thorough analysis of the required features, the target users' technical environment, and the long-term maintenance strategy to determine whether native or cross-platform development is the most suitable approach.
- What are the limitations?
- The study focused on a specific type of AR application (emergency response) and may not generalize to all AR use cases or industries.