Developing Mobile Apps Using Cross-Platform Frameworks: A Case study

Embed Size (px)

Text of Developing Mobile Apps Using Cross-Platform Frameworks: A Case study

PowerPoint

Developing Mobile Apps Using Cross-Platform Frameworks: A Case studyShah Rukh Humayoun, Stefan Ehrhart, and Achim EbertInstructorChris Su SpeakerGuofu Long Good afternoon, everyone. I am speaker : Long guofu. Instructor : Chris Su.

In last few years , a huge variety of frameworks the mobile cross platform development have been released to deliver quick and overall better solution.

Today I want to share thesis() Developing Mobile Apps Using Cross-Platform Frameworks: A Case study.

1 OutlineBackgroundIntroductionThe Testing Scenarios and The Developed AppsThe User Evaluation StudyThe software Evaluation Conclusion

The remainder of this paper is structured as follows. In Section 1, we highlight the background. Section 2 , introduce the cross platform. In Section 3, we describe the three scenarios for developing apps and details of the development of these apps in different frameworks and environments. In Section 4, we provide details of the user evaluation study. In Section 5, we analyze from the software evaluation perspectives. Finally, we conclude in Section 6.

2

BackgroundAbout Backgroud.350%

The Rate Of Smartphones2012

The rate of smartphones amongst cell-phones was expected to exceed the 50% boundary in the year 2012 with the amount doubling each year .

4The Resolution

Where the smartphone more and more than before. The software engineers needs to consider

The resolutionScreen sizeComputation powerAnd different operating systems

It makes people very angry.

5

Screen Size

Where the smartphone more and more than before. The software engineers needs to consider

The resolutionScreen sizeComputation powerAnd different operating systems

It makes people very angry.

6computation power

Where the smartphone more and more than before. The software engineers needs to consider

The resolutionScreen sizeComputation powerAnd different operating systems

It makes people very angry.

7

operating systems

Where the smartphone more and more than before. The software engineers needs to consider

The resolutionScreen sizeComputation powerAnd different operating systems

It makes people very angry.

8computation poweroperating systems

resolutions

screen size

Where the smartphone more and more than before. The software engineers needs to consider

The resolutionScreen sizeComputation powerAnd different operating systems

It makes people very angry.

9

IntroductionIntroduction.10

How to solve this problem?How to solve this problem?Some people has beensuggested code once , run everywhere.Ok , that is cross plat form. 11

Code once, run everywhere!How to solve this problem?Some people has beensuggested code once , run everywhere.Ok , that is cross plat form. 12

How to solve this problem?Some people has beensuggested code once , run everywhere.Ok , that is cross plat form. 13

The Testing Scenarios and The Developed AppsThe testing Scenarios and the Developed Apps14

We choose three frameworks out of a variety of frameworks as well as the native iOS and Android environments for developing apps versions and then for detailed testing based on our targeted criteria.

Okay3We choose three frameworks out of a variety of frameworks as well as the native iOS and Android environments for developing apps versions and then for detailed testing based on our targeted criteria.Appcelerator Titanium , RhoMobile Rhodes, MoSync

3MovePic, BubbleLevel, and AnnotatePicThe scenarios setting MovePic, BubbleLevel, and AnnotatePicOur focus was towardstouch-events, accelerometer, camera access, and the file system access. We left otherinteraction-schema elements, such as localization services, due to their behavior complexity.

For each scenario, we developed apps using the above-mentioned frameworksas well as the native iOS and Android development environments.androidios15

MovePic, BubbleLevel, and AnnotatePicFor each scenario, we developed apps using the above-mentioned frameworks as well as the native iOS and Android development environments.Our focus was towards touch-events, accelerometer, camera access, and the file system access. We left other interaction-schema elements, such as localization services, due to their behavior complexity.Okay3We choose three frameworks out of a variety of frameworks as well as the native iOS and Android environments for developing apps versions and then for detailed testing based on our targeted criteria.Appcelerator Titanium , RhoMobile Rhodes, MoSync

3MovePic, BubbleLevel, and AnnotatePicThe scenarios setting MovePic, BubbleLevel, and AnnotatePicOur focus was towardstouch-events, accelerometer, camera access, and the file system access. We left otherinteraction-schema elements, such as localization services, due to their behavior complexity.

For each scenario, we developed apps using the above-mentioned frameworksas well as the native iOS and Android development environments.androidios16The MovePic Scenario

Goal was to test the support and processing of multi-touch gestures in smart-devices. This was done by hardcoding an image through the image view in the underlying device. The presented image could be manipulated with multi-touch gestures such as panning, pinch zooming, rotating and dragging. The native iOS version was developed using the built-in gesture recognizers. iOS

I use my phone to make a sample demo . U can found the picture had rotating in the current Screen.17

Demo

This was done by hardcoding an image through the image view in the underlying device. The presented image could be manipulated with multi-touch gestures such as panning, pinch zooming, rotating and dragging. The native iOS version was developed using the built-in gesture recognizers. iOS

I use my phone to make a sample demo . U can found the picture had rotating in the current Screen.18

Demo

This was done by hardcoding an image through the image view in the underlying device. The presented image could be manipulated with multi-touch gestures such as panning, pinch zooming, rotating and dragging. The native iOS version was developed using the built-in gesture recognizers. iOS

I use my phone to make a sample demo . U can found the picture had rotating in the current Screen.19The BubbleLevel Scenario

The bubblelevel scenario simulates a spirit level on the screen using the accelerometer data.

The BubbleLevel Scenario

About the BubbleLevel Scenario.the bubblelevel scenario simulates a spirit level on the screen using the accelerometer data.

a spirit level is a tool to measure if some object is parallel or orthogonal to the ground. the scenario`s goal was to test the support and processing of the accelerometer in the device as well as checking its request rate.

Look at the sample demo . U can find the number have change.

20

Demo

The BubbleLevel Scenario

About the BubbleLevel Scenario.the bubblelevel scenario simulates a spirit level on the screen using the accelerometer data.

a spirit level is a tool to measure if some object is parallel or orthogonal to the ground. the scenario`s goal was to test the support and processing of the accelerometer in the device as well as checking its request rate.

Look at the sample demo . U can find the number have change.

21

Demo

The BubbleLevel Scenario

About the BubbleLevel Scenario.the bubblelevel scenario simulates a spirit level on the screen using the accelerometer data.

a spirit level is a tool to measure if some object is parallel or orthogonal to the ground. the scenario`s goal was to test the support and processing of the accelerometer in the device as well as checking its request rate.

Look at the sample demo . U can find the number have change.

22

Demo

The BubbleLevel Scenario

About the BubbleLevel Scenario.the bubblelevel scenario simulates a spirit level on the screen using the accelerometer data.

a spirit level is a tool to measure if some object is parallel or orthogonal to the ground. the scenario`s goal was to test the support and processing of the accelerometer in the device as well as checking its request rate.

Look at the sample demo . U can find the number have change.

23The AnnotatePic Scenario

the annotatepic scenario`s goal was the utilization of complex interaction-schema such as camera access, file system access and phone -specific service.

The AnnotatePic Scenariothe annotatepic scenario`s goal was the utilization of complex interaction-schema such as camera access, file system access and phone -specific service. the basic task was to take image from the device`s camera, adding some additional information(name, description and date), and the saving the image and the data in the device`s internal memory.

Look at the demo.

24

Demo

The AnnotatePic Scenariothe annotatepic scenario`s goal was the utilization of complex interaction-schema such as camera access, file system access and phone -specific service. the basic task was to take image from the device`s camera, adding some additional information(name, description and date), and the saving the image and the data in the device`s internal memory.

Look at the demo.

25

Demo

The AnnotatePic Scenariothe annotatepic scenario`s goal was the utilization of complex interaction-schema such as camera access, file system access and phone -specific service. the basic task was to take image from the device`s cam