Customization framework for native mobile applications
A native user interface (UI) application of a mobile device includes a library of different components such as text, forms, tables, lists, maps, views and buttons. The components can also have associated actions in some cases. When a view of the UI is launched, the mobile device contacts a server or other data source to obtain metadata associated with the view. The metadata can be tailored to a user or organization of the mobile device. The metadata selects specific components and defines a layout for the components. The mobile device uses the metadata to retrieve the components and render them in the view. The views can be changed by changing the metadata without changing the native application.
1 . An apparatus, comprising:
one or more processors; and
a non-transitory machine-readable storage medium that provides instructions that, when executed by the one or more processors, configures the apparatus to perform operations comprising, at a native application of a computing device:
launching a view of a user interface (UI) of the native application;
in response to the launching, sending a request which identifies the view to a metadata service;
receiving metadata from the metadata service in response to the request, wherein the metadata identifies one or more components of the native application and specifies a layout of the one or more components;
receiving a definition from a registry of providers, wherein a first component of the one or more components is mapped from the received definition; and
rendering the one or more components, including the first component, in one or more positions in the view according to the layout.
2 . The apparatus of claim 1 , wherein the rendering comprises selecting a display parameter from among a plurality of available display parameters of the one or more components according to the metadata.
3 . The apparatus of claim 2 , wherein the display parameter comprises at least one of a font size, a font type, a color and a list size.
4 . The apparatus of claim 1 , wherein the one or more components comprise static components.
5 . The apparatus of claim 1 , wherein the one or more components comprise data-bound components.
6 . The apparatus of claim 1 , wherein the one or more components comprise plugin components.
7 . The apparatus of claim 1 , wherein the operations performed at the native application further comprise nesting one component within another component according to the metadata which specifies that the layout.
8 . The apparatus of claim 1 , wherein the one or more components are hard coded into the native application.
9 . The apparatus of claim 1 , wherein the operations performed at the native application further comprise: while loading data of the one or more components, displaying a stencil at the one or more positions in the view.
10 . A non-transitory machine-readable storage medium that provides instructions that, when executed by one or more processors, configures the one or more processors to perform operations comprising:
receiving a request from a native application of a computing device, the request identifies a view of a user interface (UI) of the native application;
in response to the request, accessing metadata corresponding to the view, wherein the metadata identifies one or more components of the native application and specifies a layout of the one or more components;
receiving a definition from a registry of providers, wherein a first component of the one or more components is mapped from the received definition; and
transmitting the metadata, including the first component, to the native application.
11 . The non-transitory machine-readable storage medium of claim 10 , wherein the accessing the metadata comprises accessing a database having different metadata corresponding to different views, and identifying the metadata corresponding to the view based on an identifier of the view in the request.
12 . The non-transitory machine-readable storage medium of claim 10 , wherein the accessing the metadata comprises accessing a multi-tenant database having different metadata for different tenants, and identifying the metadata corresponding to a tenant of the native application.
13 . The non-transitory machine-readable storage medium of claim 10 , wherein the operations performed further comprise:
receiving requests identifying views of UIs from multiple instances of the native application; and
performing a machine learning to identify usage patterns of the UIs based on the requests.
14 . The non-transitory machine-readable storage medium of claim 10 , wherein the operations performed further comprise:
receiving and storing updated metadata for the view; and
transmitting the updated metadata to the native application in response to a subsequent request from the native application of the computing device for metadata for the view of the UI.
15 . The non-transitory machine-readable storage medium of claim 10 , wherein the metadata specifies at least one of a font size, a color and a list size for the view.
16 . The non-transitory machine-readable storage medium of claim 10 , wherein the metadata corresponding to the view is updatable.
17 . A method, comprising:
launching a view of a user interface (UI) of a native application;
in response to the launching, sending a request which identifies the view to a metadata service;
receiving metadata from the metadata service in response to the request;
based on the metadata, accessing from the native application, a parent component and a selected child component which is selected from among a plurality of different types of available child components of the native application;
receiving a definition from a registry of providers, wherein a first component of the one or more components is mapped from the received definition; and
rendering the parent component and the selected child component in the view according to the metadata, and rendering the first component in the view.
18 . The method of claim 17 , wherein the parent component comprises a list and the selected child component comprises a row in the list, and the plurality of different types of available child components comprise different types of rows.
19 . The method of claim 17 , wherein the metadata identifies the selected child component based on a user of the native application.
20 . The method of claim 17 , wherein the rendering comprises displaying the parent component and the selected child component in positions in the view which are specified by the metadata.