BeTinker project photo


The University of the Third Age (U3A) movement is a n organisation which provides, through its U3As, life-enhancing and life-changing opportunities for retirees and semi-retirees. They learn different things from each other, including technology. U3A members in Halesworth is using Arduino toolkit to build a watering system, thus engaging themselves with technology, and let their voice to be heard. However, Arduino requires some programming skills thus is not suitable for every retirees. This project explored this user group and designed an alternative to Arduino to let the users speak out their voice.BeTinker is an tablet based application that enables retirees to learn and play with updated technology, and to programme without coding. A workshop was held to let them express their opinions, innovative ideas about this new maker toolkit.

Time: 2014.9 - 2014.11

Type: Teamwork with 4, Coursework

Role: Team leader, interactive prototyper, workshop organizer

Method & Skill: Role play, affinity diagram, concept mapping, low-fi and hi-fi prototype, video prototype, think aloud evaluation.


design process

User centric iterative design process

1. User Research

We carried out 2 interviews with 3 U3A members from the community technology group, gardening group of U3A Halesworth, discussing their current usage of technology, mainly on their learning of Arduino toolkit, how it benefited their life and what problems they encountered. After that I did role play to further understand retiree's needs.


Role play

Target User: Retirees and semi-retirees who share the characteristics below.

• Love and have good relationship with technology(E.g: Use smart phone, wearable devices.

• Well educated, open minded, and life-long learning

• Some physical constrains (E.g: Eye sight, shaky finger)


• Different knowledge levels, Arduino is too advanced for some members.

• The learning process became boring

• Small fonts make it difficult to see

User Interface Requirements

• Large font

• Color contrast

• Make the task independent and sequenced

• Keep output message as short as possible

• Reduce choice whenever possible

• Insert confirmation statements whenever possible

2. Concept Ideation

Since our target user lives far away, thus difficult to reach. Based on user research, I did body storming to empathy retirees, and tried to find connections between their daily activity and their interaction with technology.

Then affinity diagram was used to categorise the findings to inspire design. Sketches was used visualise my findings, inspirations and possible design choices. It was also used to helped me understand U3A member’s current toolkit - Arduino, how it works, and how it could be better represent.

affinity diagram 1
affinity diagram 2

Group discussion and affinity Diagram

As we found out that playing with Arduino requires some basic level of programming skills,plus some hardware know-hows, while the users’ levels vary, so some much easier toolkit could be suitable for the retiree. We searched and we chose iBeacon for the following reasons: firstly, it contains different sensors that could be used within different aspects of daily lives; secondly, it provides the APIs that enable us to design ease-to-use interface for retirees to interact with different Beacons. Concept mapping was used to help me understand iBeacon technology, and how it could be applied in the domain of maker’s toolkit for retiree.

concept mapping to understand iBeacon

Concept mapping

At this stage, I only knew my design would be a toolkit for retirees to play with beacons. How user would interact with it was unexplored, so storyboards were only used to envision the future usage and the possible changes the toolkit bring in user’s life.


Story board

With simple physical prototyping, the design concept was peer reviewed by students from other teams, and we got some insightful suggestions:

• Easy manipulation(e.g. drag and drop GUI, simple logic) to better cater for elderly people.

• Enable retirees to control light switches so as to save energy via maker toolkit.

• On platform such as iPad to enable bigger screen

3. Low-fi & video prototyping

I created a vertical prototype with cardboard to illustrate how it would be like to enable retirees to “programme” without “coding”. To deliver the concept, a scenario of setting the beacon to send notification to indicate the perfect time to drink tea when it’s at right temperature was included, I tested my prototype with my teammates, and the prototype turned out sufficient to deliver my concept. And a video prototype was made with the aid of my teammates. It was sent to U3A members to ask for their opinions.

paper prototype

Making lowfi prototype

Beacon Tinker_concept from Weiwei Zhang on Vimeo.

Video Link: Click to view video prototype in a new window

4. Hi-fi prototyping

More concepts on the interface were explored, wireframes were created and refined after getting suggestions from team members. Then the Hi-fi prototype was made and prepared to be tested in the workshop. Below are my prototypes.

hifi prototype

Making hifi prototype

Interactive prototype

5. Workshop I

After the team members had created different prototypes, we gather together to plan and prepare materials needed for the workshop.

workshop material

Three purposes of the workshop:

• firstly to test if our concept of “programming without coding” work with retirees;

• secondly to compare and test different styles of interaction created by team members;

• finally we planned an open question to enabled us to learn from real users of more possible way to apply beacon technology as maker toolkit for retirees.

Workshop Process:

1. Introduction session of iBeacon

2. Signing consent form.

3. Separate testing sessions with different retiree volunteers using think aloud protocol

4. Briefing discussion, sharing experience and Q and A with users.

5. Sending thank you card.

workshop plan

Figure: Workshop plan

6. Workshop II

Testing Session:

1. Introduce the scenarios.

2. Give user a task.

3. Think aloud during the testing.

4. Short discussion with user after the testing.


• “Programming without coding” is cool, but using “If…then Do…” syntax is hard for user to understand unless they have some programming skills.

• Drag and drop style of interaction is simple and easy

• Tell the information in user’s language

-The habit to use unit of measurement is related to their generation

-Using human language rather than numeric information.

• Retirees provided us more innovative future usages via the toolkit.

-- Thanks for reading --
If you have any questions or simply want to chat with me about this project, feel free to drop me an email.