Develop Cross-Platform Smartphone Application for Lotus OA

Article Preview

Abstract:

Lotus OA is widely used in some large departments. Because of its special architecture, it is difficult to develop a corresponding native mobile application. This paper propose an economic structure to develop native mobile application for Lotus OA. Use this structure, traditional Web developer can directly participate in the Lotus mobile development. This paper introduces our development process, explain the reason why we choose this structure. Also, this paper compares our software structure with other software structures, the result shows that our structure is more economic than other structures.

You might also be interested in these eBooks

Info:

Periodical:

Advanced Materials Research (Volumes 926-930)

Pages:

2317-2320

Citation:

Online since:

May 2014

Authors:

Export:

Price:

Permissions CCC:

Permissions PLS:

Сopyright:

© 2014 Trans Tech Publications Ltd. All Rights Reserved

Share:

Citation:

* - Corresponding Author

[1] IBM Lotus official site. http: /www-01. ibm. com/software/cn/lotus/ 2013. 10. 22.

Google Scholar

[2] Raluca Budiu. Mobile: Native Apps, Web Apps, and Hybrid Apps. http: /www. nngroup. com/articles/mobile-native-apps/. 2013. 9. 14.

DOI: 10.3139/9783446435438.002

Google Scholar

[3] Charland A, Leroux B. Mobile application development: web vs. native[J]. Communications of the ACM, 2011, 54(5): 49-53.

DOI: 10.1145/1941487.1941504

Google Scholar

[4] Qiang Zhang, Feng Li. Weitao Gong, et al. The best method of developing Web 2. 0 application based on IBM Lotus Domino. http: /www. ibm. com/developerworks/cn/lotus/domino-web20-app/. 2008. 7. 10.

Google Scholar

[5] Xianwei Qi, Quancang Xin, Lin Dong, et al. Design and realization of mobile office system based on Lotus Domino[C]/Proceedings of 2010 Asia-Pacific Conference on Information Network and Digital Content Security (2010APCID). (2010).

Google Scholar

[6] Ghatol R, Patel Y. Beginning PhoneGap: Mobile Web Framework for JavaScript and HTML5[M]. Apress, (2012).

Google Scholar