[MGNLUI-59] As a user, I can "run" the UI on a smartphone Created: 28/Aug/12  Updated: 14/Dec/15  Resolved: 14/Dec/15

Status: Closed
Project: Magnolia UI
Component/s: user interaction
Affects Version/s: 5.2
Fix Version/s: None

Type: Story Priority: Major
Reporter: Andreas Weder Assignee: Andreas Weder
Resolution: Outdated Votes: 0
Labels: ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
is superseded by MGNLUI-18 Test on Android Tablet Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

We currently don't support smart phones with Magnolia 5+. That is deliberate: we don't just want to enable touch support, but properly serve every device class with an interface that makes sense. Simply enabling our current UI would offer many hard to read and hard to touch elements on small screens.

However, it seems that this gets requested significantly more recently and also seems to be asked by customers, so we should reconsider it.

The current state seems to be that simply enabling GWT permutation for smart phones doesn't seem to do the trick, as there remain to be issues with scrolling and page layout in general, which have to be addressed.



 Comments   
Comment by Andreas Weder [ 24/Oct/12 ]

Lowering the priority of this.

Comment by Christopher Zimmermann [ 17/Dec/12 ]

Stopped in-progress status as priority is lowered.
The GWT generation is kind of tricky. its easy to add devices to the get.xml files, but adding devices makes the compilation of magnolia_ui project take much longer. It may also give hudson problems (would need to confirm).
Best strategy for now might just be to add the smartphone devices in a commented out line in the file, then people could enable them locally when they want to test.

Comment by Mikaël Geljić [ 03/Dec/13 ]

Small update:

  • Adding generation of permutations for smartphone isn't a big deal, we currently build 11 permutations.
    • maximum permutation count to my knowledge was 12, maybe ie10 permutation added one or two more, but again no big issue.
    • we would then remove the "Unsupported Browser" page when requesting a non-existing widgetset
      • most likely replace it with a warning "Not optimized for this browser" message upon login
  • The main problem is that the whole interface is highly unusable at all on smaller devices.
    • We may need more tolerant layouts and a responsive approach to get there
    • or for the time being compute a different viewport zoom or disable such static zooming.
Comment by Andreas Weder [ 14/Dec/15 ]

This is an old issue, I thus close it. There's no significant concept or convincing idea currently on what we wanted to achieve with this. We might go with native apps, or a web app, a reduced feature set or the full one...

Generated at Mon Feb 12 08:33:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.