# Initiatives

## 🙋 Why?

This document outlines the features that we'd like to implement in the future in order to allow even more people to use & enjoy drip.

## 💦 Features

[TOC]

### 🌐 Localization

#### Why are we implementing this feature?

Currently drip. is only available in English, temperature is tracked in Celcius. We'd like to
- make drip. available for the users that don't feel comfortable using app interface in English,
- expand drip. community by inviting people to help with translations,
- introduce non-coders to open source community.

#### Who will benefit from this feature?

- People that don't feel comfortable using English interface,
- People that use Farenheit for tracking temperature.

#### How do we implement it?

- Prepare code base by
- extracting app text into separate JSON file (patially accomplished), as well as google play/app store/website texts,
- add language switch,
- providing support for different measurement systems,
- adjusting UI to allow RTL languages
- Investigate localization beyond written language (possibly with the help of the external experts). For example, icons, date formats, check if UI looks good in the new language,
- Integrate with the third-party service (i.e. Weblate, Localise, Crowdin)
- Work with the community to involve people into the translations, preparation of the necessary materials, etc.

#### What is our plan?

| Milestone | Description | Deliverable |Time estimate |
| ----------------- |:----------------------- |:----------------------- |:----------------------- |
| Investigate localization beyond written language|(see above)| Finalized localization concept| 4 weeks|
| Prepare codebase & integrate with 3rd party service |(see above)| app ready to support multiple languages | 8-10 weeks |
| Involve community into the work on translations | TBD | drip. with in multiple languages (alpha version) | TBD |
| Get feedback from beta-testers | Get feedback from beta testers & address received feedback | drip. in multiple languages | 2 weeks |
| Prepare press outreach about the upcoming release | | Press materials | 2 weeks |
| Release | | New version of drip. available in Google play and AppStore | 1 week |

### ☑️ Symptom customisation

#### Why are we implementing this feature?

- Most of the drip. users don't track all available symptoms. For example, some are not interested in tracking fertility-related data.
- Some of the users would like to track custom symptoms, like pain/mood/etc. with ability to specify level of symptom, weight, etc.
- We would like to make drip. useful for transgender people.

#### Who will benefit from this feature?

- Current drip. users
- Transgender people

#### How do we plan to implement it?

- We'd like to allow user choose/customize symptom that (s)he tracks.
- We'd like to learn more (make some interviews?) about needs of transgender people and address most urgent ones accordintly.
- Once the feature is ready, we'd like to reach out to the organisations that work with transgender people.

#### What is our plan?

| Milestone | Description | Deliverable |Time estimate |
| ----------------- |:----------------------- |:----------------------- |:----------------------- |
| | | |

### 🚄 UX improvement

#### Why are we implementing this feature?

We want to make drip. users experience easier, smoother & even more pleasant.

#### Who will benefit from this feature?

All current and future users of drip.

#### How do we plan to implement it?

We either would like to get help from the external UI/UX specialists or conduct UI/UX research ourselves and implement the improvements to address (our) findings.

#### What is out plan?

| Milestone | Description | Deliverable |Time estimate |
| ----------------- |:----------------------- |:----------------------- |:----------------------- |
| Find a UI/UX consultant or conduct UI/UX research ourselves | | List of UI/UX painpoints | 4 weeks |
| Address top painpoints| TBD | drip. with improved UI/UX (alpha version) | 8 weeks |
| Get feedback from beta-testers | Get feedback from beta testers & address received feedback | drip. with improved UI/UX | 2 weeks |
| Prepare press outreach about the upcoming release | | Press materials | 2 weeks |
| Release | | New version of drip. available in Google play and AppStore | 1 week |

### 👮‍♀️ Security audit

#### Why are we implementing this feature?

We would like to make sure that drip. meets the highest security standards.

#### Who will benefit from this feature?

All current and future users of drip.

#### How do we plan to implement it?

We would like to get security & privacy audit from the external consultant(s)/orgnisation(s).

#### What is out plan?

| Milestone | Description | Deliverable |Time estimate |
| ----------------- |:----------------------- |:----------------------- |:----------------------- |
| Find security confulstant and get audit from them | | Audit restult | TBD |
| Address top painpoints| TBD | drip. with improved security (alpha version) | TBD |
| Get feedback from beta-testers | Get feedback from beta testers & address received feedback | drip. with improved security | TBD |
| Publish security audit results | | | TBD |
| Prepare press outreach about the upcoming release | | Press materials | 2 weeks |
| Release | | New version of drip. available in Google play and AppStore | 1 week |

### 🎤 Accessibility

#### Why are we implementing this feature?

Currently drip. doesn't offer accessibility features.

#### Who will benefit from this feature?

People with vision impairment or low vision.

#### How do we plan to implement it?

React Native provides ["APIs for integrating apps with assistive technologies like the bundled screen readers VoiceOver (iOS) and TalkBack (Android)."](https://reactnative.dev/docs/accessibility) The following resources might be useful:
- https://www.shopify.com/partners/blog/react-native-accessibility
- http://man.hubwiz.com/docset/React_Native.docset/Contents/Resources/Documents/react-native/docs/accessibility.html
- https://levelup.gitconnected.com/accessibility-in-react-native-apps-f06d5469a453

Also we would like to involve community in the feature definition and beta testing.

#### What is our plan?

| Milestone | Description | Deliverable |Time estimate |
| ----------------- |:----------------------- |:----------------------- |:----------------------- |
| Research | Research existing API, get in touch with possible beta testers and get requirements from them & implement accessibility feature on one page | Prototype implementing accessible home page for iOS & Android | 4 weeks |
| Get feedback from testers | Find testers, gather their feedback about the prototype & address received feedback | Prototype implementing accessible home page for iOS & Android | 4 weeks |
| Make drip. accessible | Implement accessibility features based on the learnings from the prototype | first version of accessibility implementation | 4 weeks |
| Get feedback from testers | Get feedback from beta testers & address received feedback | drip. with accessibility features | 2 weeks |
| Prepare press outreach about the upcoming release | | Press materials | 2 weeks |
| Release | | New version of drip. available in Google play and AppStore | 1 week |

### 👩‍💻 Maintenance & Tech Wealth

#### Why are we implementing this feature?

More info can be found [in this article](https://increment.com/planning/reframing-tech-debt/)

#### Who will benefit from this feature?

Contrubutors and drip. users

#### How do we plan to implement it?

Make sure we use
- up-to-date dependancies,
- revise and improve our technology stack on the regular basis.

#### What is our plan?

It's an on-going effort