Decision on app navigation

[JayBrizle]

I think the design for the app navigation should get settled on before we get too deep in features added. The 3 main patterns currently are Dashboard, Slide panels, and Tabs it seems. Any thoughts or visuals(Maxim is a great drawing artist lol) on this?

[JaeW]

Where's your Android super hero? I miss him . . .

[JaeW]

So what's the video reference? Do you want to add video tutorials/hints or something like that?

[mgolokhov]

As always in the background =)

[JaeW]

Nice!

[mgolokhov]

Link to the motivational video

[JaeW]

Oh yeah . . . how could I possibly forget about the motivational video?

[JaeW]

Okay, so you have the drawer with navigation. Will that be a permanent item on the screen? Or a pull-out like in the English grammar app?

[mgolokhov]

Pull-out style

[JaeW]

Nice. I like the pull-out. Will it contain an app-map, kind of like a website site map? Or something else?

[mgolokhov]

Navigation as in the gmail app

[JaeW]

Makes sense. Okay, so does the start screen have questions? Or what does it display? We really need to give your Droid super hero a name. ;-)

[mgolokhov]

just do it button )))

[JaeW]

K. So they press the button . . . where does that take them?

[mgolokhov]

[mgolokhov]

questions-questions... navigation by swipe

[JaeW]

So, when they first hit this page will it tell the user to select from the spinner tags? What will the options/overflow menu do? Instead of the 'Commit' button, what about one of the new floating buttons? Like in the Gmail app - bottom right-hand side.

[JaeW]

So I totally get that this app is for programmers, but programmers are still neurologically wired the same way as the rest of the species. Therefore, if you want this to be good - if you really want people to use it and get benefit from it I would suggest taking a look at these design guidelines. For instance, people work best when work/learning is divided into "chunks." So maybe give them a series of 10 questions then give them feedback. When the get a question right it helps to give them a small reward. Hitting milestones should trigger something fun and unexpected. That kind of thing.

[JaeW]

Questions make you think about how you want things to work . . . . or they just annoy the flying f*ck out of you. Questions are helping or . . . . . not?

[mgolokhov]

Totally agree. Should be

• chunks
• progress
• category
• ....

Same stuff as in the English app. We'll do it step by step. My primary goal is to build QuestionActivity (working horse activity), so students can play with it now.

[JaeW]

A more limited scope is good.

So we assume anyone using it (for now) is in Part 1? That would eliminate levels for now.

What needs to be decided before the first Activity is built?

[JaeW]

So this is pretty cool. If you're interested in the different options on the navigation drawer.

[JaeW]

Last question, although it should have been my first. How can I best help? I'm done with the class - I have time this week..

[mgolokhov]

Anyone can use (folks from Part 2 can refresh old topics). Nothing holds us (except labs and laziness) to build this Activity =) Nobody canceled navigation graphs.

[mgolokhov]

You can review questions, build app, ask your questions about code, draw your UI sketches...

[JaeW]

I did some work on the ViewPager, but I think it will require slight re-design. Currently you display the questions in the main activity. Because ViewPager container needs to be inflated from an android.support.v4.view.ViewPager view I'm pretty sure you can't put it into a generic ViewGroup. Would you (both) be okay with putting the questions into a separate activity?

[mgolokhov]

Your fork is a bit outdated, try this https://help.github.com/articles/syncing-a-fork/

[JaeW]

My bad. I'll check it out tonight. On Nov 18, 2015 4:28 PM, "Maxim Golokhov" notifications@github.com wrote:

Your fork is a bit outdated, try this https://help.github.com/articles/syncing-a-fork/

— Reply to this email directly or view it on GitHub https://github.com/mgolokhov/dodroid/issues/16#issuecomment-157885411.

[mgolokhov]

android.support.v4.view.ViewPager view I'm pretty sure you can't put it into a generic ViewGroup

As a ViewGroup successor it should be ok to use it inside other ViewGroup, then you can find it by method findViewById()

In the latest app version I reverted to two activities=)

[mgolokhov]

By the way, in windows os you need to install python 2.7 and put it in sys PATH. You also can comment line in the script build.gradle
preBuild.dependsOn exportQuestions;

[mgolokhov]

@shiraeeshi What about having two buttons "commit" and "next" visible at the same time? If user clicks next without committing, it means that he skipped the question and will return to it later (after the last question in the set). If user answers wrong, he has two options: either try one more time or move to the next question. But if user can try one question more then one times, doesn't it break the statistics? If user doesn't know the right answer and tries to guess it, he will make his statistics worse and worse with every commit. I need to understand the statistics logic you are implementing.

[mgolokhov]

Two buttons at the same time is bad, because we loose pixels. That's why we implemented viewpager with swipe (the first version was with buttons). Still we can have settings for such things.