Unified Contact Card Interface for Mobile Data Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices face inefficiencies due to limited screen size and the need to navigate multiple applications to access and view data associated with contacts, leading to cumbersome processes for retrieving information like emails and calendar events.

Innovation Solution

An association application that allows users to access, analyze, and associate various data objects and information with contacts, enabling them to view all relevant data from a single contact card, minimizing the need for physical interaction with multiple applications and lists.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users navigate through multiple applications to access contact-related data, then data accessibility is improved, but operation complexity increases and time consumption increases

Engineering Contradiction:
Improvedata accessibilityVSAvoidoperation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent combines multiple application-specific data views into a single unified contact card interface. Instead of requiring users to navigate separate email, calendar, and messaging applications, the system merges all contact-related data into one centralized location, thereby improving accessibility while reducing operational complexity

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The contact card is designed as a universal interface that performs multiple functions simultaneously - displaying email messages, calendar events, messaging conversations, and contact details all in one place. This multi-functional approach allows users to access diverse data types without switching applications, resolving the contradiction between versatility and complexity

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If users navigate through multiple applications to access contact-related data, then data accessibility is improved, but time consumption increases

Engineering Contradiction:
Improvedata accessibilityVSAvoidtime consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system pre-organizes all contact-related data into the contact card structure in advance. When a user needs to access information about a contact, the data is already aggregated and ready for immediate viewing, eliminating the time required to manually navigate through multiple applications and locate relevant information

Inventive Principle:
Principle #10Preliminary action

3Weight of moving object

If the device screen size is limited, then device portability is improved, but information visibility deteriorates

Engineering Contradiction:
Improvedevice portabilityVSAvoidinformation visibility
Core Design Contradiction:
Weight of moving objectVSLoss of information

Solution Approach 1:

The contact card interface segments information into distinct, organized sections for different data types (emails, calendar events, messages, contact details). This segmentation allows the limited screen space to be efficiently utilized, presenting comprehensive information in a structured manner that maintains visibility while preserving device portability

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7502606B2Computer-readable medium, method, and device for associating information with a contact
Publication Date: 2009.03.10 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7502606B2 patent drawing
  • US7502606B2 patent drawing
  • US7502606B2 patent drawing

AI summary

A method, computer-readable medium, and a computing device are provided for associating one or more data objects and other information with one or more contacts. In certain embodiments, an association application operates to access, analyze, and associate one or more data objects and other information with one or more contacts. A user may then examine a contact and utilize data objects and other information associated with the particular contact. Thus, a user can think about information as it relates to a contact, rather than the information type or application that the information relates. The user can now go to one location where information is compiled with respect to a specific contact.