Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mobile control #123

Open
peteruithoven opened this issue Mar 24, 2014 · 6 comments
Open

Mobile control #123

peteruithoven opened this issue Mar 24, 2014 · 6 comments

Comments

@peteruithoven
Copy link
Collaborator

Let's brainstorm on controlling Jetzt on mobile platforms like phones and tablets, where we are mostly limited to touch.
We could for example split up the screen in different areas where each area has a function. A first attempt:
mouse areas

Another option is using swipe gestures, using a library like Hammer.js.
A first attempt:

  • swiping left: go back a sentence
  • swiping right: go forward a sentence
  • swiping up: increase speed
  • swiping down: decrease speed
  • pinching: zooming
    In combination with:
  • click on reader: pause
  • click on background: close

Ideas and opinions are welcome.

@ds300
Copy link
Owner

ds300 commented Mar 24, 2014

pinch to zoom? I like the idea of just having labelled buttons in the places where you've put the boxes, but with pause on the bottom right.

I think by far the biggest problem is figuring out how to start jetzt and select content to read. At least in the context of a browser. Firefox mobile has extensions, which is great, but others don't so you're very limited by bookmarklets.

@peteruithoven
Copy link
Collaborator Author

Nice, added pinch to zoom.
What I was thinking was showing hints when the reader is opened for a moment and than fading them out (like the OS X / iOS scrollbars). They could show up again when you move the mouse or touch the screen. This would keep the reader very "clean" / "calm".
What do you mean with labelled buttons?

True, but I don't really know a solution, so I thought to fix the issues I could fix first.

@peteruithoven
Copy link
Collaborator Author

Why put pause bottom right? Because the label might overlap the reader?

@nomicode
Copy link
Contributor

I believe those "boxes" are meant to represent "hot" areas of the screen, and would not actually be visible.

I prefer the swipe idea. Feels a lot more natural. No need for a tutorial. Most well designed gestures come naturally to people who are familiar with touch screens. You could have a little "?" in one of the corners with a single screen help graphic.

@peteruithoven have you looked at Apache Cordova? Would it be possible to package jetzt up as an actual app we distribute through the App Store? See #76 for more.

@ds300
Copy link
Owner

ds300 commented Mar 24, 2014

I like both of your ideas and and now dislike my own so 👍

@peteruithoven
Copy link
Collaborator Author

@nslater, nop, I don't really feel like paying apple 100,- per year to get into their store or to even get it on my phone. But I'm sure someone else does.
We could make a "WebApp", with hints on how to add it to the homescreen, iOS and Chrome on Android now allow this and of course Firefox OS.
But I think this is a topic for a separate issue.

I like the ? in a corner idea, this would be usefull to show the keys as well.

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

No branches or pull requests

3 participants