This page describes a concept, not an available live version. The purchased domain is confirmed; there is no public app or landing page version.
OwnSay
Concept for an iPhone/iPad communication aid
OwnSay should support people who need help expressing needs, sentences, routines or responses. This page describes a concept and not a released App Store product.
Status
Processing
Account
Live version
01
About OwnSay
OwnSay is planned as a communication aid or AAC app concept for iPhone and iPad. The app should support people who want to express needs, routines, answers or prepared sentences through clear buttons, symbols or boards.
OwnSay is not in the App Store yet. This page describes a planned app and makes no medical, therapeutic or care-replacing promises.
02
Planned Communication Workflow
The planned workflow starts with categories or boards. Users select a quick button, symbol or phrase to make a statement visible or potentially output it later if that feature is implemented.
A caregiver or editing mode can help adjust boards, categories and quick buttons. The concrete implementation, permissions and data storage must be described transparently before a release.
03
Target Groups and Use Cases
OwnSay is intended for people who need support expressing needs, recurring routines, answers or simple sentences. Family members or caregivers may also play a role when setting up content.
The concept does not replace professional care, diagnosis, therapy or individual guidance. It can only be planned as a digital aid whose suitability depends on the concrete context.
04
Planned Technical Implementation
OwnSay is planned as an iPhone/iPad universal app. Core building blocks are communication boards, a local phrase/button library, an accessibility-aware interface and later support, privacy and accessibility pages for the landing page.
For the core concept, communication content is treated as device-near content. Cloud sync, accounts or a backend are not claimed as existing here and would need to be described separately before implementation.
05
Privacy, Accessibility and Limits
Communication content can be very sensitive. Before release, OwnSay therefore needs to clearly explain where content is stored, which permissions are required and whether data leaves the device.
Accessibility is part of the concept: clear buttons, readable states, operability on iPhone and iPad and a structure that makes later support and privacy information findable. OwnSay is still not a medical or therapeutic app.
Planned OwnSay User Journey
Choose board
Open a category or communication page.
Choose button or phrase
Select a prepared statement.
Show statement
Make the statement visible or output it later if implemented.
Adjust content
Maintain boards in caregiver or editing mode.
Find support
Find privacy, support and accessibility information through the landing page.
Planned OwnSay Architecture
A device-near communication flow should connect setup, boards, local phrase library and an accessibility-aware UI.
Hover or focus elements for details
Legend
- User
- Local in browser
- Storage
- Third Party
Features
Symbol/button communication planned
Prepare statements through clear buttons or symbols.
Custom quick buttons
Create important needs, phrases or answers.
Categories and boards
Structure content by situations or routines.
Editing mode
Adjust boards and buttons by users or caregivers.
Universal app planned
Concept for iPhone and iPad.
Accessible operation
Large targets, clear labels and understandable states.
Local content in the core concept
Plan the communication library close to the device, without claiming cloud features.
Support/privacy structure
A later landing page should make support, privacy and accessibility clearly findable.