// case note
Deux: relationship aware mobile communication
Relationship-aware mobile communication product
A private mobile communication app for conversations that need more context than a normal chat thread.
Solo full-stack development: React Native app, backend APIs, authentication, chat, contacts, invites, reminders, AI coach surfaces, and Android/iOS test builds.
Shows that I can build a real mobile product with private data flows, realtime communication, sensitive UX, and product thinking beyond basic CRUD.
_context
Deux is a personal mobile product developed over roughly a year. It is not meant to be another noisy chat interface; it explores private conversations where tone, timing, repair, and relationship context matter.
_contribution
I designed and built the app solo across mobile and backend: screens, navigation, authentication, contact flows, private chat, reminders, AI-assisted communication surfaces, data handling, and Android/iOS test distribution.
_stack
_what-I-built
- React Native mobile app with account screens, navigation, private chat, and relationship-oriented flows.
- Backend APIs for authentication, contacts, conversations, invites, reminders, and app state.
- AI coach surfaces for message review, private feedback, and shared mediator-style support.
- Android and iOS test builds with practical QA around chat, contacts, push, and app flows.
_what-it-demonstrates
- Relationship-centered messaging model focused on calmer, clearer private exchanges.
- Full-stack mobile engineering with React Native, TypeScript, backend APIs, realtime chat, contacts, invites, reminders, and test distribution.
- AI-assisted conversation support designed as private guidance, not a generic chatbot bolted onto chat.
_value
Deux demonstrates my ability to connect mobile engineering, backend architecture, realtime communication, privacy-aware UX, and product strategy into one coherent application.
_details-on-request
Some details related to private data, product logic, and the roadmap are not public. I can discuss the scope, technical choices, and user experience in a professional conversation.