2016
DOI: 10.1007/978-3-319-46295-0_11
|View full text |Cite
|
Sign up to set email alerts
|

Cross-Device Integration of Android Apps

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
2
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
3
3

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(2 citation statements)
references
References 15 publications
0
2
0
Order By: Relevance
“…Today, cloud/server-side synchronization allows such a migration but requires for each device to be individually connected to the server, as it is the case of Google suite (Docs, Meet, etc. ), Android and others [1], [2]. Also, some approaches such as LiquidJS [3], which is based on Liquid Software principals [4], allow to adapt services to device characteristics.…”
Section: Introductionmentioning
confidence: 99%
“…Today, cloud/server-side synchronization allows such a migration but requires for each device to be individually connected to the server, as it is the case of Google suite (Docs, Meet, etc. ), Android and others [1], [2]. Also, some approaches such as LiquidJS [3], which is based on Liquid Software principals [4], allow to adapt services to device characteristics.…”
Section: Introductionmentioning
confidence: 99%
“…Some works as seen in [2], [3] and [4], had tried to address the multi-device service migration -but not multi-OS (e.g., Android and iOS), and all used Android as a platform.…”
Section: Introductionmentioning
confidence: 99%