Configuration strings/policy for MDM rollout of app
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
Research direction
The payload names no source files or tests. The request is for MDM-delivered configuration (keyboardLangs and defaultKBLang) that sets the keyboard languages and default language on managed devices. Start by finding where the app stores its enabled keyboard languages and default layout, then decide how managed configuration would be read. The issue does not define the design or the done state, so a maintainer must agree on the approach before any code is written.
Written by the indexing model from the issue text.
Description
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
Support for MDM policy/configuration strings. Can the app be set up to receive configuration data from an MDM policy? I looked in issues and discussions but couldn't find anything when searching for "MDM" or "policy".
Why do you want this feature?
I want to roll out this app at my place of work (non-commercial gov't org.) without having to manually set the correct keyboard language for every phone. Being able to configure something like { "keyboardLangs": "en,de,fr", "defaultKBLang": "fr" } via Intune would be fantastic.
Additional information
If this already exists then it should be exposed in some documentation somewhere.
- Dominant language
- Kotlin
- Stars
- 678
- Forks
- 84
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from FossifyOrg/Keyboard
-
Error of the Ukrainian keyboard layoutPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
FossifyOrg/Keyboard#487 · 1 comment ·
Maintainers usually reply within 5 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Keyboard#484 ·
Maintainers usually reply within 5 days
-
bug needs triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
FossifyOrg/Keyboard#462 · 1 comment ·
Maintainers usually reply within 5 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 18/100
FossifyOrg/Keyboard#450 ·
Maintainers usually reply within 5 days
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
FossifyOrg/Keyboard#447 ·
Maintainers usually reply within 5 days
All issues in FossifyOrg/Keyboard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
utopia-rise/godot-jvm#1004 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
pedroSG94/RootEncoder#2213 ·
Maintainers usually reply within 2 days
-
coding good first issue size:xs skill:kotlin-core sub-issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
SKaiNET-developers/SKaiNET#1323 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dzid26/TeslaBatteryBLE#183 ·
Maintainers usually reply within 1 day