Skip to content
This repository has been archived by the owner on Jul 17, 2020. It is now read-only.

Not mobile friendly #349

Open
Bouncey opened this issue Jun 13, 2017 · 10 comments
Open

Not mobile friendly #349

Bouncey opened this issue Jun 13, 2017 · 10 comments

Comments

@Bouncey
Copy link
Member

Bouncey commented Jun 13, 2017

Not sure if this was a design decision, but the app is hard to navigate in mobile and there is information missing, i.e. who has submitted availability.

iPhone 5C, safari, latest iOS

Unable to use a different browser as this is a works phone

@jrogatis
Copy link
Collaborator

@Bouncey Its a initial design decision. But any help to enhance this aspect will be more them welcome!

@jrogatis jrogatis self-assigned this Jun 13, 2017
@jrogatis jrogatis removed their assignment Jun 13, 2017
@anischyros
Copy link
Contributor

I tried this with my iPhone 5C with Safari and agree that it is complicated to navigate, but not impossible. I was able to view an event I'd made previously, make some availability changes, and see all of the availability grid. I had to zoom in order to use the availability grid and swipe the display to one side or the other to see the entire display.

@jrogatis
Copy link
Collaborator

We need to refactor the grid component to be able to zoom in and out and scroll thru the days.

@chemok78
Copy link

I used it in Chrome on an Android phone and i noticed most parts of the website are responsive but the details page of the event(after you click "View Details") is not responsive. That makes it hard to use.

Also I am not able to swipe the grid on my mobile phone, it just doesn't respond.

@jrogatis
Copy link
Collaborator

@chemok78. Yap this component is the most important of the app. and is by design not responsive yet. Any help with ideas to improve that will be welcome!

@staadecker
Copy link
Contributor

Hello,

I'd like to help with this, but I am a beginner in React.

I already have everything setup and I can run a local version on my computer and phone. Any hints on where should I start?

@jrogatis
Copy link
Collaborator

about this @SUPERETDUPER . The main issue here is to figure out a possible refactor at the main component the grid. It's a good challenge, but maybe you need some time to understand react first.

@staadecker
Copy link
Contributor

@jrogatis I'll try and we'll see what happens :).

@staadecker
Copy link
Contributor

I think I do not have enough understanding of React to do this yet so if anyone else wants to work on this go ahead.

@jrogatis
Copy link
Collaborator

it's a hard one @SUPERETDUPER, this is by far the most complex component of the app...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants