Abstract: Systems, devices and methods directed to operation of a point of sale (PoS) device during network connectivity to a cloud server, as well as during network outages and/or interruptions. The POS device can process transactions in a seamless manner even during network outages and/or interruptions. A POS application that runs on a POS device in an “online” mode can automatically detect an interruption in network connectivity, and switch to an “offline” mode. In the offline mode, the POS device can continue to process transactions and/or conduct other activities.

Abstract: The methods and apparatuses described herein generally relate to providing a platform for allowing a website user to select a product for purchase at a non-merchant website. For example, a commerce engine can receive a request to review product information from a non-merchant website, and can translate the request into a format that can be understood by at least one merchant server using at least one type of commerce platform. The commerce engine can send the translated requests to at least one merchant server, and the merchant servers that receive the requests can determine information about the product (e.g., remaining inventory at particular merchants, product price, and/or other product details). The merchant servers can provide this information to the commerce engine, which can send the product information to the non-merchant website. The commerce engine can also facilitate a transaction with the merchant server, based on the product information returned by the non-merchant website.

Abstract: A non-transitory processor-readable medium storing code representing instructions to be executed by a processor. The code causes the processor to send a signal to a compute device such that a first graphical user interface is rendered at the compute device via a dynamic form builder. The code causes the processor to receive, via the first graphical user interface, a set of inputs associated with a set of questions and a set of layout settings. The code causes the processor to generate, based on the set of inputs, a platform-agnostic configuration application data structure. The code causes the processor to send the platform-agnostic configuration application data structure to an application on a mobile device, causing the mobile device to render a second graphical user interface. The second graphical user interface includes a dynamic form configured to receive at least one response to a question from the set of questions.

Abstract: The methods and apparatuses described herein generally relate to providing a platform for allowing a website user to select a product for purchase at a non-merchant website. For example, a commerce engine can receive a request to review product information from a non-merchant website, and can translate the request into a format that can be understood by at least one merchant server using at least one type of commerce platform. The commerce engine can send the translated requests to at least one merchant server, and the merchant servers that receive the requests can determine information about the product (e.g., remaining inventory at particular merchants, product price, and/or other product details). The merchant servers can provide this information to the commerce engine, which can send the product information to the non-merchant website. The commerce engine can also facilitate a transaction with the merchant server, based on the product information returned by the non-merchant website.

Abstract: The methods and apparatuses disclosed herein generally relate to optimizing the creation and loading of application interface layouts by providing a platform for generating configuration files for mobile applications. A mobile configuration file can allow a developer to update an application layout, and for the application to render updated layouts, without any need to alter the underlying code of the application after it has been installed on the a client device. A mobile workbench receives drag-and-drop layout definition input from a developer, and creates a mobile configuration file based on the developer's input. The mobile workbench can then dynamically update the mobile configuration file as the developer updates the application layout. The developer and/or the mobile workbench can send the updated application layout to mobile applications running on client devices, such that the client devices need not redownload the mobile application to render the updated application layout.