Deploy Anywhere Framework For Heterogeneous Mobile Application Development

• US 20100017812A1
• Filed: 12/15/2008
• Published: 01/21/2010
• Est. Priority Date: 07/18/2008
• Status: Active Grant

• Current Assignee: Sybase Incorporated (SAP SE)
• Original Assignee: Sybase Incorporated (SAP SE)
• Inventors: NIGAM, Samir
• Granted Patent: US 8,769,553 B2
• Time in Patent Office: Days
• US Class Current: 719/328
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces

Abstract

A system, method, and computer program product are provided for developing a portable software application. The method includes the steps of defining a project, adding a screen to the project, the screen being defined as a generic screen or a platform-specific screen, adding a component to the screen, the component being defined as a generic component or a platform-specific component, redefining the screen as a platform-specific screen when it is defined as a generic screen and one or more platform-specific components have been added to the screen, and defining an application flow from the screen to one or more additional screens.

Claims

1. A method for developing a portable software application, said method comprising:

(a) defining a project;

(b) adding a screen to said project, said screen being defined as a generic screen or a platform-specific screen;

(c) adding a component to said screen, said component being defined as a generic component or a platform-specific component;

(d) redefining said screen as a platform-specific screen when it is defined as a generic screen and one or more platform-specific components have been added to said screen; and

(e) defining an application flow from said screen to one or more additional screens.

2. The method of claim 1, wherein step (a) comprises setting a development language for said project.

3. The method of claim 1, wherein said screen is added to said project by selecting a pre-existing screen.

4. The method of claim 1, wherein said screen is created using a template.

5. The method of claim 1, wherein said component is added to said screen by selecting said component from a palette.

6. The method of claim 1, further comprising setting properties for one or more controls associated with said component.

7. The method of claim 6, further comprising determining if said controls are platform specific.

8. The method of claim 1, wherein step (a) comprises defining a sequence of screens presented to a user.

9. The method of claim 1, further comprising:

defining a first device profile;

building an application for a first device based on said first device profile;

defining a second device profile;

analyzing said application for deployment to a second device based on said second device profile; and

presenting a portability analysis to a user based on said analyzing step.

10. The method of claim 9, wherein said analyzing step comprises performing a portability check.

11. The method of claim 10, wherein said portability check comprises:

comparing said first device profile to said second device profile to determine differences between said first device and said second device;

determining whether said portable software application relies on any capabilities in said first device that are absent or otherwise different in said second device; and

identifying usage of said one or more platform specific components.

12. The method of claim 1, further comprising providing functionality to said component by identifying platforms supported by said component.

13. A computer program product having control logic stored therein, said control logic enabling a processor to develop a portable software application according to a method that comprises:

defining a project;

adding a screen to said project, said screen being defined as a generic screen or a platform-specific screen;

adding a component to said screen, said component being defined as a generic component or a platform-specific component;

redefining said screen as a platform-specific screen when it is defined as a generic screen and one or more platform-specific components have been added to said screen; and

defining an application flow from said screen to one or more additional screens.

14. The computer program product of claim 13, the method further comprising:

defining a first device profile;

building an application for a first device based on said first device profile;

defining a second device profile;

analyzing said application for deployment to a second device based on said second device profile; and

presenting a portability analysis to a user.

15. The computer program product of claim 14, the method further comprising:

performing a portability check.

16. The computer program product of claim 15, the portability check comprising:

comparing said first device profile to said second device profile to determine differences between said first device and said second device;

determining whether said portable software application relies on any of capabilities in said first device that are absent or otherwise different in said second device; and

identifying usage of said one or more platform specific components.

17. A system for developing a portable software application, comprising:

a project defining module configured to define a project;

a screen adding module configured to add a screen to said project, said screen being defined as a generic screen or a platform-specific screen;

a component adding module configured to add a component to said screen, said component being defined as a generic component or a platform-specific component;

a redefining module configured to redefine said screen as a platform-specific screen when it is defined as a generic screen and one or more platform-specific components have been added to said screen; and

an application flow defining module configured to define an application flow from said screen to one or more additional screens.

18. The system of claim 17, wherein said project defining module is configured to set a development language for said project.

19. The system of claim 17, wherein said screen adding module is configured to add said screen to said project by selecting a pre-existing screen.

20. The system of claim 17, wherein said component adding module is configured to add said component to said screen by selecting said component from a palette.