[go: up one dir, main page]

WO2013109858A1 - Canevas de conception - Google Patents

Canevas de conception Download PDF

Info

Publication number
WO2013109858A1
WO2013109858A1 PCT/US2013/022106 US2013022106W WO2013109858A1 WO 2013109858 A1 WO2013109858 A1 WO 2013109858A1 US 2013022106 W US2013022106 W US 2013022106W WO 2013109858 A1 WO2013109858 A1 WO 2013109858A1
Authority
WO
WIPO (PCT)
Prior art keywords
design canvas
computer
canvas
application
properties
Prior art date
Application number
PCT/US2013/022106
Other languages
English (en)
Inventor
Scott COTTLE
Robert M. Brinson
Drew RAMSEY
Kimberly Allen
Kjersti KYLE
Evan HALLEY
Whit RHODES
Original Assignee
Smart Online, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Smart Online, Inc. filed Critical Smart Online, Inc.
Publication of WO2013109858A1 publication Critical patent/WO2013109858A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/34—Graphical or visual programming

Definitions

  • Smartphones have become popular computing and communication devices throughout the world. Smartphones have become popular, at least in part, because the functionality of these devices may be easily customized by users by way of developing and/or installing mobile applications, thereby providing users with relevant functionality and connecting brands with interested consumers. There are now well over one million mobile applications available on the various smartphone mobile application stores, and some expect mobile application downloads to exceed seventy five billion by the end of 2014.
  • Some attempted solutions for these problems have involved use of a translation/abstraction layer used during development of mobile applications. Developers use the translation/abstraction layer by writing code once in a non-native environment (e.g. Ruby), and the tool translates this code into multiple other languages or codes. Such translators, however, tend to seek the lowest common denominator among the various languages or codes in an attempt to ensure that the mobile application works in different environments. This can result in mobile applications that are not optimized for each (or even any) of the various targeted platforms. Furthermore, these and other development environments require prior software development knowledge and are only suited for technically savvy individuals.
  • a non-native environment e.g. Ruby
  • the present disclosure is directed to a design canvas for a development platform for mobile applications.
  • the design canvas can include a user interface for the development platform.
  • the design canvas can be used to design, create, and configure various aspects of a mobile application including, but not limited to, presentation, features, and functionality of the mobile applications.
  • the design canvas also can be used to design, create, and/or configure various aspects of mobile websites, web applications, conventional websites, desktop applications, print media, other digital and/or real media, combinations thereof, or the like.
  • the development platform can enable a tech savvy or non-tech savvy user- developer to design and/or configure mobile applications, the "look and feel" of the mobile applications, functionality of the mobile applications, and/or feature sets of the mobile applications, as well as initiating the build and compile process of the mobile application.
  • This process may support manually or automatically building and/or initializing a back office or portal associated with the mobile application.
  • a method and/or subsystem may then retrieve native, interpreted, precompiled or compiled source code units from a repository or bucket and hooks these units to the target platform, thus creating a functioning interface.
  • This method or process is followed by a manual or automated process that constructs and compiles the end mobile application and supports building and/or initiating a back office or portal associated with the mobile application.
  • the design canvas can be presented as a user interface that represents a dimension presentation area for an application, web page, print media, or the like.
  • the application, web page, print media, or other project will be described as a mobile application. Because the concepts and technologies disclosed herein can be used to develop other types of media and/or projects, it should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the design canvas can include and/or can represent a screen real estate or part thereof.
  • the design canvas can be generically dimensioned to enable users to establish or edit dimensions for the mobile application.
  • the design canvas also can be used to dynamically adjust a resulting presentation area of the mobile application based upon known or expected device screen dimensions.
  • the design canvas can also be precisely dimensioned, or a combination of precise and generic dimensioned may be used.
  • the design canvas can be segmented into discreet functional and non-functional display areas, and segments included in the mobile application (as displayed in the design canvas) can be edited or removed via the design canvas.
  • users may place elements on the design canvas, edit elements in the design canvas, and/or remove elements from the design canvas and/or areas or segments thereof.
  • the design canvas can be generated and presented by the development platform, and the development platform can be configured to track, store, and use placement locations and/or other configuration information about the design canvas to build a mobile application.
  • the design platform can monitor splits, segments, element placement, or the like, in the design canvas to supply and direct build, rebuild, update processes, or the like with respect to the mobile application developed using the development platform.
  • the design canvas also can be configured to maintain and/or enforce various rules and/or standards.
  • the design canvas can maintain and/or enforce rules or standards for best practices, design guidelines, compliance information, various interactions, combinations thereof, or the like.
  • FIGURE 1 is a block diagram illustrating one operating environment for the concepts and technologies disclosed herein, according to one embodiment.
  • FIGURE 2 is a block diagram illustrating another operating environment for the concepts and technologies disclosed herein, according to another embodiment.
  • FIGURES 3A-3E are user interface drawings showing aspects of the concepts and technologies disclosed herein for a design canvas for a mobile application development platform, according to various embodiments.
  • FIGURE 4 is a flow diagram illustrating a method of developing mobile applications, according to one embodiment.
  • FIGURE 5 is a block diagram illustrating a computer hardware and software architecture for a computing system capable of implementing aspects of the embodiments presented herein.
  • the operating environment 100 shown in FIGURE 1 includes a development system 102.
  • the functionality of the development system 102 is provided by a personal computer ("PC") such as a desktop, tablet, or laptop computer system.
  • PC personal computer
  • the functionality of the development system 102 is provided by other types of computing systems including, but not limited to, server computers, handheld computers, netbook computers, embedded computer systems, personal digital assistants, mobile telephones, smart phones, or other computing devices.
  • the development system 102 operates in communication with a communications network (“network”) 104.
  • network communications network
  • the development system 102 provides the functionality described herein for a design canvas for a development platform for mobile applications without communicating with other devices.
  • the functionality of the development system 102 is provided by a server computer.
  • the illustrated embodiment should be understood as being illustrative, and should not be construed as being limiting in any way.
  • the development system 102 is configured to execute an operating system 106 and one or more application programs such as, for example, an application development module 108 and/or other application programs.
  • the operating system 106 is a computer program for controlling the operation of the development system 102.
  • the application development module 108 is an executable program configured to execute on top of the operating system 106 to provide various functions.
  • the application development module 108 is an executable program configured to provide an interface for creating, editing, saving, and outputting mobile applications.
  • the application development module 108 is configured to receive, store, and/or obtain from a user, various application data 110.
  • the application data 110 can correspond to variables, images, text, and/or indications of functionality that is desired for inclusion in a mobile application.
  • the application data 110 is stored at the development system 102 in a memory or other suitable data storage device.
  • the application data 110 is obtained or received by the application development module 108 from a user or external device or system, illustrated generally in FIGURE 1 as a data source 112.
  • the data source 112 can include a user interfacing with the application development module 108 and/or a device or system that communicates with the development system 102 via the network 104.
  • the functionality of the data source 112 is provided by hard drive, memory, or other data storage device associated with the development system; a server computer or other device configured to host or store the application data 110; a user interfacing with the application development module 108; and/or any other suitable entity.
  • the application data 110 is received at and/or imported by the application development module 108 for use in developing and outputting mobile applications. Example methods for obtaining the application data 110 are illustrated and described below.
  • the application development module 108 is configured to create, edit, store, provide previews of, and output mobile applications. According to various embodiments, the application development module 108 is configured to output one or more versions of a mobile application 114A-N (hereinafter collectively and/or generically referred to as "mobile application versions 114").
  • a first mobile application version 114A corresponds to a mobile application that is executable by devices running a member of the iOS family of operating systems from APPLE CORPORATION in Cupertino, California
  • a second mobile application version 114N corresponds to a mobile application that is executable by devices running a member of the ANDROID family of operations systems from GOOGLE, INC. in Mountain View, California. Because the mobile application versions 114 can include versions of mobile applications executable by other platforms, it should be understood that these embodiments are illustrative, and should not be construed as being limiting in any way.
  • the application development module 108 is configured to obtain the application data 110 and to use the application data 110 to generate a basic outline of a mobile application for which the mobile application versions 114 are to be created.
  • the application data 110 indicates one or more blocks of code, snippets, routines, or other bocks of code (hereinafter referred to as "modules") 116 that are to be included in a mobile application.
  • the modules 116 can be stored in a module library 118.
  • the functionality of the module library 118 is provided by a data storage device associated with the development system 102. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the modules 116 can be configurable blocks of executable code. Users can select or specify modules 116 to be added to a mobile application. Additionally, users can configure settings or variables included in the modules 116. According to various embodiments, the development system 102 guides users through configuration of the modules 116 via one or more user interfaces 120.
  • the user interfaces 120 can present variables of the modules 116, provide data entry fields for specifying values of the variables, and/or provide mechanisms by which users can arrange, remove, add, and/or otherwise control the variables within the module 116. Additional aspects of the modules 116 are described in more detail below.
  • the user interfaces 120 can include a design canvas 122.
  • the design canvas 122 can be configured to support interactions with users or other entities to allow the users to create a mobile application such as one or more of the mobile application versions 114.
  • the development system 102 can support, but is not limited to, blocks of functionality, customization of functionality, data management, and automated application building.
  • the design canvas 122 can be a portion of the development system 102 that can allow a user to design one or more application canvases for a mobile application.
  • an "application canvas" can refer to an application display screen.
  • the application canvases can represent the mobile application execution environment, and as such, the user can interact with the application canvas as displayed in the design canvas 122 to allow user to create and customize the mobile application display on the mobile device.
  • the development system 102 also can be configured translate the application canvas to a configuration file.
  • a webservice application programming interface (“API") 124 that can be accessed by a requestor, and via which the development system 102 can deliver the configuration files to the requestor.
  • the webservice API 124 can be accessed when the mobile application is built, or on demand to the mobile devices in the field.
  • the mobile devices and/or applications on the devices can consume the configuration files to deliver a particular look and feel and functionality to the user.
  • the design canvas 122 is a graphic interface via which the users can design the look and feel of mobile applications.
  • the design canvas 122 can act as and/or interface with an emulator for the purposes of previewing the mobile application, visualizing various functionality and/or visual elements of the mobile application, quality assurance (QA), combinations thereof, or the like.
  • the design canvas 122 can provide the user with the ability to select, position, and/or configure various elements and/or element relations to the design canvas 122, the mobile application, and/or other elements individually.
  • the elements can stand alone or can be nested within other elements. Elements can be nested within other nested elements to an 'nth' level. Elements can also be set to overlap each other with hierarchies that can be defined by the user. Additionally, or alternatively, the elements can be prevented from overlapping each other.
  • the design canvas 122 can manage and/or allow for multiple canvases to represent different functionality or views of application blocks. These canvases can represent display screens to be generated by the mobile device executing the mobile application. Elements can be dropped onto each canvas and can represent gesture recognizers, display content, and/or content obtained (e.g., pulled) from external sources and/or ingested content.
  • the application canvases also can represent different types of displays such as, for example, table views/lists, scrolling and non-scrolling views which can include splash screens, home screens, subsequent screens, sections of screens, combinations thereof, or the like.
  • the design canvas 122 also can include an aggregated view of multiple pages and their interactions.
  • a user can interact with the design canvas 122 to pull non-visible regions of the application canvas into a viewable area for various purposes such as, for example, completing design of the application canvas.
  • Application canvases can be saved as configuration data that can be retrieved to recreate or restore previous design sessions.
  • the application canvases also can be cloned and used to generate views on various devices.
  • the design canvas 122 can be used in conjunction with the development system 102, which as described in detail above can provide libraries of content and functionality that can be added to the mobile application.
  • An example of content that can be added to the mobile application can include images uploaded and provided to the development system 102 users or uploaded to the development system 102 by the users to be used in the mobile application design.
  • An example of functionality can include the various modules 116 described herein, which can include, for example, a block of code that performs a specific action or actions and integrates with native phone capabilities, such as a webservice API call to Facebook to retrieve a collection of posts associated with a Facebook user account. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the mobile application designer may be provided with one or more application canvases, which can be customized to provide a unique non-template display for the mobile application user. For example, in order to display a collection of Facebook wall posts, the mobile application designer may customize an application canvas presenting a list of some or all posts associate with a particular user, and another application canvas presenting only one post. In this way, the mobile application designer may provide the mobile application user with a view that allows quick scanning of social networking post titles and dates, and can allow the user to drill down to a specific social networking post to retrieve further information and/or to interact with an individual social networking post. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the mobile application designer may also design and develop the overall interaction structure for using the mobile application by placing gesture recognizer elements such as buttons that can be configured to allow the mobile application users to navigate between blocks of functionality of the mobile application.
  • the mobile application designer may create a mobile application that supports a particular event such as an annual conference, where a button on the home application canvas can be used to navigate to a list of conference workshops and/or presentations.
  • the list of workshops and/or presentations may allow the mobile application user to navigate to a detailed description of a particular workshop or presentation, and the mobile application designer may add a gesture recognizer element to that detail application canvas to allow the mobile application user to then navigate to a list of speakers at the conference, or a list of Twitter posts tagged with a particular hashtag related to the conference or presentation.
  • the mobile application designer also can design an application canvas that may be used for some or all user device types, such as small-screened devices such as app-capable mobile phones and tablets.
  • the development system 102 may send a configuration file as a data structure that could be XML, JSON, text, or other non-proprietary or proprietary file(s).
  • the mobile application framework may use a parser, designer, or interpreter, to read this information. For every application canvas or element, there can be an object with attributes including but not limited to size, position, etc. Data can be parsed into individual platform views.
  • the application canvas configuration file may be adapted to work on multiple device sizes and aspect ratios by, for example, applying algorithmic conversions to application canvases and elements on the application canvases for the purpose of converting for other device aspect ratios: in full, semi-conversion for subsequent user modification, or duplicated, left blank, with all data and configurations intact for user recreation.
  • the mobile application designer also can design multiple instances of an application canvas that may be targeted to specific device types or used in specific instances on a user's device. For example, the mobile application designer can choose to use one application canvas configuration when the mobile application user is viewing the mobile application using a device with a screen aspect ratio that is taller than it is wide (e.g., portrait mode), and can use another application canvas configuration when the mobile application user is viewing the mobile application using a device having a screen aspect ratio that is wider than it is tall (e.g., landscape mode).
  • a device with a screen aspect ratio that is taller than it is wide e.g., portrait mode
  • another application canvas configuration when the mobile application user is viewing the mobile application using a device having a screen aspect ratio that is wider than it is tall
  • the mobile application designer also may choose to use a different application canvas configuration for screen dimensions that are relatively smaller than some other screen dimensions.
  • the development system 102 may be configured to support this feature by including a specific configuration file when the mobile application is compiled and built, or the development system 102 may read a property in the API request for a configuration file, and return a specific configuration based on that property.
  • the configuration file may be saved to the device as part of the mobile application data, and can allow the device to display the application canvas configuration when the device does not have access to a data connection.
  • the device also may check for a new configuration file when the mobile application user selects an option to view a part of the mobile application that uses that application canvas configuration, allowing the mobile application designer to update the mobile application look and feel during execution of the mobile application.
  • the design canvas 122 can be initialized.
  • the mobile application can request, retrieve, interpret, and process delivered configuration data to dynamically present the user with a mobile rendition of the application canvas. In some cases this includes the retrieval of content, which can be mapped to certain views to apply properties and functionality.
  • the application canvas can be drawn by creating all application canvas elements (views) as the most common generic view's common size, location, and theming properties. The mobile application can then apply to each element included in the application canvas its more specific properties based on respective data types associated with those elements.
  • the application canvas configuration file may be used by itself, for example, when the display content including but not limited to text or images, are included as part of the configuration file.
  • the application canvas configuration file may also be used in combination with a data file, or with data retrieved by an API call to another webservice where the mobile application designer intends to use the application canvas configuration file to display one or more data records, for example, Facebook wall posts. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the mobile application designer may have the ability to select whether some display elements should be included in the mobile application, such as a tabs bar which may appear on some, none, or all application canvas displays, or for example if a navigation bar should be included on the home screen of the mobile application.
  • some elements, such as a navigation bar may always be included as part of an application canvas, such as including a navigation bar on an application canvas to allow the mobile application user to navigate back through previous application pages.
  • the mobile application designer can be given a blank canvas representing a mobile device screen.
  • the application canvas can be non-scrolling and can fill the device screen.
  • the application canvas also can scroll to allow the user to view an application canvas that is larger than the device screen.
  • the application canvas also can be divided into any combination of scrolling and non- scrolling regions.
  • the mobile application designer may divide the application canvas into smaller regions by interacting with the design canvas 122 is some way, such as right-clicking on the design canvas 122 and selecting to split the design canvas 122, and thereby the application canvas, into two application canvas regions.
  • the application canvas regions can, but do not necessarily, have similar properties that can be customized by being divided further into smaller application canvas regions and/or by adding elements that provide display or interaction functionality to the mobile application.
  • the mobile application designer may also divide the application canvas by selecting to split the application canvas into application canvas regions having differing properties, such as by adding a fixed application canvas region that does not scroll on the device screen, and a scrolling canvas region that displays a region of the application canvas on the screen and can be manipulated by the mobile application user to view hidden parts of the application canvas.
  • the mobile application designer may choose to add an application canvas region that overlays another application canvas region and can be viewed or hidden on the device by an action performed by the mobile application user, such a tapping on the device screen.
  • the mobile application designer may customize an application canvas by changing properties of the application canvas or the application canvas regions, such as by changing the color of the application canvas or canvas region, or by adjusting the height or width of the application canvas regions.
  • the mobile application designer may customize the application canvas through several methods, including but not limited to, triggering a contextual menu that displays options such as adding or deleting application canvas regions, dragging control bars that resize application canvas regions, or control panels that display application canvas or application canvas region properties that may include, but are not limited to, transition animations when the application canvas is shown or hidden, or background color and color selection tools for updating the background color. It should be understood that these embodiments are illustrative, and should not be construed as being limiting in any way.
  • the mobile application designer may also add, delete, and customize elements on the application canvas or regions of the application canvas. These may include, but are not limited to, gesture recognizer elements such as buttons or tabs, or display elements such as text or images. These elements can be configured to display data specified as part of the application canvas configuration. The elements can also be populated with data pulled into the mobile application, such as a Facebook or RSS feed, or a collection of data records managed through another part of the development system 102. The mobile application designer may add these elements to an application canvas by interacting with the design canvas 122 to drag boxes representing the elements from a toolbox portion of the screen to the application canvas portion of the screen.
  • the mobile application designer may also add elements by interacting with the design canvas 122, which can display a representation of the application canvas or regions of the application canvas, such as by right-clicking on a tab bar to add or a remove a tab from the tab bar.
  • the mobile application designer may customize the element by dragging the element to reposition the element on the design canvas 122, or by dragging control bars that resize the element.
  • the mobile application designer may also customize the element by triggering a contextual menu that displays options such as deleting the element, copying or pasting style elements from or to the element, as well as displaying additional information about the element, such as the element dimensions at different screen resolutions.
  • the mobile application designer may also customize the element by triggering a control panel that displays element properties including but not limited to whitespace, foreground color, background color, display images, actions performed when the mobile application user interacts with the element, or transition animations when actions are triggered by the mobile application user.
  • Elements may have maximum/minimum size properties assigned to them to assist the mobile application designer in sizing or creating their layout.
  • the sizes may be calculated such that when they appear on the mobile application they will size appropriately to the device.
  • the sizes can include, for example, a width of three hundred twenty pixels or other width that can be calculated such that the elements will shrink to fit a narrower display.
  • a height of the element can be set to show at the pixel height rather than stretching to fit the relative height of the device.
  • Device aspect ratio may represent a conversion or 1:1 of the element size on the device or can be converted to fit the different aspect ratios of a variety of devices, or may be set to convert one dimension while not converting the other dimension.
  • An element may also expand one dimension to accommodate variable content sizes, or may maintain dimensions and display only part of the content, possibly ending in an ellipsis to indicate to the mobile application user that more content may be available in another canvas view.
  • the design canvas 122 may include functionality for assisting a mobile application designer by providing or making use of tools that may be managed and saved to the development system 102.
  • the tools can include, but are not limited to, the provisioning of libraries of icons or images provided for the benefit of system accounts or by account specific libraries of icons or images that can be uploaded by application designers or other account users. These libraries may then be accessed via the design canvas 122 to choose images to display on the application canvas.
  • the mobile application designer may be provided with a field or other functionality for entering a web address, which may be accessed to retrieve colors in a CSS file, or the like, of a web property.
  • colors and/or colors schemes can be used to populate a custom pallet, upload a file containing a collection of color codes, for example, rgba color or hexadecimal color codes, or an input for pasting in a list of color codes.
  • a mobile application designer can set color schemes for the mobile application by simply entering a web address or other resource with access to a CSS file or the like. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the mobile application designer may add or delete colors in a custom color pallet to be used when updating colors of application canvases and/or elements.
  • the mobile application designer can be given an option to sort, reorder, or otherwise update the custom pallet, either at initialization of the mobile application or at some other time.
  • the development system 102 may also provide or allow the mobile application designer to create libraries of sets of stylistic configurations, for example, allowing the user to create a style for text titles or text content that specifies a specific font size, color, whitespace, etc, which can be accessed to apply to an element on an application canvas, thereby assisting the mobile application designer in quickly creating a consistent look and feel throughout the mobile application.
  • the design canvas 122 may also assist application designers in adhering to application design best practices.
  • This may include assigning maximum or minimum size properties to application canvases and/or elements, and may be dependent on other properties of the element or application canvas to which they are applied. For example, the mobile application designer may not be permitted to size a gesture recognizer element smaller than a specified height or width to ensure that the element is displayed at a size in which a user can interact with the element easily, i.e., such that the mobile application user does not experience difficulty or frustration in tapping a button or navigating between form fields. Another example may include preventing the mobile application designer from layering multiple gesture recognizer elements on top of each other and thus preventing the mobile application user from being able to access some of the gesture recognizer elements. It should be understood that these embodiments are illustrative, and should not be construed as being limiting in any way.
  • the design canvas 122 may also assist application designers by providing tip/hint content in conjunction with the application canvas. These tips may be presented to the mobile application designer in formats including but not limited to text, audio, or video. These tips may assist the mobile application designer by explaining such topics including but not limited to help in interacting with the design canvas 122 or the development system 102 overall, best practices for application design, or common practices for designing an application canvas associated with a specific set of functionality.
  • FIGURE 1 illustrates one development system 102, one network 104, one data source 112, and two or more mobile application versions 114. It should be understood, however, that some implementations of the operating environment 100 include multiple development systems 102, multiple networks 104, and/or multiple data sources 112, and can be used to generate a single version of a mobile application. Thus, the illustrated embodiments should be understood as being exemplary, and should not be construed as being limiting in any way.
  • FIGURE 2 aspects of another operating environment 200 for the various embodiments presented herein will be briefly described. It should be understood that the operating environment 200 can correspond to and/or include the development system 102 described herein, though this is not necessarily the case. As such, the described embodiment should be understood as being illustrative and should not be construed as being limiting in any way.
  • the operating environment 200 shown in FIGURE 2 includes a client application 202 such as a web browser or stand-alone application.
  • the operating environment 200 also includes one or more content and data providers 204 such as news feeds, data feeds, service and/data providers, or the like.
  • the client application 202 and/or the content and data providers 204 can be accessed by the development system 102 via the network 104.
  • the functionality of the development system 102 can be provided by a web server 206 that includes one or more application servers 208 and processes and logic 210.
  • the web server 206 can be configured to store or access data 212.
  • the data 212 can include, for example, various information associated with an application development platform for a user and/or organization.
  • the data 212 includes, but is not limited to, account profiles 214, user profiles 216, an application UI designer 218, an application configuration manager 220, an application content manager 222, an application functionality manager 224, and/or other information 226. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the account profiles 214 can include profile data for accounts associated with the development system 102.
  • the account profiles 214 can include data indicating available and/or blocked features, history information, or the like for a particular account. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the user profiles 216 can include profile data for users or organizations associated with the development system 102.
  • the user profiles 216 can include data indicating user names, user passwords or other authentication data, or the like for users. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the application UI designer 218 can include UIs for providing a design mode of application creation, as will be described herein in additional detail.
  • the application configuration manager 220 can include UIs for providing a configuration mode as will be described herein in additional detail.
  • the application content manager 222 can include UIs and/or data for providing a content management mode of operation as will be described herein in additional detail.
  • the application functionality manager 224 can include UIs and/or data for controlling application functionality as will be described in additional detail herein.
  • the other information 226 can be any other information such as, for example, modules, user data, color schemes, or the like that may be used by the development system 102. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the modules 116 include a social media module.
  • the social media module can include, but is not limited to, functionality for setting- up, viewing, sharing, and/or editing social networking media feeds; enabling or disabling various social networking functions; configuring views for displaying social networking data; and/or controlling various other features of social networking.
  • Contemplated social media services can include, but are not limited to, the FACEBOOK social networking service, the TWITTER realtime messaging service, the YOUTUBE video service, other services, RSS feeds, combinations thereof, or the like.
  • Various social networking services and/or other services can be interfaced with using the concepts and technologies disclosed herein. As such, it should be understood that the illustrated embodiment is illustrative, and should not be construed as being limiting in any way.
  • the modules 116 include a list module that can include, but is not limited to, features for creating lists for the mobile application. Via the list module, users or other entities can configure page titles, list view field options, detail view field options, filter options, categories, sort orders, and sharing options associated with lists on the mobile application. The user also can configure various views of the lists, add/edit items in the lists, and take other actions, even post-deployment. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the modules 116 can include a push notification module.
  • the push notifications module can be used to enable push notifications and/or to control push notifications.
  • the push notification module can include functionality for generating, scheduling, and sending push notifications to users of the mobile applications.
  • the push notifications module also can be used to add push notification services to a back office associated with the user account, via which the user can create push notifications for the mobile application. Additional details of the back office component of the push notifications functionality are discussed below. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the modules 116 can include a surveys module.
  • the surveys module include, but is not limited to, functionality for creating surveys for presentation via the mobile application. Users can name the survey; set begin and expiration dates for the survey; provide instructions to users; provide a survey question, answer options, and options for adding answers and survey questions; provide an option and associated functionality for completing the survey; and a cancel button that can include, among other features, a pop-up box warning of cancellation; and the like.
  • the surveys module also can include a back office component that presents survey results to the user. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the modules 116 include an action alert module.
  • the action alert module can include, but is not limited to, features for creating functionality for taking various types of action via the mobile application.
  • users can create an action item; define alert types such as email, phone calls, donations, education, notifications, or other action; set action dates; describe the action; and assign various actions to the set action types such as, for example, tap to call, tap to email, and the like.
  • the action alert module can be used to provide additional alert- type-specific options. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • FIGURES 3A-3E various user interfaces provided by the development system 102 are shown, according to illustrative embodiments. It should be understood that the illustrated user interfaces are illustrative and should not be construed as being limiting in any way.
  • the design canvas 122 can be presented as a user interface that represents an application canvas, i.e., a dimensioned presentation area for a mobile application, a web page, print media, or the like.
  • an application canvas i.e., a dimensioned presentation area for a mobile application, a web page, print media, or the like.
  • the application, web page, print media, or other project will be described as a mobile application. Because the concepts and technologies disclosed herein can be used to develop other types of media and/or projects, it should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the design canvas 122 can include and/or can represent a screen real estate or part thereof.
  • the design canvas 122 can be generically dimensioned to enable users to establish or edit dimensions for the mobile application.
  • the design canvas 122 also can be used to dynamically adjust a resulting presentation area of the mobile application based upon known or expected device screen dimensions.
  • the design canvas 122 can be segmented into discreet functional and nonfunctional display areas, and segments included in the mobile application (as displayed in the design canvas 122) can be edited or removed via the design canvas 122.
  • users may place tools on the design canvas 122, edit tools in the design canvas 122, and/or remove tools from the design canvas 122 and/or areas or segments thereof.
  • the design canvas 122 can be generated and presented by the development platform, and the development platform can be configured to track, store, and use placement locations and/or other configuration information about the design canvas 122 to build a mobile application.
  • the design platform can monitor splits, segments, tool placement, for the like, in the design canvas 122 to supply and direct build, rebuild, update processes, or the like with respect to the mobile application developed using the development platform.
  • the design canvas 122 also can be configured to maintain and/or enforce various rules and/or standards.
  • the design canvas 122 can maintain and/or enforce rules or standards for best practices, design guidelines, compliance information, various interactions, combinations thereof, or the like.
  • FIGURE 3A illustrates a screen display 300A that can be presented to allow a user to present a design canvas 122, according to one embodiment.
  • the design canvas 122 can be presented in a screen display 300A as a design canvas display 302.
  • the screen display 300A can be presented on various devices such as, for example, a personal computer, a smart phone, or the like.
  • the screen display 300A is generated via a web interface with the development system 102. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the design canvas display 302 which can correspond to an application canvas of a mobile application, can be presented in the screen display 300A.
  • the screen display 300A also can include a toolbox 304 for adding text, images, video, touch controls or gesture controls, buttons, lists, other elements, or the like. Users can interact with the screen display 300A, and thereby the design canvas 122, to add elements (including, but not limited to, tabs and navigation) to the mobile application. Users can select any, all, none or any combination of these elements. Upon selection of an element, the selected element can be placed into the design canvas display 302 at a predetermined location, at a best-practice- recommended location, at a user customized location, and/or at another location.
  • FIGURE 3B illustrates addition of an element to the design canvas and display of a canvas setup screen 306, which can ask a user if additional elements are to be added to the design canvas 122. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • FIGURE 3C illustrates a screen display 300C that can be presented to allow a user to configure a mobile application using the development system 102.
  • the design canvas 122 can be split in a number of ways.
  • the design canvas 122 can be split by using a context-sensitive menu structure, by using system-generated structure, and/or by using a template-based structure.
  • the design canvas 122 can be split proportionally (e.g., bisected), randomly, in accordance with particular designs and/or external considerations, based upon user input, based upon geometric and/or free form considerations, iteratively, or the like.
  • regions 308A-C of the design canvas 122 and/or the design canvas display 302 can be manipulated by users.
  • Supported manipulations include movement, resizing, deletion, merging, splitting, exporting, saving, importing, duplicating, copying, other manipulations, or the like.
  • the regions 308 can be manipulated, if desired, by manipulating region border controls 310A-B. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • FIGURE 3D illustrates a screen display 300D that can be presented to allow a user to configure a mobile application using the development system 102.
  • the toolbox 304 can include various elements or tools such as, for example, buttons, labels, web views, code segments and snippets, widgets, lists, media, etc. Each tool may consist of the tool functionality codified, its interfaces, resources, configuration, etc.
  • the toolbox 304 may be segmented based on various criteria, including but not limited to, functionality type, alphabetical sorting, user preferences, enterprise design, business requirements, account status, etc.
  • Tools may be populated or may be restricted from the toolbox 304 based on various criteria, including but not limited to, availability from developers, applicability for use, regulatory requirements, subscription level, device, etc. Tools may be edited/configured for themes, icons, verbiage, data, requirements, order, etc. Because additional and/or alternative information can be included in the screen display 300D, it should be understood that the illustrated embodiment is illustrative, and should not be construed as being limiting in any way
  • FIGURE 3E illustrates a screen display 300E that can be presented to allow a user to configure a mobile application using the development system 102.
  • users can place tools on the design canvas 122 and/or regions 308 thereof.
  • the development system 102 can support drag-and-drop of the elements, a context menu structure, a template import, a system generated (e.g., structured or random) approach, or the like.
  • the tool may be represented in the design canvas display 302 as an icon 312 or as the actual tool representation.
  • the tools may be edited/configured for themes, icons, verbiage, data, requirements, order, external feeds, etc.
  • the tools also can be manipulated within the design canvas display 302. Some possible manipulations include, but are not limited to, movement, resizing, deletion, merging, exporting, saving, importing, duplication, copying, linking, combinations thereof, or the like.
  • the design canvas 122 also may be used for creating, editing, importing, linking, etc. page themes; adding, removing, reordering pages, interfaces, or the like; setting and/or applying theme inheritance; capturing themes from external source material to establish theme or an alternative for the current work product; capturing themes from external source material to create theme baseline, template, etc.; quality assurance, user acceptance and preference testing; cross-platform modeling, production, or integration; combinations thereof; or the like.
  • cross-platform may be used to refer to various platforms and/or environments including, but not limited to, mobile websites, web applications, conventional websites, desktop applications, print media, etc. These platforms may be viewed and/or implemented on numerous computing and related devices. Because additional and/or alternative information can be included in the screen display 300E, it should be understood that the illustrated embodiment is illustrative, and should not be construed as being limiting in any way.
  • FIGURE 4 aspects of a method 400 for developing a mobile application using a design canvas 122 will be described in detail. It should be understood that the operations of the method 400 are not necessarily presented in any particular order and that performance of some or all of the operations in an alternative order(s) is possible and is contemplated. The operations have been presented in the demonstrated order for ease of description and illustration. Operations may be added, omitted, and/or performed simultaneously, without departing from the scope of the appended claims.
  • the illustrated method 400 can be ended at any time and need not be performed in their respective entireties. Some or all operations of the methods disclosed herein, and/or substantially equivalent operations, can be performed by execution of computer-readable instructions included on a computer-storage media, as defined herein, and/or via execution of logic via various hardware incorporated into one or more logic circuits or other devices.
  • Computer-readable instructions can be implemented on various system configurations, including single -processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor- based, programmable consumer electronics, combinations thereof, and the like.
  • the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within a computing system or another device.
  • the implementation is a matter of choice dependent on the performance and other requirements of the computing system or other device.
  • the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules. These operations, structural devices, acts, and modules may be implemented in software, in firmware, in special purpose digital logic, in special purpose analog logic or other hardware, and/or in any combination thereof.
  • the method 400 is described as being performed by the development system 102 via execution of one or more application programs such as, for example, the application development module 108.
  • the development system 102 can include and/or can be configured to execute additional and/or alternative application programs.
  • devices other than the development system 102 can be configured to provide the functionality described herein with respect to FIGURE 4 by way of executing various application programs.
  • the illustrated embodiments should be understood as being illustrative, and not limiting in any way of the concepts and technologies disclosed herein.
  • the method 400 begins at operation 402, wherein the development system 102 creates a mobile application and creates a design canvas 122 associated with the mobile application.
  • the design canvas 122 may not be saved until the application design space is saved.
  • creating the design canvas 122 can correspond, in some embodiments, to creating a screen display or other user interface 120, which can include a design canvas display 302 associated with a design canvas 122. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.
  • the method 400 proceeds to operation 406, wherein the development system 102 detects selection of a control within a user interface 120 to add an element to the design canvas 122.
  • the functionality shown in operation 404 can correspond to detecting selection of an option to add a tool, a module 116, and/or other elements to a mobile application, for example via selection of a control in the toolbox 304 discussed above. It should be understood that these embodiments are illustrative, and should not be construed as being limiting in any way.
  • the method 400 proceeds to operation 408, wherein the development system 102 configures the element added in operation 406.
  • a user such as an application designer may customize the element by dragging the element to reposition the element on the design canvas 122 or within the design canvas display 302, or by dragging control bars that resize the element.
  • the user may also customize the element by triggering a contextual menu that displays options such as deleting the element, copying or pasting style elements from or to the element, as well as displaying additional information about the element, such as the element dimensions at different screen resolutions.
  • the user may also customize the element by triggering a control panel that displays element properties including but not limited to whitespace, foreground color, background color, display images, actions performed when the mobile application user interacts with the element, or transition animations when actions are triggered by the mobile application user. It should be understood that these embodiments are illustrative, and should not be construed as being limiting in any way.
  • the method 400 proceeds to operation 410, wherein the development system 102 determines if the application canvas or the design canvas 122 corresponding thereto has been split. As explained above, a user may enter a command for splitting the design canvas 122 by way of various controls. Thus, operation 408 can correspond to determining if such a command or selection of such a control has been detected. If the development system 102 determines, in operation 408, that the design canvas 122 has been split, the method 400 proceeds to operation 410.
  • the development system 102 can determine if the new region 308 created in operation 408 is to have the same properties as the original design canvas 122 or a region 308 from which the new region 308 is being created. If the development system 102 determines that the new region 308 is not to have the same properties as the original design canvas 122 or region 308 from which the new region 308 is formed, the method 400 proceeds to operation 412.
  • the development system 102 can obtain input for setting the properties of the new region 308 created in operation 408.
  • the properties e.g., color schemes, fonts, controls, etc.
  • the method 400 proceeds to operation 414.
  • the method 400 also can proceed to operation 414 if the development system 102 determines, in operation 410, that the new region 308 is to have the same properties as the original design canvas 122 or region 308 from which the new region 308 is formed.
  • the development system 102 can create the region(s) 308 in accordance with appropriate properties.
  • the method 400 proceeds to operation 416, wherein the development system 102 determines if the application design is complete.
  • the method 400 also can proceed to operation 416 from operation 408, if the development system 102 determines that a command for splitting the design canvas 122 has not been detected.
  • the method 400 can return to operation 404. Operations 404-416 can be repeated until the development system 102 determines, in any iteration of operation 416, that the application design is complete. If the development system 102 determines that the application design is complete, the method 400 proceeds to operation 418.
  • the development system 102 can compile and output the mobile application and/or one or more versions thereof such as the mobile application versions 114. From operation 418, the method 400 proceeds to operation 420. The method 400 ends at operation 420.
  • FIGURE 5 an illustrative computer architecture 500 for a computing device capable of executing software components described herein for a design canvas will be described in detail.
  • the computer architecture 500 shown in FIGURE 5 illustrates an embedded control computer, a desktop computer, a laptop computer, a server computer, a cellular telephone, a smart phone, a PDA, combinations thereof, and the like, and can be configured to execute aspects of the software components presented herein.
  • a device having an architecture similar to the computer architecture 500 of FIGURE 5 may serve as the development system 102 and/or a device in communication with the development system 102. It should be appreciated that the described software components can also be executed on other example computing environments.
  • the computer architecture 500 includes a central processing unit 502 (CPU), a system memory 504, which includes a random access memory (RAM) 506 and a read-only memory (ROM) 508, and a system bus 510 that can couple the system memory 504 to the CPU 502.
  • the computer architecture 500 may further include a mass storage device 512.
  • the mass storage device 512 can store the operating system 106, as well as other software, data, and various program modules. In the illustrated embodiment, the mass storage device 512 stores the application development module 108, the module library 118, and the user interfaces 120.
  • modules 116 can be stored as part of the module library 118 and, therefore, by the mass storage device 512. Execution of the application development module 108 by the CPU 502 can cause a computing system embodying the computer architecture 500 to provide functionality such as that described herein.
  • the mass storage device 512 can be connected to the CPU 502 through a mass storage controller (not shown) connected to the bus 510.
  • the mass storage device 512 and its associated computer-readable media can provide non-volatile storage for the computer architecture 500.
  • computer-readable media can be any available computer storage media or communication media that can be accessed by the computer architecture 500.
  • Communication media includes computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any delivery media.
  • modulated data signal means a signal that has one or more of its characteristics changed or set in a manner as to encode information in the signal.
  • communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (“RF”), infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer- readable media.
  • computer storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data.
  • computer media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD- ROM, digital versatile disks ("DVD"), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer architecture 500.
  • DVD digital versatile disks
  • HD-DVD high definition digital versatile disks
  • BLU-RAY blue ray
  • computer storage medium does not include waves, signals, and/or other transitory and/or intangible communication media, per se.
  • a computing system embodying the computer architecture 500 may operate in a networked environment using logical connections to remote computers through a network such as the network 104.
  • the computing system embodying the computer architecture 500 may connect to the network 104 through a network interface unit 514 connected to the bus 510. It should be appreciated that the network interface unit 514 may also be utilized to connect to other types of networks and remote computer systems.
  • the computing system embodying the computer architecture 500 may also include an input/output controller 516 for receiving and processing input from a number of other devices, including a keyboard, mouse, or electronic stylus (not illustrated). Similarly, the input/output controller 516 may provide output to a video display, a printer, or other type of output device (also not illustrated).
  • a number of program modules and data files may be stored in the mass storage device 512 and RAM 506 of a computing system embodying the computer architecture 500.
  • the program modules and data files include, but are not limited to, the operating system 106 suitable for controlling the operation of a desktop computer, laptop computer, server computer, mobile telephone, and/or other computing device or environment.
  • the mass storage device 512, ROM 508, and RAM 506 may also store one or more program modules.
  • any of the mass storage device 512, the ROM 508, and the RAM 506 may store the application development module 108 for execution by the CPU 502.
  • the mass storage device 512, the ROM 508, and the RAM 506 may also store other types of program modules and/or data including, but not limited to, the application data 110, the modules 116, the module library 118, the user interfaces 120, and/or the mobile application versions 114.
  • Software modules such as the application development module 108 may be associated with the system memory 504, the mass storage device 512, or other data storage.
  • the application development module 108 may include software instructions that, when loaded into the CPU 502 and executed, transform a general-purpose computing system into a special-purpose computing system customized to facilitate all, or part of, the techniques for identifying backup coverage in a wireless network as disclosed herein.
  • the program modules may provide various tools or techniques by which the computing system embodying the computer architecture 500 may participate within the overall systems or operating environments using the components, logic flows, and/or data structures discussed herein.
  • the CPU 502 may be constructed from any number of transistors or other circuit elements, which may individually or collectively assume any number of states. More specifically, the CPU 502 may operate as a state machine or finite-state machine. Such a machine may be transformed to a second machine, or specific machine by loading executable instructions contained within the program modules. These computer- executable instructions may transform the CPU 502 by specifying how the CPU 502 transitions between states, thereby transforming the transistors or other circuit elements constituting the CPU 502 from a first machine to a second machine, wherein the second machine may be specifically configured to support real time event driven energy management.
  • the states of either machine may also be transformed by receiving input from one or more user input devices associated with the input/output controller 516, the network interface unit 514, other peripherals, other interfaces, or one or more users or other actors.
  • Either machine may also transform states, or various physical characteristics of various output devices such as printers, speakers, video displays, or otherwise.
  • Encoding of the program modules may also transform the physical structure of the storage media.
  • the specific transformation of physical structure may depend on various factors, in different implementations of this description. Examples of such factors may include, but are not limited to: the technology used to implement the storage media, whether the storage media are characterized as primary or secondary storage, and the like.
  • the program modules may transform the physical state of the system memory 504 when the software is encoded therein.
  • the software may transform the state of transistors, capacitors, or other discrete circuit elements constituting the system memory 504.
  • the storage media may be implemented using magnetic or optical technology.
  • the program modules may transform the physical state of magnetic or optical media, when the software is encoded therein. These transformations may include altering the magnetic characteristics of particular locations within given magnetic media. These transformations may also include altering the physical features or characteristics of particular locations within given optical media, to change the optical characteristics of those locations. It should be appreciated that various other transformations of physical media are possible without departing from the scope and spirit of the present description.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

L'invention porte sur des concepts et sur des technologies pour un canevas de conception devant être utilisé dans le développement d'une application mobile. Selon les concepts et les technologies décrits dans l'invention, un système de développement peut recevoir une entrée pour créer une application mobile et pour créer un espace de travail d'application et un canevas de conception, en réponse à la réception de l'entrée. Le système de développement peut afficher une représentation du canevas de conception dans une interface utilisateur. La représentation peut comprendre un affichage du canevas de conception. Le système de développement peut également recevoir une entrée supplémentaire pour ajouter un élément à l'application mobile, pour ajouter l'élément au canevas de conception, en réponse à la réception de l'entrée, et pour configurer l'élément dans l'interface utilisateur.
PCT/US2013/022106 2012-01-18 2013-01-18 Canevas de conception WO2013109858A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201261587831P 2012-01-18 2012-01-18
US61/587,831 2012-01-18
US201261658540P 2012-06-12 2012-06-12
US61/658,540 2012-06-12

Publications (1)

Publication Number Publication Date
WO2013109858A1 true WO2013109858A1 (fr) 2013-07-25

Family

ID=48799675

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/022106 WO2013109858A1 (fr) 2012-01-18 2013-01-18 Canevas de conception

Country Status (1)

Country Link
WO (1) WO2013109858A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9582225B2 (en) 2015-03-27 2017-02-28 Kyocera Document Solutions Inc. Document solution management platform in a decentralized environment
US20190287284A1 (en) * 2018-03-16 2019-09-19 Ali Ispahany Method of creating mobile applications
CN110471656A (zh) * 2018-05-10 2019-11-19 北京京东尚科信息技术有限公司 组件层级的调整方法和装置
CN112463602A (zh) * 2020-11-24 2021-03-09 上海哔哩哔哩科技有限公司 用户界面测试方法及系统
CN114579004A (zh) * 2022-03-09 2022-06-03 北京百度网讯科技有限公司 流程画布的生成方法、装置和电子设备
CN115202525A (zh) * 2022-07-14 2022-10-18 深圳视界信息技术有限公司 一种基于画布设置问卷的方法、装置、设备及介质
CN115544605A (zh) * 2022-11-25 2022-12-30 深圳小库科技有限公司 生成建筑空间的方法、云平台及计算机可读存储介质
CN117033844A (zh) * 2023-10-07 2023-11-10 之江实验室 一种画布元素布局方法、装置、存储介质及电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050066287A1 (en) * 2003-09-11 2005-03-24 Tattrie Scott I. User-friendly data binding, such as drag-and-drop data binding in a workflow application
US20060248506A1 (en) * 2005-04-18 2006-11-02 Research In Motion Limited System and method for flexible visual representation of device fonts
US20110154287A1 (en) * 2009-12-18 2011-06-23 Sybase, Inc. Visual Generation of Mobile Applications Based on Data Models

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050066287A1 (en) * 2003-09-11 2005-03-24 Tattrie Scott I. User-friendly data binding, such as drag-and-drop data binding in a workflow application
US20060248506A1 (en) * 2005-04-18 2006-11-02 Research In Motion Limited System and method for flexible visual representation of device fonts
US20110154287A1 (en) * 2009-12-18 2011-06-23 Sybase, Inc. Visual Generation of Mobile Applications Based on Data Models

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SOROKER ET AL.: "Pegboard: A Framework for Developing Mobile Applications.", 22 June 2006 (2006-06-22), XP001541420, Retrieved from the Internet <URL:http://static.usenix.org/events/mobisys06/full_papers/p138-soroker.pdf> [retrieved on 20130304] *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9582225B2 (en) 2015-03-27 2017-02-28 Kyocera Document Solutions Inc. Document solution management platform in a decentralized environment
US20190287284A1 (en) * 2018-03-16 2019-09-19 Ali Ispahany Method of creating mobile applications
CN110471656A (zh) * 2018-05-10 2019-11-19 北京京东尚科信息技术有限公司 组件层级的调整方法和装置
CN112463602A (zh) * 2020-11-24 2021-03-09 上海哔哩哔哩科技有限公司 用户界面测试方法及系统
CN114579004A (zh) * 2022-03-09 2022-06-03 北京百度网讯科技有限公司 流程画布的生成方法、装置和电子设备
CN115202525A (zh) * 2022-07-14 2022-10-18 深圳视界信息技术有限公司 一种基于画布设置问卷的方法、装置、设备及介质
CN115544605A (zh) * 2022-11-25 2022-12-30 深圳小库科技有限公司 生成建筑空间的方法、云平台及计算机可读存储介质
CN117033844A (zh) * 2023-10-07 2023-11-10 之江实验室 一种画布元素布局方法、装置、存储介质及电子设备
CN117033844B (zh) * 2023-10-07 2024-01-16 之江实验室 一种画布元素布局方法、装置、存储介质及电子设备

Similar Documents

Publication Publication Date Title
US11797273B2 (en) System and method for enhancing component based development models with auto-wiring
WO2013109858A1 (fr) Canevas de conception
US9360992B2 (en) Three dimensional conditional formatting
CN111522552B (zh) 子应用生成方法、装置、计算机设备和存储介质
US20100235806A1 (en) Rich Web Site Authoring And Design
US9959257B2 (en) Populating visual designs with web content
JP2016224923A (ja) ユーザフォームインタフェースの自動生成の方法およびシステム
CN108228253A (zh) 一种app构建方法及系统
US20160380915A1 (en) Rules-Based Workflow Messaging
US20140047409A1 (en) Enterprise application development tool
US10019424B2 (en) System and method that internally converts PowerPoint non-editable and motionless presentation mode slides into editable and mobile presentation mode slides (iSlides)
Murphy et al. Beginning Android 3
US20250047735A1 (en) System and Method to Standardize and Improve Implementation Efficiency of User Interface Content
Allen et al. Beginning Android 4
CN111679818A (zh) 编辑展示软件的方法和系统
JP2020524837A (ja) ウェブサイトコンポーネント相互間におけるスマートインタラクションのためのシステム及び方法
US20110023014A1 (en) Method and apparatus for modifying an executable application using in-memory object representation
CN116931895A (zh) 一种复合组件的处理方法、装置及设备
CN113326044A (zh) 一种基于控件库的开发方法、系统及存储介质
CA2686367A1 (fr) Facade de visualisation de code de logiciel pour editeur dynamique en langage natif
US8438539B2 (en) Using a menu slideshow framework for generating a custom menu-driven slideshow containing definable content
CN115145545A (zh) 小程序代码的生成方法、装置、计算机设备和存储介质
Cimino et al. An efficient model-based methodology for developing device-independent mobile applications
CN113704593B (zh) 一种运营数据处理方法及相关装置
CN114217877A (zh) 基于页面交互组件的操作处理方法、装置、设备及介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13738913

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13738913

Country of ref document: EP

Kind code of ref document: A1