Granted Patent B2

US 12,321,726 · App. 18/761,232 · Granted Jun 3, 2025

Inventors: Nathan Mark Wittstock (Portland, OR); Ryan Lepinski (Portland, OR); Michael James Herrick (Portland, OR)

Assignee: Airship Group, Inc.

G06F8/38H04L51/214

Abstract

Claims (46)

1. A computer-implemented method, comprising:

receiving a design of in-application user interface elements (in-app UI elements) generated by a message publisher via a graphical user interface provided by a message management server, wherein the in-app UI elements comprise a series of messages, wherein the graphical user interface provided by the message management server simulates an appearance of the in-app UI elements that augment a software application, the software application developed by the message publisher;

converting the design of the in-app UI elements as a payload that includes configuration data of the in-app UI elements;

receiving, from a software development kit (SDK) associated with the message management server, an identifier that represents an instance of the SDK incorporated as part of the software application, and the SDK developed by the message management server;

receiving, from the message publisher, a trigger condition for displaying the in-app UI elements;

determining that the software application associated with the identifier matches the trigger condition;

generating, responsive to the trigger condition being met, the payload that includes the configuration data of the in-app UI elements; and

transmitting the message payload to the SDK, wherein the SDK uses the configuration data to render the in-app UI elements, wherein the in-app UI elements are rendered as the series of messages that cover at least a portion of the software application.

2. The computer-implemented method of claim 1 , wherein the configuration data is received from the message publisher through a portal provided by the message management server, and the graphical user interface is part of the portal.

3. The computer-implemented method of claim 1 , further comprising:

receiving a response from the SDK, the response corresponding to an interaction with rendered in-app UI elements by an end user in the software application and forwarded to the SDK.

4. The computer-implemented method of claim 3 , further comprising performing, by the message management server, an action based on the response.

5. The computer-implemented method of claim 1 , wherein the trigger condition is a mobile event.

6. The computer-implemented method of claim 1 , wherein the series of messages is a series of horizontally scrollable messages.

7. The computer-implemented method of claim 1 , wherein the series of messages is a series of application on-boarding messages.

8. A system, comprising:

a software development kit (SDK) included in a software application, the software application importing the SDK as part of the software application, the software application developed by a message publisher; and

a message management server in communication with the SDK, the SDK developed by the message management server, the message management server comprising one or more processors and memory configured to store computer code comprising instructions, the instructions, when executed by the one or more processors, cause the one or more processors to:

receive a design of in-application user interface elements (in-app UI elements) generated by the message publisher via a graphical user interface provided by the message management server, wherein the in-app UI elements comprise a series of messages, wherein the graphical user interface provided by the message management server simulates an appearance of the in-app UI elements that augment the software application, the software application developed by the message publisher;

convert the design of the in-app UI elements as a payload that includes configuration data of the in-app UI elements;

receive, from the SDK associated with the message management server, an identifier that represents an instance of the SDK incorporated as part of the software application, and the SDK developed by the message management server;

receive, from the message publisher, a trigger condition for displaying the in-app UI elements;

determine that the software application associated with the identifier matches the trigger condition;

generate, responsive to the trigger condition being met, the payload that includes the configuration data of the in-app UI elements; and

transmit the message payload to the SDK, wherein the SDK uses the configuration data to render the in-app UI elements, wherein the in-app UI elements are rendered as the series of messages that cover at least a portion of the software application.

9. The system of claim 8 , wherein the configuration data is received from the message publisher through a portal provided by the message management server, and the graphical user interface is part of the portal.

10. The system of claim 8 , wherein the instructions, when executed, further cause the one or more processors to:

receive a response from the SDK, the response corresponding to an interaction with rendered in-app UI elements by an end user in the software application and forwarded to the SDK.

11. The system of claim 10 , wherein the instructions, when executed, further cause the one or more processors to perform, by the message management server, an action based on the response.

12. The system of claim 8 , wherein the trigger condition is a mobile event.

13. The system of claim 8 , wherein the series of messages is a series of horizontally scrollable messages.

14. The system of claim 8 , wherein the series of messages is a series of application on-boarding messages.

15. A non-transitory computer-readable medium configured to store computer code comprising instructions, wherein the instructions, when executed by one or more processors, cause the one or more processors to:

receive a design of in-application user interface elements (in-app UI elements) generated by a message publisher via a graphical user interface provided by a message management server, wherein the in-app UI elements comprise a series of messages, wherein the graphical user interface provided by the message management server simulates an appearance of the in-app UI elements that augment a software application, the software application developed by the message publisher;

convert the design of the in-app UI elements as a payload that includes configuration data of the in-app UI elements;

receive, from a software development kit (SDK) associated with the message management server, an identifier that represents an instance of the SDK incorporated as part of the software application, and the SDK developed by the message management server;

receive, from the message publisher, a trigger condition for displaying the in-app UI elements;

determine that the software application associated with the identifier matches the trigger condition;

generate, responsive to the trigger condition being met, the payload that includes the configuration data of the in-app UI elements; and

transmit the message payload to the SDK, wherein the SDK uses the configuration data to render the in-app UI elements, wherein the in-app UI elements are rendered as the series of messages that cover at least a portion of the software application.

16. The non-transitory computer-readable medium of claim 15 , wherein the configuration data is received from the message publisher through a portal provided by the message management server, and the graphical user interface is part of the portal.

17. The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed, further cause the one or more processors to:

receive a response from the SDK, the response corresponding to an interaction with rendered in-app UI elements by an end user in the software application and forwarded to the SDK.

18. The non-transitory computer-readable medium of claim 17 , wherein the instructions, when executed, further cause the one or more processors to perform, by the message management server, an action based on the response.

19. The non-transitory computer-readable medium of claim 15 , wherein the trigger condition is a mobile event.

20. The non-transitory computer-readable medium of claim 15 , wherein the series of messages is a series of horizontally scrollable messages.

Assignments (1)

Continuity (3)

References Cited (81)