Wearables; Privacy, Accessibility & Localisation

If you were starting a new project, how would you incorporate these elements of quality that are often overlooked? I will walk you through my approach using an example open source wearables app for logging your poo. I will give you pointers in how to refactor your existing projects to improve these elements of quality.

Case Study example: Insight Timer, a meditation app with over 4 million meditators and 2000 teachers. This app focused on growth over quality and has had to invest significant engineering rescources into supporting multiple languages and it's still slow going.

We will do a deep dive into the following areas:

Privacy by design - what does this look like for a health app?

Using Google Translate for quick and dirty translations

Using a string translation service for a better localised experience

Challenges in rendering Right to Left for wearables

Using Screen reader technologies in other languages

 
1 favorite thumb_down thumb_up 1 comment visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Talk

5 minutes introduction

Going over Insight Timer as a case study

5 minutes for Privacy by design

walking through my reasoning and design choices for incorporating privacy and transperancy for this app

10 minutes for Using Google Translate for quick and dirty translations

will involve a live code demo of using the Google Translate API to translate the app into a language it's never been translated into before.

5 minutes for Using a string translation service for a better localised experience

this is the next iteration from using a machine learning translation approach. What type of services are out there? We will go through an example service that I built to support this app.

5 minutes for Challenges in rendering Right to Left for wearables

we will go over the challenges I experienced here with a demo of changing the rendering in app.

10 minutes for Using Screen reader technologies in other languages

Not many people combine both accessiblity testing and localisation testing. We will explore some screen reader technology in another language and talk about how to refactor code to help support this.

5 minutes for Q&A

Learning Outcome

An appreciation of inclusive design, it's not hard to build if it's there from the start.

How to use translation services at your disposal

How to test for accessibility in other languages

Target Audience

Mobile developers, product managers, testers

Prerequisites for Attendees

A basic understanding of swift or kotlin

schedule Submitted 8 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Pavi De Alwis
    By Pavi De Alwis  ~  7 months ago
    reply Reply

    I like these aspects of the submission, and they should be retained:

    • End user devices are still part of IoT and the App dev end of the spectrum and. Particularly mobile devices so keen to hear about this.

    I think the submission could be improved by:

    • Using an IoT case study