Henrique , I also appreciate your commitment . But I appeal again: How many hours did you work last week about it? Enjoy the weekend! Take advantage of the late summer ! Especially when there is a lot of work, you should relax!

Henrique , I also appreciate your commitment . But I appeal again: How many hours did you work last week about it? Enjoy the weekend! Take advantage of the late summer ! Especially when there is a lot of work, you should relax!

Hello excuse me disturb you but AndroidPIT 2.0 application in French lacks functionality compared to the German language we lack the status of the profile pictures and he impossible to create a topic is this normal ?

Pickers provide a simple way to select a single value from a set. In addition to touching the up/down arrow buttons, it's possible to set the desired value from the keyboard or via a swipe gesture.

Well, there's no right or wrong, but only useful/usable or not useful/usable.

Please don't use the Google developer guide lines as a bible without any failures. I highly recommend to think about features and usability for your own. The Google guide lines were not explicit dedicated to create a community forum app - these guide lines just give a rough direction. They never ment to be strict requirements. There would be *no* invention if everybody would do exactly what Google defined in their guide lines.

In terms of this "jump to page" feature, there are several things that make this feature not perfect.

1) The feature only appears within a thread to jump to the thread pages. We also need that feature for travelling through the pages of each thread listing.

2) There's no indictator within a thread listing or a thread, on which page I am. But this is important as the user needs some orientation. See the old app - the indicator where I am is shown in the upper right corner of each thread or page.

3) The number picker dialog you created, is scrolling way to slow. Try it with a thread like "Millionenzähler" which has several thousands of pages. And compare the behaviour and speed with the scrolling speed of the listview in the old app.

4) The number picker looks not clear. See the number picker sample at the web page you mentioned - there's a clear difference between the maximum and minimum value and the entry field (entry field black font, max/min values grey font). In your dialog it's all the same font and color and as I opend it the first time, I didn't know what to do. I saw three numbers separated by blue lines - that's not intuitive and self-explanatory.

Again, please see the things not only from a developer perspective who is fixated on Google guide lines. Please see the things from a user and usability perspective. This app, the forum, the magazin and your app section is a very vital part of the business of your company. And a community forum has to be designed to encourage users to use it, to create threads, to read and to help others. Therefore the app needs to be intuitive and fast. It must provide intelligent features to handle the forum and travelling through it. Every missing vital feature, every lack of usability will cost your company users and customers.

Keep up your great work, but please think a bit more about the features UI you're implementing. Not only the design is key, but most of all the usability!

Pickers provide a simple way to select a single value from a set. In addition to touching the up/down arrow buttons, it's possible to set the desired value from the keyboard or via a swipe gesture.

Well, there's no right or wrong, but only useful/usable or not useful/usable.

Please don't use the Google developer guide lines as a bible without any failures. I highly recommend to think about features and usability for your own. The Google guide lines were not explicit dedicated to create a community forum app - these guide lines just give a rough direction. They never ment to be strict requirements. There would be *no* invention if everybody would do exactly what Google defined in their guide lines.

In terms of this "jump to page" feature, there are several things that make this feature not perfect.

1) The feature only appears within a thread to jump to the thread pages. We also need that feature for travelling through the pages of each thread listing.

2) There's no indictator within a thread listing or a thread, on which page I am. But this is important as the user needs some orientation. See the old app - the indicator where I am is shown in the upper right corner of each thread or page.

3) The number picker dialog you created, is scrolling way to slow. Try it with a thread like "Millionenzähler" which has several thousands of pages. And compare the behaviour and speed with the scrolling speed of the listview in the old app.

4) The number picker looks not clear. See the number picker sample at the web page you mentioned - there's a clear difference between the maximum and minimum value and the entry field (entry field black font, max/min values grey font). In your dialog it's all the same font and color and as I opend it the first time, I didn't know what to do. I saw three numbers separated by blue lines - that's not intuitive and self-explanatory.

Again, please see the things not only from a developer perspective who is fixated on Google guide lines. Please see the things from a user and usability perspective. This app, the forum, the magazin and your app section is a very vital part of the business of your company. And a community forum has to be designed to encourage users to use it, to create threads, to read and to help others. Therefore the app needs to be intuitive and fast. It must provide intelligent features to handle the forum and travelling through it. Every missing vital feature, every lack of usability will cost your company users and customers.

Keep up your great work, but please think a bit more about the features UI you're implementing. Not only the design is key, but most of all the usability!

You should never use what you're used to as a guideline. The new app uses a different UI, it's not supposed to look like the old app, everyone will need to adapt, which should be very easy because we're using the same UI concepts that Google apps use.

The website I gave is the usability and user experience guidelines for Android. It's not from a developer perspective.

In the old app, the behavior is not intuitive because it jumps from page 21 to 31 for example. What if I want to jump to page 22? It doesn't make sense to go to page 21 and then press next. Since it jumps every 10 pages, it's obviously faster to navigate. The "one million thread" is not representative of the German forum.

The jump to page feature that is now implemented was a quick fix because all of you were crying for that feature. It will improve.

Also, the "jump to page" feature actually depends on the user knowing to which page to jump to in advance, which might change if the number of items per page changes. Even worse, having to long press to jump to a page is even worse, that's why we now have the "jump to page" in the action bar.

The long press in a thread to show options is also not intuitive, that is also going to be changed. Only users that know that behavior from the old app or actually try long pressing to see what happens, will know that something is there.