Performance in mobile apps
📱📈
Comprehensive Analysis of Innovative Cross-Platform App Development Frameworks
Types of mobile apps
- Native
Types of mobile apps
- Native
- Hybrid
Types of mobile apps
- Native
- Interpreted
- Hybrid
The framework choice
Recentness
¿Why those frameworks were chosen?
Novelty
JS Support
Developers interests
Community
UI navigation
Design and Features Requirements
Multimedia Access
C
R
U
D
reate
ead
pdate
elete
Contact List
| Paradigm | Interpreted | Interpreted | Hybrid |
| Framework Version | 0.22 | 2.0.0-beta-3 | 0.11.1 |
| JavaScript Version | JSX | Angular JS | UX Markup |
| Camera Access | Yes | Yes | Yes |
| Image Gallery Access | Yes | Yes | No |
| Contact Access | Yes | Yes (untested) | No |
| Navigation | Intermediate | Simple | Complex |
| GPS Access | Yes | Yes | Yes |
| Remote Data Fetching | Simple | Simple | Simple |
| Debbuging | Simple | Simple | Simple |
| Framework Setup | Simple | Simple | Simple |
| Sidebar/Drawer | Simple | Simple | Simple |
| Code Reusability | 100% | 100% | 100% |
| UI Development | Slow but very customizable | Core features | Easy and Fast |
Implementation and Results
Cross-Platform Mobile Development: A Study on Apps with Animations
Introduction
A mobile application may require to be developed several times, one for each supported platform, thus dramatically increasing the required time and skills for developers, and finally, the cost of production.
Framework's Performance Comparison
Titanium
MoSync
Paper's Goal
Design and Implementation
A serious game which aims to help children to learn letters. The fishes Nemo and Dory race along a path and the child has to move the Nemo fish to avoid obstacles. This game requires to implement a lot of animations to move the two fishes, Nemo between four positions, the obstacles and an octopus. Moreover, to realized the illusion of the horizontal movement of Nemo, the background is moved during all the play, changing its speed depending on the result of the choices of the player
Game
Design and Implementation
| MoSync | Titanium | Jquery | Phonegap | |
|---|---|---|---|---|
| Licenses | 5 | 4 | 5 | 5 |
| API | 3 | 4.5 | 2 | 2 |
| Community | 3 | 5 | 5 | 5 |
| Tutorials | 4 | 5 | 4 | 5 |
| Complexity | 2 | 5 | 4 | 4 |
| IDE | 4 | 5 | - | - |
| Devices | 2 | 4 | 5 | 4 |
| GUI | 4.5 | 5 | 3 | - |
| Knowledge | 5 | 5 | 5 | 5 |
Conclusion
The best framework for development of mobile applications with animations is Titanium, because it natively supports, with some limitations, animations and transition effects, and its performances are good and promising even for applications more complex than the case study.
Future work
Analysis of new frameworks
Impact of Progressive Web Apps on Web App Development
PWA - History - Features
Sayali Sunil Tandel, Abhishek Jamadar
Student, Department of Computer Engineering, Smt.Indira Gandhi College, Navi Mumbai (Ghansoli),
Maharashtra, India
- Responsive
1- Who designed the concept of PWA?
2- What a PWA is?
3- Why did PWA exits?
4- Mobile development approaches
- Independent of connectivity
- Installation
- Fresh
Native App vs PWA vs Standar Web app
Core tenets of PWA
1- Service Workers
2- App Shell
3- Web App Manifest
Results - Lighthouse
Progressive Web Apps: the Definite Approach to Cross-Platform Development?
Introduction
- Status of mobile develop
- Advantages of cross-platform develop
- Objetive of the paper
Environment of develop
- Native Development and WebApp Development
- PWA
- Cross-platform development
Tim A. Majchrzak University of Agder, Kristiansand, Norway
Andreas Biørn-Hansen, Tor-Morten Grønli Faculty of Technology, Westerdals Oslo ACT, Oslo, Norway
Unified Development
- Requirements
1- Conceptual View
2- Technical View
- Web Browser
Conclusion
William Jobe
Stockholm University, Stockholm, Sweden
Native Apps vs Mobile Web Apps
Explore the viability of replacing native applications with mobile web applications in a developing country setting
Objective
2 apps were developed
Running tracks 🏃♀️
Scheduling "slum runs" 📆
- MyTracks
- RunKeeper
Samples
- 30 elite runners from Kenya 🇰🇪
- 4 - 6 months of use
- 30 smartphones
Screenshot of run tracking app
Runners expressed that they had tested the mobile web app as instructed, but the GPS location data was always incorrect.
The results showed that the GPS location functionality jumped a few hundred meters in different directions and therewith added distance to the run without having actually started to run.
Results using run tracking app
Screenshot of "slum runs" app
Results using "slum runs" app
The mobile web app for booking “slum runs” was appreciated by the runners and proved to be highly useful.
The runners used the web app as if it were a native app without any significant problems.
Conclusions
- The conclusions from this research are that native apps are still the best choice for hardware intensive apps.
- However, websites or applications that primarily consume content can be successfully replaced with web apps.
Survey on Native and Hybrid Mobile Application Development Tools
Bharati Vidyapeeth’s
Institute of Management Information Technology
University of Mumbai, Maharashtra, India
Compare native apps vs hybrid apps based on the advantages and disadvantages between them in order to developers can choose the best
option to build mobile apps.
Objective
Seven popular hybrid apps frameworks were studied and compared with against native frameworks.
There are no samples.
Samples
-
Ionic.
-
Mobile Angular UI.
-
Intel XDK.
-
Appcelerator Titanium.
-
Sencha touch.
-
Kendo UI.
-
Phone Gap.
-
Bonus.
-
Native apps.
Possible experiment (?
Native vs Hybrid frameworks comparisson
Hybrid frameworks comparisson
Conclusions
1) Depending on the project you will made, you'll choose between web apps, native apps, hybrid apps.
2) Hybrid apps will be a bridge between native and web apps, merging advantages from both of them (high performance on hardware [native] and cross-platform compatibility [web apps]).
3) Ionic Framework is the best framework to develop hybrid apps.
Critics
- Wrongly written.
- It does not have a clear objective.
- Many of the comparisons they make are not supported by a clear source.
- The conclusion is not clear.
Example
Progressive Web Apps: The Possible Web-Native Unifier for Mobile Development
Objective
Compare bundle sizes, launch time and first render time in hybrid, interpreted and PWA apps
Samples
- 1 PWA
- 1 Hybrid app developed with Ionic
- 1 Interpreted app developed with React Native
- 1 Nexus 5X with Android 7.0
- 10 tests per app
Screenshots
Results
Critics
- They don't have benchmarks about use of CPU, RAM, battery and GPU.
- This paper is old and they doesn't have results on iOS.
State
Of
The Art
1- Comparar performance a través de benchmarks en CPU, RAM, GPU y uso de Batería entre aplicaciones móviles híbridas y interpretadas.
2- Comparar CPU performance de aplicación interpretada vs PWA.
3- Comparar CPU performance de aplicación interpretada vs PWA vs Hybrid app.