2014
DOI: 10.1016/j.csi.2013.08.007
|View full text |Cite
|
Sign up to set email alerts
|

Using standards to build the DIMAG connected mobile applications framework

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2015
2015
2019
2019

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(2 citation statements)
references
References 10 publications
0
2
0
Order By: Relevance
“…While Android prefer tabbed layout to have their tabs on the upper side of the layout 13 , iOS prefer to have the tabs on the bottom side of the layout 14 . With this kind of difference, existing multi-platform framework could not decrease the effort of devising appropriate user interfaces for the different device types and orientations, however it still helped to create a codebase which is usable across multiple platforms 15 .…”
Section: Related Workmentioning
confidence: 99%
“…While Android prefer tabbed layout to have their tabs on the upper side of the layout 13 , iOS prefer to have the tabs on the bottom side of the layout 14 . With this kind of difference, existing multi-platform framework could not decrease the effort of devising appropriate user interfaces for the different device types and orientations, however it still helped to create a codebase which is usable across multiple platforms 15 .…”
Section: Related Workmentioning
confidence: 99%
“…In this way, the client receiving program is always open, which not only occupies system resources, but also affects the operation of other applications. Programmers using this framework can start specific system development on the basis of a common function that has been implemented [6]. The framework provides a collection of classes for all the application's expected default behavior.…”
Section: Introductionmentioning
confidence: 99%