Messaging App Historical Item Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current messaging applications lack the ability to seamlessly integrate and re-engage users with historical interactions, such as links or advertisements, within ongoing conversations, which can lead to missed opportunities for commerce and user engagement.
Innovation Solution
A messaging application that requests and inserts historical items, including links and access mechanisms, from remote servers into messaging sessions, allowing users to re-engage with business applications by launching web browser or native applications directly from the messaging interface, enhancing user interaction and commerce opportunities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If messaging applications only provide basic communication functionality, then the application simplicity is maintained, but user engagement and commerce opportunities are limited
Solution Approach 1:
The patent combines messaging functionality with web browsing and native application access into a unified messaging interface. Historical items from web browsers and native applications are integrated directly into the messaging session, allowing users to communicate and access external content without switching applications, thereby enhancing versatility while maintaining interface simplicity
Solution Approach 2:
The messaging application is designed to perform multiple functions beyond basic text communication. It can display and interact with historical items from web browsers and native applications, launch external applications directly from messaging, and provide commerce opportunities, making the messaging application a universal platform for communication and content access
2Productivity
If users manually navigate to historical content through separate applications, then access accuracy is maintained, but user time and operational steps increase
Solution Approach 1:
The system pre-loads and stores historical items from web browsers and native applications in the messaging session context. When users need to access historical content, it is already prepared and available within the messaging interface, eliminating the need for manual navigation through multiple applications and significantly reducing access time
Solution Approach 2:
The messaging application serves as an intermediary that bridges communication between users and historical content from external applications. Instead of requiring users to manually navigate to historical items through separate applications, the messaging app retrieves and displays these items directly within the conversation context, streamlining the access process
Data Source
AI summary
A method includes executing a messaging application to generate a messaging session between a user device and an application contact that represents a communication channel with a business's application. The method further includes requesting historical items from one or more remote servers for insertion into the messaging session. The historical items include links that were generated by the remote servers and selected by a user prior to creation of the messaging session. The links are associated with the business's application. The method further includes receiving historical items from one or more of the remote servers, inserting the received historical items into the messaging session, and receiving user selection of one of the historical items. Additionally, the method includes launching an application according to an access mechanism of the selected historical item and setting the launched application state into a state specified by the access mechanism of the historical item.


