Responsive for linux apps (to make them usable on Linux Mobile OS)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- react, typescript
- Domain
- frontend, mobile-dev
Research direction
No files or tests are named. Begin by reproducing the interface on the reported postmarketOS, Phosh, OnePlus 6T setup and trace the responsive UI entry points; the work is done when the Proton applications are usable on small touch screens.
Written by the indexing model from the issue text.
Description
We are happy to answer your questions about the code or discuss technical ideas.
Please complete the following checklist (by adding [x]):
- I have searched open and closed issues for duplicates
- This isn't a feature request
- This is not a report about my app not working as expected
Linux mobile devices are starting to gain traction and maturity. While the ecosystem is not perfect yet, it is becoming increasingly usable. Supporting this movement with well-adapted Proton applications would make a significant difference.
At the moment, however, the current releases are not very mobile-friendly.
For example, Proton Pass is now distributed unofficially on Flathub, and it recently gained an aarch64 release, which was great to see: https://github.com/flathub/me.proton.Pass
Unfortunately, after opening the application on a Linux mobile device, it became clear that the interface is not responsive enough for small touch screens.
Would it be possible to improve the responsiveness of the applications and better support smaller/mobile Linux screens?
Thank you for your work and for considering Linux mobile users.
Screenshot:
System:
- OS: postmarketos
- UI: phosh
- Device: OnePlus 6T
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 715
- PR merge metrics
- No merged PRs in 30d
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.
More from ProtonMail/WebClients
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ProtonMail/WebClients#539 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
ProtonMail/WebClients#537 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ProtonMail/WebClients#524 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
ProtonMail/WebClients#541 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
ProtonMail/WebClients#535 ·
All issues in ProtonMail/WebClients
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·