Co-authored-by: ange <ange@yw5n.com> Reviewed-on: #43
This commit is contained in:
parent
8fe630dc59
commit
615fc9bd90
@ -1,5 +1,7 @@
|
||||
# Icing
|
||||
|
||||
## Encrypting phone calls on an analog audio level
|
||||
|
||||
An Epitech Innovation Project
|
||||
|
||||
*By*
|
||||
@ -8,6 +10,12 @@ An Epitech Innovation Project
|
||||
---
|
||||
|
||||
The **docs** folder contains documentation about:
|
||||
|
||||
#### Epitech
|
||||
- The Beta Test Plan
|
||||
- The Delivrables
|
||||
|
||||
#### Icing
|
||||
- The project
|
||||
- A user manual
|
||||
- Our automations
|
||||
|
||||
@ -1,95 +0,0 @@
|
||||
# Beta Test Plan
|
||||
|
||||
## Core Features
|
||||
|
||||
### Icing protocol
|
||||
- Handshakes
|
||||
- ECDH
|
||||
- Compression
|
||||
- Audio error correction
|
||||
- In-call pubkey share
|
||||
- Trust shifts
|
||||
|
||||
### Icing dialer (based on Icing kotlin library, an Icing protocol implementation)
|
||||
- Call
|
||||
- Encrypted if public key available
|
||||
- Allows users to share their public keys
|
||||
- Normal call if conditions unment
|
||||
- Encrypted and clear DTMF transmission
|
||||
- SIM choice on call
|
||||
- Call history
|
||||
|
||||
- Contacts
|
||||
- Contact creation / editing
|
||||
- Contact sharing via QR code / VCF
|
||||
- Contact search
|
||||
- Favorite contacts
|
||||
- Storage of user public keys
|
||||
- Blocked number
|
||||
- Contact preview (picture, number, public key...)
|
||||
|
||||
- Visual voicemail
|
||||
- Play / Pause
|
||||
- Notification
|
||||
- Quick link to call, text, block, share number...
|
||||
|
||||
- SIM settings
|
||||
- Default SIM choice
|
||||
|
||||
- Asymetric Keys
|
||||
- Secure storage
|
||||
- Generation at startup if missing
|
||||
- Full key management
|
||||
- Secure generation
|
||||
- Exportation on creation (insecure generation)
|
||||
- Importation
|
||||
- Trust shift
|
||||
|
||||
|
||||
## Beta Testing Scenarios
|
||||
- Clear call from Icing dialer to another dialer (Google, Apple...)
|
||||
- Clear call from Icing dialer to another Icing dialer
|
||||
- Clear call from Icing dialer to an icing pubkey-known contact but without Icing dialer
|
||||
- Encrypted call from Icing dialer to a known contact with Icing dialer
|
||||
- Encrypted call from Icing dialer to an unknown contact with Icing dialer
|
||||
- Create / Edit / Save contact with(out) public key
|
||||
- Share contact as QR code / Vcard
|
||||
- Import contact from QR code / Vcard
|
||||
- Listen to voicemail
|
||||
- Record encrypted call and check the encryption
|
||||
- Change default SIM
|
||||
|
||||
## User Journeys
|
||||
|
||||
Mathilda, 34 years-old, connects to her PayPal account from a new device.
|
||||
To authenticate herself, PayPal sends her a code on her voicemail.
|
||||
Mathilda being aware of the risks of this technology, she has set up strong Icing authentication with her network provider by registering a pair of her Icing public keys.
|
||||
When she calls her voicemail, Icing protocol is triggered and checks for her key authentication ;
|
||||
it will fail if the caller does not pocesses the required Icing keys.
|
||||
Mathilda is thus the only one granted access, and she can retreive her PayPal code securely.
|
||||
|
||||
Jeff, 70 years-old, calls his bank after he had a problem on his bank app.
|
||||
The remote bank advisor asks him to authenticate, making him type his password on the phone dialer.
|
||||
By using the Icing protocol, not only would Jeff and the bank be assured that the informations are transmitted safely,
|
||||
but also that the call is coming from Jeff's phone and not an impersonator.
|
||||
|
||||
Elise is a 42 years-old extreme reporter.
|
||||
After interviewing Ukrainian opposition's leader, the SBU (ex KGB) are looking for her accross the whole country.
|
||||
She hides in western moutains near Romania, and she barely receive cellular network.
|
||||
She suspects her phone line to be monitored, so the best she can do to call for extraction safely, is to use her Icing dialer.
|
||||
|
||||
Paul, a 22 years-old developer working for a big company, decides to go to China for vacations.
|
||||
But everything goes wrong! The company's product he works on, is failling in the middle of the day and no one is
|
||||
qualified to fix it. Paul doesn't have WiFi and his phone plan only covers voice calls in China.
|
||||
With Icing dialer, he can call his collegues and help fix the
|
||||
problem, safe from potential Chinese spies.
|
||||
|
||||
## Evaluation Criteria
|
||||
- Can a private key be generated
|
||||
- Can a normal call be made?
|
||||
- Can an encrypted call be made?
|
||||
- Can a contact be created / edited / imported / exported?
|
||||
- Can a voicemail be listened to?
|
||||
- Is the encryption fast enough, light enough to be usable (audible call)
|
||||
- Is the encryption strong enough not to be deciphered by a modern (as of 2025)
|
||||
supercomputer?
|
||||
@ -1,92 +0,0 @@
|
||||
# Beta Test Plan
|
||||
|
||||
## Fonctionnalités Principales
|
||||
|
||||
### Protocole Icing
|
||||
- Poignées de main
|
||||
- ECDH
|
||||
- Compression
|
||||
- Correction d’erreurs audio
|
||||
- Partage de clé publique pendant l’appel
|
||||
- Changements de confiance
|
||||
|
||||
### Icing Dialer (basé sur la bibliothèque Kotlin Icing, une implémentation du protocole Icing)
|
||||
- Appel
|
||||
- Chiffré si la clé publique est disponible
|
||||
- Permet aux utilisateurs de partager leurs clés publiques
|
||||
- Appel normal si les conditions ne sont pas réunies
|
||||
- Transmission DTMF chiffrée et en clair
|
||||
- Choix de la carte SIM lors de l’appel
|
||||
- Historique des appels
|
||||
|
||||
- Contacts
|
||||
- Création / modification de contacts
|
||||
- Partage de contacts via QR code / VCF
|
||||
- Recherche de contacts
|
||||
- Contacts favoris
|
||||
- Stockage des clés publiques des utilisateurs
|
||||
- Numéros bloqués
|
||||
- Aperçu du contact (photo, numéro, clé publique, etc.)
|
||||
|
||||
- Messagerie vocale visuelle
|
||||
- Lecture / Pause
|
||||
- Notification
|
||||
- Accès rapide pour appeler, envoyer un SMS, bloquer ou partager le numéro
|
||||
|
||||
- Paramètres SIM
|
||||
- Choix de la SIM par défaut
|
||||
|
||||
- Clés asymétriques
|
||||
- Stockage sécurisé
|
||||
- Génération au démarrage en cas d’absence
|
||||
- Gestion complète des clés
|
||||
- Génération sécurisée
|
||||
- Exportation lors de la création (génération non sécurisée)
|
||||
- Importation
|
||||
- Changement de confiance
|
||||
|
||||
## Scénarios de Test Bêta
|
||||
- Appel normal depuis Icing Dialer vers un autre dialer (Google, Apple…)
|
||||
- Appel normal depuis Icing Dialer vers un autre Icing Dialer
|
||||
- Appel normal depuis Icing Dialer vers un contact connu pour sa clé publique Icing mais sans Icing Dialer
|
||||
- Appel chiffré depuis Icing Dialer vers un contact connu utilisant Icing Dialer
|
||||
- Appel chiffré depuis Icing Dialer vers un contact inconnu utilisant Icing Dialer
|
||||
- Création / modification / enregistrement d’un contact avec (ou sans) clé publique
|
||||
- Partage de contact sous forme de QR code / Vcard
|
||||
- Importation de contact depuis un QR code / Vcard
|
||||
- Écoute de la messagerie vocale
|
||||
- Enregistrement d’un appel chiffré et vérification du chiffrement
|
||||
- Changement de la SIM par défaut
|
||||
|
||||
## Parcours Utilisateurs
|
||||
|
||||
Mathilda, 34 ans, se connecte à son compte PayPal depuis un nouvel appareil.
|
||||
Pour s’authentifier, PayPal lui envoie un code sur sa messagerie vocale.
|
||||
Consciente des risques liés à cette technologie, Mathilda a mis en place une authentification Icing robuste avec son fournisseur de réseau en enregistrant une paire de ses clés publiques Icing.
|
||||
Lorsqu’elle appelle sa messagerie vocale, le protocole Icing se déclenche et vérifie son authentification par clé ;
|
||||
l’appel échouera si l’interlocuteur ne possède pas les clés Icing requises.
|
||||
Mathilda est ainsi la seule à obtenir l’accès, et elle peut récupérer son code PayPal en toute sécurité.
|
||||
|
||||
Jeff, 70 ans, appelle sa banque après avoir rencontré un problème sur son application bancaire.
|
||||
Le conseiller bancaire à distance lui demande de s’authentifier en saisissant son mot de passe sur le téléphone.
|
||||
En utilisant le protocole Icing, non seulement Jeff et la banque ont la garantie que les informations sont transmises en toute sécurité,
|
||||
mais aussi que l’appel provient bien du téléphone de Jeff et non d’un imposteur.
|
||||
|
||||
Elise, une reporter intrépide de 42 ans,
|
||||
après avoir interviewé le leader de l’opposition ukrainienne, se retrouve recherchée dans tout le pays par la SBU (ex-KGB).
|
||||
Elle se cache dans les montagnes de l’Ouest, près de la Roumanie, et reçoit à peine le réseau cellulaire.
|
||||
Soupçonnant que sa ligne téléphonique est surveillée, le mieux qu’elle puisse faire pour appeler en toute sécurité pour demander une extraction est d’utiliser son Icing Dialer.
|
||||
|
||||
Paul, un développeur de 22 ans travaillant pour une grande entreprise, décide de partir en vacances en Chine.
|
||||
Mais tout tourne mal ! Le produit de l’entreprise sur lequel il travaille tombe en panne en plein milieu de la journée et personne n’est
|
||||
qualifié pour le réparer. Paul n’a pas de WiFi et son forfait téléphonique ne couvre que les appels vocaux en Chine.
|
||||
Avec Icing Dialer, il peut appeler ses collègues et contribuer à résoudre le problème, en toute sécurité face aux éventuels espions chinois.
|
||||
|
||||
## Critères d’Évaluation
|
||||
- Une clé privée peut-elle être générée ?
|
||||
- Un appel normal peut-il être passé ?
|
||||
- Un appel chiffré peut-il être passé ?
|
||||
- Un contact peut-il être créé / modifié / importé / exporté ?
|
||||
- Une messagerie vocale peut-elle être écoutée ?
|
||||
- Le chiffrement est-il suffisamment rapide et léger pour être utilisable (appel audible) ?
|
||||
- Le chiffrement est-il suffisamment robuste pour ne pas être déchiffré par un supercalculateur moderne (à partir de 2025) ?
|
||||
@ -1,57 +0,0 @@
|
||||
# Livrables du Projet
|
||||
|
||||
---
|
||||
|
||||
## Commun
|
||||
|
||||
### Développer et fidéliser une communauté d’utilisateurs
|
||||
|
||||
Nous prévoyons de créer une communauté d’utilisateurs où ceux-ci pourront partager leurs expériences avec le projet et fournir des retours sur des plateformes sociales telles que Telegram, Discord ou Matrix.
|
||||
|
||||
L’objectif est de promouvoir notre projet dans différentes communautés open-source, ainsi que celles axées sur la sécurité et la confidentialité, afin de rassembler des utilisateurs expérimentés capables d’apporter des retours pertinents.
|
||||
|
||||
Comme nous ne nous concentrons pas sur la vente d’un produit à qui que ce soit, mais plutôt sur le développement d’un protocole open-source, la fidélisation des utilisateurs n’est pas une priorité ; elle constituera davantage un indicateur de pertinence du projet qu’un objectif en soi. Cela signifie que nous nous concentrerons sur l’écoute et la prise en compte de bons retours plutôt que sur la publication de messages ludiques sur les réseaux sociaux.
|
||||
|
||||
### Travailler sur l’expérience utilisateur
|
||||
|
||||
Nous travaillerons à rendre le dialer convivial et facile à utiliser.
|
||||
|
||||
Nous avons confiance dans notre démarche actuelle de développement de l’UX et les retours des utilisateurs seront pris en compte.
|
||||
|
||||
---
|
||||
|
||||
## Spécifications
|
||||
|
||||
### Renforcer la crédibilité et accroître la réputation du projet
|
||||
|
||||
- **Développement transparent :**
|
||||
Maintenir une feuille de route et un changelog publics pour documenter chaque mise à jour et décision durant le cycle de vie du projet.
|
||||
|
||||
- **Audits de sécurité :**
|
||||
Nous nous appuierons sur nos tests automatisés et sur des experts de la communauté afin d’assurer des audits organiques et constants.
|
||||
|
||||
- **Engagement de la communauté :**
|
||||
Impliquer activement notre communauté d’utilisateurs dans les discussions, rapports de bugs et demandes de fonctionnalités. Mettre régulièrement la communauté au courant des avancées et des changements à venir.
|
||||
|
||||
- **Bonnes pratiques de l’open-source :**
|
||||
Adhérer aux pratiques de codage reconnues dans l’industrie, à une documentation approfondie, et à des pipelines d’intégration/déploiement continus afin de garantir un code de haute qualité et facile à maintenir.
|
||||
|
||||
- **Visibilité sur les forums clés :**
|
||||
Présenter et partager notre travail lors de conférences et d’événements axés sur l’open-source, la cybersécurité et la confidentialité pour renforcer la crédibilité et attirer des retours constructifs.
|
||||
|
||||
### Établir des partenariats stratégiques
|
||||
|
||||
- **Collaborations académiques :**
|
||||
S’associer avec des institutions académiques pour des initiatives de recherche et la validation de notre protocole, en tirant parti de leur expertise pour de futures améliorations.
|
||||
|
||||
- **Alliances industrielles :**
|
||||
Rechercher des partenariats avec des acteurs reconnus dans le domaine des logiciels open-source afin de bénéficier de leur large couverture communautaire, tels que AOSP, GrapheneOS ou LineageOS.
|
||||
|
||||
- **Opportunités d’intégration :**
|
||||
Explorer des collaborations avec des systèmes d’exploitation mobiles (par exemple, AOSP) et des fournisseurs de VoIP pour intégrer Icing dans les infrastructures de communication existantes.
|
||||
|
||||
- **Projets d’innovation communs :**
|
||||
S’engager dans des efforts de co-développement en accord avec notre mission, afin que les deux parties contribuent et bénéficient des avancées technologiques.
|
||||
|
||||
- **Financement et soutien :**
|
||||
Identifier et rechercher des subventions, des parrainages et des financements de recherche en adéquation avec les objectifs du projet, garantissant ainsi un développement durable.
|
||||
245
docs/beta_test_plan.md
Normal file
245
docs/beta_test_plan.md
Normal file
@ -0,0 +1,245 @@
|
||||
# Beta Test Plan
|
||||
|
||||
## Core Functionalities
|
||||
|
||||
---
|
||||
### Action Plan review:
|
||||
|
||||
In our previous Action Plan, we listed the following functionnal specifications:
|
||||
- Phone call encryption between two known pairs, that exchanged keys in person. *Mandatory*
|
||||
- Phone dialer that is discret and functional, and should not disturb a normal use (clear phone call). *Mandatory*
|
||||
- Phone call encryption between two unknown pairs, with key exchange on the go. Optional.
|
||||
- SMS encryption between two known pairs (in person key exchange). Optional.
|
||||
|
||||
We now retain only the two first functional specifications.
|
||||
|
||||
### Core Functionalities
|
||||
|
||||
Based on this review, here are all the core functionnalities we set:
|
||||
|
||||
#### Icing protocol
|
||||
- Advanced protocol documentation, paving the way for a full RFC.
|
||||
|
||||
The protocol definition will include as completed:
|
||||
- Peer ping
|
||||
- Ephemeral key gestion
|
||||
- Perfect Forward Secrecy
|
||||
- Handshakes
|
||||
- Real-time data-stream encryption (and decryption)
|
||||
- Encrypted stream compression
|
||||
- Transmission over audio stream
|
||||
- Minimal error correction in audio-based transmission
|
||||
- Error handling and user prevention
|
||||
|
||||
And should include prototype or scratches functionalities, among which:
|
||||
- Embedded silent data transmission (silently transmit light data during an encrypted phone call)
|
||||
- On-the-fly key exchange (does not require prior key exchange, sacrifying some security)
|
||||
- Strong error correction
|
||||
|
||||
#### The Icing dialer (based on Icing kotlin library, an Icing protocol implementation)
|
||||
|
||||
The Icing dialer should be a fully transparent and almost undistinguishable smartphone dialer.
|
||||
Any Icing-unaware user should be able to use the dialer smoothly to make calls to anyone.
|
||||
The dialer should propose a full set of functionnalities to handle its Icing protocol implementation.
|
||||
|
||||
Here is the list of all the functionnalities our dialer will integrate:
|
||||
|
||||
- Call
|
||||
- Ringtone on incoming call
|
||||
- Incoming and ongoing call notification
|
||||
- Complete dialer with all numbers, star *, pound #
|
||||
- Mute button
|
||||
- Speaker button
|
||||
- Normal call
|
||||
- DTMF transmission
|
||||
- SIM choice on call
|
||||
|
||||
- Encrypted Call
|
||||
- Encrypted call if pair public key is known
|
||||
- Encrypted DTMF transmission
|
||||
- Data rate indicator
|
||||
- Data error indicator
|
||||
- Disable encryption button
|
||||
|
||||
- Call history
|
||||
- Call details (timedate, duration, ring number)
|
||||
- Missed calls filter
|
||||
- Outgoing calls filter
|
||||
- Incoming calls filter
|
||||
- Call back function
|
||||
- Contact modal on history tap
|
||||
- Block call number
|
||||
|
||||
- Contacts
|
||||
- Sorted contact listing
|
||||
- Contact creation / editing buttons
|
||||
- Contact sharing via QR code / VCF
|
||||
- Contact search bar (application wide)
|
||||
- Favorite contacts
|
||||
- Contact preview (picture, number, public key...)
|
||||
|
||||
- Visual voicemail
|
||||
- Play / Pause
|
||||
- Notification
|
||||
- Quick link to call, text, block, share number...
|
||||
|
||||
- Miscellanous
|
||||
- Settings menu
|
||||
- Version number
|
||||
- Storage of user public keys
|
||||
- Blocklist gestion (list / add / del / search)
|
||||
- Default SIM choice
|
||||
|
||||
- Asymetric Keys
|
||||
- Secure storage
|
||||
- Generation at startup if missing
|
||||
- Full key management (list / add / del / search / share)
|
||||
- Secure generation (Android Keystore generation)
|
||||
- Insecure generation (RAM generation)
|
||||
- Exportation on creation (implies insecure generation)
|
||||
- Importation
|
||||
- Trust shift (shift trust from contacts)
|
||||
|
||||
|
||||
## Beta Testing Scenarios
|
||||
- Clear call from Icing dialer to another dialer (Google, Apple...)
|
||||
- Clear call from Icing dialer to another Icing dialer
|
||||
- Clear call from Icing dialer to an icing pubkey-known contact but without Icing dialer
|
||||
- Encrypted call from Icing dialer to a known contact with Icing dialer
|
||||
- Encrypted call from Icing dialer to an unknown contact with Icing dialer
|
||||
- Create / Edit / Save contact with(out) public key
|
||||
- Share contact as QR code / Vcard
|
||||
- Import contact from QR code / Vcard
|
||||
- Listen to voicemail
|
||||
- Record encrypted call and check the encryption
|
||||
- Change default SIM
|
||||
|
||||
## User Journeys
|
||||
|
||||
Mathilda, 34 years-old, connects to her PayPal account from a new device.
|
||||
To authenticate herself, PayPal sends her a code on her voicemail.
|
||||
Mathilda being aware of the risks of this technology, she has set up strong Icing authentication with her network provider by registering a pair of her Icing public keys.
|
||||
When she calls her voicemail, Icing protocol is triggered and checks for her key authentication ;
|
||||
it will fail if the caller does not pocesses the required Icing keys.
|
||||
Mathilda is thus the only one granted access, and she can retreive her PayPal code securely.
|
||||
|
||||
Jeff, 70 years-old, calls his bank after he had a problem on his bank app.
|
||||
The remote bank advisor asks him to authenticate, making him type his password on the phone dialer.
|
||||
By using the Icing protocol, not only would Jeff and the bank be assured that the informations are transmitted safely,
|
||||
but also that the call is coming from Jeff's phone and not an impersonator.
|
||||
|
||||
Elise is a 42 years-old extreme reporter.
|
||||
After interviewing Russians opposition's leader, the FSB is looking to interview her.
|
||||
She tries to stay discreet and hidden, but those measures constrains her to barely receive cellular network.
|
||||
She suspects her phone line to be monitored, so the best she can do to call safely, is to use her Icing dialer.
|
||||
|
||||
Paul, a 22 years-old developer working for a big company, decides to go to China for vacations.
|
||||
But everything goes wrong! The company's product he works on, is failling in the middle of the day and no one is
|
||||
qualified to fix it. Paul doesn't have WiFi and his phone plan only covers voice calls in China.
|
||||
With Icing dialer, he can call his collegues and help fix the
|
||||
problem, safe from potential Chinese spies.
|
||||
|
||||
## Evaluation Criteria
|
||||
### Protocol and lib
|
||||
1. Security
|
||||
- Encryption Strength: Ensure that the encryption algorithms used (AES-256, ECC)
|
||||
are up-to-date and secure.
|
||||
- Key Management: Evaluate the mechanism for generating, distributing, and
|
||||
storing encryption keys (P-256 keys, ECDH).
|
||||
- Forward Secrecy: Confirm that the protocol supports forward secrecy, meaning
|
||||
that session keys are discarded after use to prevent future decryption of
|
||||
past communication, and that future sessions are salted with a pseudo-random salt
|
||||
resulting or derived from the past calls.
|
||||
- End-to-End Encryption Integrity: Verify that no clear data is exposed
|
||||
outside the encryption boundary (client-side only).
|
||||
- Replay Protection: Ensure that the protocol includes strong mechanisms to prevent replay
|
||||
attacks.
|
||||
|
||||
2. Performance
|
||||
- Latency: Measure the round-trip time (RTT) for call setup and audio quality
|
||||
during the call. The system should aim for the lowes latency possible.
|
||||
- Bandwidth Efficiency: Evaluate the protocol’s ability to optimize bandwidth
|
||||
usage while maintaining acceptable audio quality.
|
||||
- Audio Quality: Assess the audio quality during calls, including clarity,
|
||||
consistency, and minimal distortion.
|
||||
|
||||
3. Usability
|
||||
- Ease of Integration: Evaluate how easy it is to integrate the library into an
|
||||
Android application, including the availability of well-documented APIs and
|
||||
clear examples.
|
||||
- Seamless User Experience: Check for smooth call initiation, handling of
|
||||
dropped calls, and reconnection strategies. The app should handle background
|
||||
operation gracefully.
|
||||
- UI/UX Design: Assess the user interface (UI) of the Android dialer for intuitiveness,
|
||||
accessibility, and if it could be a drop-in replacement for the original dialer.
|
||||
- Error Handling and Recovery: Evaluate how the system handles unexpected
|
||||
errors (e.g., network issues, connection drops) and recovers from them.
|
||||
|
||||
4. Interoperability
|
||||
- Support for Multiple Protocols: Verify if the protocol can
|
||||
integrate with existing standards (e.g., SIP, WebRTC) for interoperability
|
||||
with other services.
|
||||
- Cross-device Compatibility: Ensure that calls encryption can be initiated and received
|
||||
across different devices, operating systems, and network conditions.
|
||||
- Backward Compatibility: Test whether the protocol is backward compatible.
|
||||
|
||||
5. Privacy
|
||||
- Data Storage: Evaluate how the system stores any data (user details, identities).
|
||||
Ensure that sensitive information is encrypted.
|
||||
- Data Minimization: Ensure that only the minimum necessary data is used
|
||||
for the protocol to function.
|
||||
- No Call Metadata Storage: Ensure that no metadata (e.g., call logs, duration,
|
||||
timestamps) is stored unless necessary, and, if stored, it should be
|
||||
encrypted.
|
||||
|
||||
6. Maintainability
|
||||
- Code Quality: Review the library for clarity, readability, and
|
||||
maintainability of the code. It should be modular and well-documented.
|
||||
- Documentation: Ensure that the protocol and library come with thorough
|
||||
documentation, including how-to guides and troubleshooting resources.
|
||||
- Active Development and Community: Check the active development of the
|
||||
protocol and library (open-source contributions, GitHub repository activity).
|
||||
|
||||
### Dialer
|
||||
1. User Interface
|
||||
- Design and Layout: Ensure that the dialer interface is simple, intuitive, and
|
||||
easy to navigate. Buttons should be appropriately sized, and layout should
|
||||
prioritize accessibility.
|
||||
- Dialer Search and History: Ensure there’s an efficient contact search,
|
||||
history logging, and favorites integration.
|
||||
- Visual Feedback: Verify that the app most usefull buttons provides visual feedback for actions,
|
||||
such as dialling, calls available interactions for example.
|
||||
|
||||
2. Call Management
|
||||
- Call Initiation: Test the ease of initiating a call from contact list, recent
|
||||
call logs, contact search or direct number input.
|
||||
- Incoming Call Handling: Verify the visual and audio prompts when receiving
|
||||
calls, including notifications for missed calls.
|
||||
- Call Hold/Transfer/Forward: Ensure the dialer supports call hold, transfer,
|
||||
and forwarding features.
|
||||
- Audio Controls: Check whether the app allows users to adjust speaker volume,
|
||||
mute, and switch between earpiece/speakerphone.
|
||||
|
||||
3. Integration with System Features
|
||||
- Permissions: Ensure the app requests and manages necessary permissions
|
||||
(microphone, camera for scanning QR codes, contacts, call history, local storage).
|
||||
- Integration with Contacts: Ensure that the app seamlessly integrates with the
|
||||
Android contacts and syncs correctly with the address book.
|
||||
- Notifications: Ensure that call notifications and ringtone works even when the app is in
|
||||
the background or the phone is locked.
|
||||
|
||||
4. Resource Management
|
||||
- Resource Efficiency: Ensure the app doesn’t excessively consume CPU or memory
|
||||
while operating, during idle times or on call.
|
||||
|
||||
5. Security and Privacy
|
||||
- App Encryption: Ensure that any stored and sensitive data is
|
||||
encrypted, or protected.
|
||||
- Secure Call Handling: Verify that calls are handled securely through the
|
||||
encrypted voice protocol.
|
||||
- Minimal Permissions: The app should ask for the least amount of permissions
|
||||
necessary to function.
|
||||
|
||||
6. Reliability
|
||||
- Crash Resistance: Test for the app’s stability, ensuring it doesn't crash or
|
||||
freeze during use.
|
||||
@ -24,34 +24,39 @@ We are confident in our current UX development path, and user feedback will be t
|
||||
|
||||
### Enhance credibility and grow project's reputation
|
||||
|
||||
- **Transparent Development:**
|
||||
- **Transparent Development:**
|
||||
Maintain a public roadmap and changelog to document every update and decision during the project's lifecycle.
|
||||
|
||||
- **Security Audits:**
|
||||
|
||||
- **Security Audits:**
|
||||
We will rely on our automatic tests and community experts to have organic and constant auditing.
|
||||
|
||||
- **Community Engagement:**
|
||||
- **Community Engagement:**
|
||||
Actively involve our user community in discussions, bug reports, and feature requests. Regularly update the community on progress and upcoming changes.
|
||||
|
||||
- **Open Source Best Practices:**
|
||||
|
||||
- **Open Source Best Practices:**
|
||||
Adhere to industry-standard coding practices, thorough documentation, and continuous integration/deployment pipelines to ensure high-quality, maintainable code.
|
||||
|
||||
- **Visibility in Key Forums:**
|
||||
|
||||
- **Visibility in Key Forums:**
|
||||
Present and share our work in open-source, cybersecurity, and privacy-focused conferences and events to enhance credibility and attract constructive feedback.
|
||||
|
||||
### optimize relationships with the target audience
|
||||
|
||||
|
||||
|
||||
### Establish strategic partnership
|
||||
|
||||
- **Academic Collaborations:**
|
||||
- **Academic Collaborations:**
|
||||
Partner with academic institutions for research initiatives and validation of our protocol, leveraging their expertise for further improvements.
|
||||
|
||||
- **Industry Alliances:**
|
||||
|
||||
- **Industry Alliances:**
|
||||
Seek partnerships with established players in the open-source software industry to benefit from their wide community coverage, such as AOSP / GrapheneOS / LineageOS.
|
||||
|
||||
- **Integration Opportunities:**
|
||||
|
||||
- **Integration Opportunities:**
|
||||
Explore collaborations with mobile operating systems (e.g., AOSP) and VoIP providers to integrate Icing into existing communication infrastructures.
|
||||
|
||||
- **Joint Innovation Projects:**
|
||||
|
||||
- **Joint Innovation Projects:**
|
||||
Engage in co-development efforts that align with our mission, ensuring that both parties contribute to and benefit from technological advancements.
|
||||
|
||||
- **Funding and Support:**
|
||||
|
||||
- **Funding and Support:**
|
||||
Identify and pursue grants, sponsorships, and research funding that align with the project's objectives, ensuring sustainable development.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user