TL;DR
This paper introduces an extension to the Interaction Flow Modeling Language (IFML) specifically designed for mobile application front-end development. By providing a model-driven approach and automated code generation, it aims to reduce the manual effort, inconsistencies, and inefficiencies typically associated with creating mobile user interfaces.
What Problem Does This Paper Address?
Developing the front-end of mobile applications is a complex and often manual process. This leads to a high risk of errors, inconsistencies, and inefficiencies, especially when aiming for cross-platform compatibility. While model-driven approaches exist for web applications, there's a gap in addressing the unique challenges and interaction patterns of mobile environments. The authors aim to bridge this gap by extending IFML to better capture mobile-specific features and enable automated generation of mobile UIs.
Methods
The core of this work is the extension of the existing IFML standard to accommodate mobile application development. This involves:
- Extending IFML Concepts: Introducing new concepts and stereotypes within IFML to model mobile-specific UI elements (like
Screen,ToolBar,MobileComponent,MobileSystem) and events (user gestures likeLongPress,Swipe, and device-related events likeBatteryEvent,SensorEvent). - Model-Driven Approach: Utilizing these extended IFML models as the primary input for development.
- Automated Code Generation: Developing code generators that translate the IFML models into cross-platform mobile applications using HTML5, CSS, and JavaScript, specifically targeting the Apache Cordova framework. This process involves analyzing the IFML model (serialized as XMI) and generating the necessary front-end code.
Datasets
Not discussed in the paper. The paper focuses on a case study with the RedLaser application and mentions industrial development projects, but no specific datasets are listed for training or evaluation.
Key Insights and Ideas
- IFML's Adaptability: The paper demonstrates that IFML, a standard for platform-independent UI modeling, can be effectively extended to address the specific needs of mobile applications, highlighting its flexibility.
- Bridging the Gap: The proposed extensions directly tackle the limitations of standard IFML for mobile by incorporating mobile-specific UI components and event types, which are crucial for rich mobile user experiences.
- Productivity Gains: The model-driven approach with automated code generation offers significant potential for increased productivity and reduced development time compared to traditional manual development.
- Separation of Concerns: The approach inherently promotes a better separation of concerns between UI design and implementation, allowing different roles (designers, developers) to work more effectively.
Key Results
The paper reports on the implementation of a prototype IFML modeling tool and a code generator. A key result is the demonstration of the approach on the RedLaser application and an industrial case study. In the industrial case study, the model-driven development approach resulted in an estimated 48% effort saving on the core mobile app development and a 21% overall reduction in development cost compared to manual development. The authors also mention that the productivity in other industrial cases was at similar levels.
Limitations and Future Work
- Limitations:
- The paper focuses primarily on the client-side development of mobile applications.
- While the approach is demonstrated, the full scope of its applicability across all types of mobile applications might require further exploration.
- Future Work:
- Implementing more refined code generators.
- Studying design patterns specifically for model-driven mobile application design.
- Further exploration of the implementation of more refined code generators.
Summary updated