Block, Inc.

Weebly, Inc.

Square, Inc.

Vitaly Odemchuk

Katherine Swett

Xuanhua Ren

Drew Richards

Neil Straghalis

Wael Al-Sallami

Daniel Veltri

Christine Loh

Philip Goolkasian

Brandon Labbe

Shaun Forouzandeh

Benjamin A Bloch

Lisa Fong

Katherine Ahn

Medum Choe

Ryan J Glasgow

Darian Shimy

David Pearson

Joseph Boudreau

Bryan Ashley

Jocelyn Fu

Jeffrey Scott Broderick

Techniques described herein are directed to centralized brand asset management. In an example, a first computing device associated with a first point-of-sale (POS) service can receive an instruction to update a web page of a merchant, wherein the instruction to update the web page of the merchant changes a brand asset of the merchant. The first computing device can send a request to update the brand asset of the merchant to a centralized data storage storing one or more brand assets of one or more merchants. The centralized data storage can update the brand asset to an updated brand asset, which can be available to at least a second computing device associated with a second POS service. The second POS service can update a respective POS service feature based on the updated brand asset.

Centralized brand asset management

Techniques described herein are directed to centralized identities for personalization of data presentation. A centralized identity is generated when similar user identifiers as stored across resources are determined. The centralized identity associates the user identifiers with each other and allows for user-related data from the multiple disparate resources to be queried and received. This user-related data can then be utilized to determine one or more personalizations to apply, and an application being used by the user may be modified to present the personalizations.

Centralized identity for personalization of data presentation

Techniques described herein are directed to application(s), or parts thereof, that are embedded into a buyer application. In an example, engagement with a buyer application on a computing device of a buyer can be detected. A particular, discrete functionality of a merchant application of the merchant can be triggered to be initialized in response to the engagement and the particular, discrete functionality associated with the merchant application can be accessed. In an example, an indication of a transaction between the merchant and the buyer can be received and the indication of the transaction can be associated with stored activity data of one or more transactions of the buyer, wherein the one or more transactions are associated with the buyer application.

Embedded application within a buyer application

Embedding applications, or parts thereof, into other applications, or parts thereof, is described. In an example, an engagement with a first application, or a part thereof, can be detected, which can trigger a second application, or a part thereof, to be initialized in response to the engagement. In at least one example, the first application, or a part thereof, can provisionally transfer to the second application, or a part thereof. Based at least in part on detecting a user interaction with the second application, or a part thereof, a portion of the user interaction can be embedded in the first application, or a part thereof, and the embedded portion of the user interaction can be presented via a user interface associated with the first application, or part thereof, via a user computing device.

Embedded applications

Customer-device application sites (e.g., content presented via a progressive web applications) that are accessible via merchant-managed identifiers (e.g., identification codes) are described. An identification of a physical location associated with a merchant can be associated with an identification code. The identification code can be received from a computing device of a customer and, based at least in part on receiving the identification code, merchant data associated with the merchant can be caused to be presented via a web browser of the computing device of the customer. In an example, the merchant data can be presented via the web browser by a progressive web application downloaded onto the computing device of the customer via the web browser. An indication of an input received via the progressive web application can be received by the computing device of the customer and an operation based at least in part on the input can be performed.

Customer-device application sites accessible via merchant-managed identifiers

A web editing application provides a user interface for editing a web page on a client computing device. A characteristic associated with the client computing device is determined. A web page comprising visual elements can be rendered. Layout data describing locations and sizes for individual visual elements of the visual elements can be determined. Cells can be generated based at least in part on the layout data and the characteristic associated with the client computing device. Each of the cells can have a location corresponding to a location of a respective visual element of the visual elements and individual of the cells can be interactable to enable editing of the web page. Based on an interaction with the at least one cell of the cells, an edit to the web page can be determined and the web page can be updated based on the edit to the web page.

User interface for editing web content

Using combined eCommerce and brick-and-mortar data to produce intelligent recommendations for web page operation is described. In an example, a request to access an eCommerce GUI presented on behalf of a merchant can be received from a device operable by a viewer. Brick-and-mortar point-of-sale (POS) transaction data associated with one or more customers that transact with the merchant or one or more other merchants that utilize the payment processing service to process brick-and-mortar POS transactions can be used to determine a variation of the eCommerce GUI presented on behalf of the merchant to present to the viewer. Instructions for rendering the variation of eCommerce GUI can be sent to the device operable by the viewer.

Using combined ecommerce and brick-and-mortar data to produce intelligent recommendations for web page operation

Using combined eCommerce and brick-and-mortar data to produce intelligent recommendations for website editing is described. In an example, brick-and-mortar transaction data associated with a first merchant and second merchant(s) can be compared to identify a subset of the second merchant(s) that are similar to the first merchant. Performance metrics associated with eCommerce graphical user interfaces (GUIs) presented on behalf of the subset of the second merchant(s) can be determined based on aggregated transaction data associated with eCommerce point-of-sale (POS) transactions associated with the subset of the second merchant(s) and a recommendation based on content, a layout, and/or a design of at least a portion of the eCommerce GUIs can be generated. The recommendation can be sent to a computing device operable by the first merchant for use in creating or editing an eCommerce GUI to be presented on behalf of the first merchant.

Using combined eCommerce and brick-and-mortar data to produce intelligent recommendations for web page editing

A web editing application provides a user interface for editing a web page on a mobile client device. The web editing application provides templates for user selection, and may allow users to edit web pages while the editing device is offline. The web editing application determines whether a display of the client device is in landscape mode or portrait mode, and arranges certain cells differently based on this determination. The web editing application may further provide cell configuration indicators that indicate cells that are arranged differently in different display modes.

A web editing server includes an app dashboard module that provides a dashboard user interface for presenting information provided by apps installed on users' websites. In one embodiment, the app dashboard module organizes the information as a series of cards, with each card providing information for an associated app. A user can select a card to obtain more information from the app. An app developer system allows an app developer to create and/or service an app in the app center. App developers may create cards by selecting one or more components from a card definition module. The app developer system may determine data attributes from received app data, which can be used to automatically create cards for the app dashboard.

Growing community of inventors

San Francisco, CA, United States of America

Vitaly Odemchuk