Browse Prior Art Database

A method of dynamically loading content according to reader's behavior

IP.com Disclosure Number: IPCOM000242109D
Publication Date: 2015-Jun-19
Document File: 6 page(s) / 189K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article proposes a method of reloading content according to user's behavior. By analyzing speed of user's moving, a proper chance can be calculated. Thus, if moving is too fast, the reloading will happen earlier. Otherwise, reloading will happen later.

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

Page 01 of 6

A method of dynamically loading content according to reader

A method of dynamically loading content according to reader'

Problems

Mobile applications are becoming popular. Some applications can help users to read content step by step. Not all of content will be loaded at once. Instead, caching and reloading technique are used quite often. If the loaded content is read and there is intent from users to continue to read, reloading will happen.

In order to improve usability and consumability, instead of selecting one button to trigger reload, some prior arts are introduced to provide "near-seamless" reload. If there is trend from gesture to move down, reload will be triggered. This is good in some cases. However, if users is moving down too fast or too slow, or with varying frequency, reloading might not be triggered properly.

Core idea

We propose a method of reloading content according to user's behavior. By analyzing speed of user's moving, a proper chance can be calculated. Thus, if moving is too fast, the reloading will happen earlier. Otherwise, reloading will happen later.

In addition, historical data of this user can be recorded and analyzed to understand the regular behavior of this user. Some basic information from this user are also collected if needed, such as his/her age, gender, interest, etc.

By combing analysis result, the reloading chance can be found for this individual user instead of using a common rule.

The following comparison diagram can clear...