Orange-OpenSource / Orange-OpenSource/ouds-ios
In `library`, expose sensory feeback if iOS 17+ for components
Open
Nobody has claimed this yet.
⚛️ component
👂 accessibility
🔍 triage
🛠️ technical
🧰 library
- Dominant language
- Swift
- Stars
- 35
- Forks
- 11
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 18
Description
Description
With iOS 17 we can use sensory feedback, i.e. use haptics (success, errors, warnings) is a condition if filled.
It can be usefull for example for:
- the button component if we move from loader to not loader
- the text input component if we move from loader to not loader
See attached what should look like components implementations
Motivation & Context
Improve accessibility and use newer API
Types of change
- Add new component
- Update existing component
Checklist for Core Team
- Tokens have been updated
- Documentations have been updated
- Unit tests have been updated
- UI tests have been updated
- Design System Toolbox has been updated
- Retrocompatibility has been checked, or broken API have been flagged as deprecated with a workaround
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the attached Swift samples and locate the library’s button and text input component implementations. Check how sensory feedback should apply when loading changes to not loading on iOS 17+, while preserving the stated retrocompatibility requirement; done means the affected components provide this behavior without breaking older iOS versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100