Browse Prior Art Database

A Design of Topic-Aware Graphical User Interface for Messenger Systems

IP.com Disclosure Number: IPCOM000247189D
Publication Date: 2016-Aug-15
Document File: 9 page(s) / 320K

Publishing Venue

The IP.com Prior Art Database

Abstract

In a messenger system, messages are shown whenever people send their texts out. The screen is overwhelmed by pop-up messages quickly. People may miss some interesting and focus topics if they don’t keep their eyes on the screen all the time. For example, lots of messages appear within a minute and you need to scroll up and down to read all of them. All messages are displayed by input timestamp typically. Replies of a specific message are not shown right next to the message. Some misunderstanding or wrong interpretation may occur. For example, simply "YES" may be ambiguous as people not sure which sentence/topic the sender refers to. The proposed idea is to design a topic-aware graphical user interface for messenger systems. It encompasses a hierarchical topic traverse view, a topic-aware message display view, an interface for topic creation, response and search and a topic-aware activity creation, response and display view. By our design of topic-aware message user interface, users could easily catch up the topic they are interested in and not bothered by unstructured and unrelated conversations. In addition, it is easy to embed topic-aware activity such as vote within the same interface.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 01 of 9

A Design of Topic-Aware Graphical User Interface for Messenger Systems

Problem statement and background:

In a messenger system, messages are shown whenever people send their texts out. The screen is overwhelmed by pop-up messages quickly. People may miss some interesting and focus topics if they don't keep their eyes on the screen all the time. For example, lots of messages appear within a minute and you need to scroll up and down to read all of them.

All messages are displayed by input timestamp typically. Replies of a specific message are not shown right next to the message.Some misunderstanding or wrong interpretation may occur. For example, simply "YES" may be ambiguous as people not sure which sentence/topic the sender refers to.

Core idea:


- Brief descriptions


The proposed idea is to design a topic-aware graphical user interface for messenger systems. It encompasses:

A hierarchical topic traverse view

Topics can be organized hierarchically

   
Able to switch contexts by selecting corresponding topics
A topic-aware message display view

Topic-aware visual design
*When you stay at a specific topic, the topic name is presented in the top (the position of topic selection UI component).
*Otherwise, the topic name appears next to each message.

Personalized message display
*Order by message input time, replies within the topic, involved amount of people, my reply time…etc.

*Filter by sender name, keyword in message, input time…etc.

An interface for topic creation, response and search

   A # prefix in the message input frame indicates a specific topic *The topic never exists before, the topic will be created and can be found in the topic selection frame *The topic exists already, input messages will be associated with the topic *The topic ever existed but is aging to be inactive, the topic will be re-activated and can be found in the topic selection frame A type ahead matching list is presented in the bottom of message input frame
A topic-aware activity creation, response and display view

Meeting schedule, vote etc. can be bound to a specific topic.

- Embodiment of Hierarchical Topic View

1



Page 02 of 9


- Embodiment of Topic-Aware Message Display View

2



Page 03 of 9


- Embodiment of Personalized Message Display View

3



Page 04 of 9


- Embodiment of Topic Creation, Response and Search Interface

4



Page 05 of 9


- Embodime...