Mobile Launcher Segmentation for Diverse User Interfaces
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current smartphones typically come with a single launcher that cannot meet the diverse interface style demands of different age groups, such as elderly, children, and carrier-customized preferences.
Innovation Solution
A method and system for producing multiple launchers by extracting and customizing XML files and .inc files from launcher main code, using PHP to display layouts, and generating client-customized graphics packages for mobile terminals, allowing users to choose from various interface styles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single launcher is provided in smartphones, then device complexity is reduced and ease of manufacture is improved, but adaptability to meet diverse interface style demands of different age groups deteriorates
Solution Approach 1:
The launcher is segmented into multiple independent launcher packages (e.g., launcher for elderly, launcher for children, standard launcher) that can be independently developed, customized, and installed. Each launcher package contains its own configuration files (XML, .inc files) that define its specific interface style and behavior, allowing the system to provide diverse interface styles without creating a monolithic complex system.
Solution Approach 2:
The smartphone launcher system is designed to be universal by supporting multiple launcher packages that can coexist and be switched between. The underlying architecture provides common functionalities (app management, navigation) while allowing different interface styles and customization options, making the system adaptable to various user groups including elderly, children, and standard users.
2Adaptability or versatility
If multiple launchers are customized for different age groups, then adaptability to diverse user needs is improved, but development and testing time increases
Solution Approach 1:
Common functionalities and configurations are prepared in advance as reusable templates and base configurations. The XML and .inc files contain pre-defined structures for common launcher elements (app grids, navigation bars, widgets) that can be inherited and modified across different launcher packages, eliminating the need to develop each launcher from scratch and significantly reducing development and testing time.
Solution Approach 2:
Launcher packages can be copied and replicated from a base template, with modifications made to specific configuration files (XML for layout, .inc for styling) to create customized versions for different user groups. This copying approach allows rapid proliferation of multiple launchers while maintaining consistency in core functionality and reducing the overall development burden.
3Adaptability or versatility
If multiple launchers with different interface styles are provided, then user preference satisfaction is improved, but ease of operation deteriorates due to multiple choices
Solution Approach 1:
The system provides self-service mechanisms that allow users to automatically select or switch between launchers based on their needs. This may include automatic detection of user profile (e.g., elderly mode, children mode) and automatic switching to the appropriate launcher, or providing simple default options that require minimal user decision-making while still offering the ability to switch when needed.
Data Source
AI summary
A method of producing launchers for a mobile terminal is disclosed. The method includes: obtaining launcher main code having an architecture of at least two launchers; extracting form the launcher main code a corresponding first parsed XML file and first macro definition .inc file of each of the at least two launchers, and generating a second XML file using the attribute information of all applications in the launcher main code; customizing the first XML file and first .inc file of each launcher and the second XML file to obtain a corresponding second .inc file of the launcher; generating a corresponding third XML file of each of the at least two launchers using the corresponding second .inc file and first XML file of the launcher; and compiling the corresponding third XML file to obtain the at least two launchers. A system for producing launchers for the mobile terminal is disclosed.