Cockatrice: Implement "Tip of the day" style feature

Created on 31 Jan 2015  Â·  24Comments  Â·  Source: Cockatrice/Cockatrice

One of the big UI problems we have is that we have a lot of features that aren't very discoverable. Something like intellij's tip of the day feature would help people find out about them

  • Card arrows
  • Buddy list
  • [[card]], [card], and [url]
  • Handling bottom deck cards
  • How to play face down
  • Confusion about when other player can see cardnames - drawing card, etc
  • What the user shirts mean

Example: http://www.javaspecialists.eu/courses/concurrency/setup/idea12.png

Hacktoberfest Roadmap Suggestion UI / UX

Most helpful comment

i think this should be in a normal repo instead of the wiki (this one or another; i have no preference). my 2 reasons for this are 1) the wiki should be reserved for information about the client/server/project, not used for storing metadata files, and 2) the wiki is potentially susceptible to vandalism, since it is community-editable without approval (good for documentation, bad for resources that will be automatically download by every client and then parsed)

All 24 comments

We can have a list of tips, a seen flag in the config (tips/seenCardArrowTip -> true) and cycle through them. Most useful/important tips first

I like this. Especially since we are adding a lot of features now.

I'm a fan, and users can opt out of if they'd like (at which points mods should just refuse their dumb questions relating to something we explain)

Were would the list of items to display to the user be pulled from?

Server operator's Database

And pulled down to the client? Or is it something presented to the user on connect?

Pulled and presented after the user logs into the server

You mean like a popup? That would get annoying real fast.

Disable-able at any point with a little checkbox on the physical popup

I would still want to get message of the day. Maybe it would be better built into the client. Maybe under the user list in each room? Or in the server tab.

They would be hard coded in the client. That way we can use it to message
about new features. This doesn't need to have any server side knowledge

On Tue, Sep 15, 2015, 2:12 AM poixen [email protected] wrote:

I would still want to get message of the day. Maybe it would be better
built into the client. Maybe under the user list in each room? Or in the
server tab.

—
Reply to this email directly or view it on GitHub
https://github.com/Cockatrice/Cockatrice/issues/652#issuecomment-140290819
.

I'll grab some screenshots of a version other software uses

On Tue, Sep 15, 2015, 6:59 AM Gavin Bisesi [email protected] wrote:

They would be hard coded in the client. That way we can use it to message
about new features. This doesn't need to have any server side knowledge

On Tue, Sep 15, 2015, 2:12 AM poixen [email protected] wrote:

I would still want to get message of the day. Maybe it would be better
built into the client. Maybe under the user list in each room? Or in the
server tab.

—
Reply to this email directly or view it on GitHub
https://github.com/Cockatrice/Cockatrice/issues/652#issuecomment-140290819
.

I was thinking you wanted something client side, but the problem with that idea is the list of items would never change to display to the user till they upgraded there client. This shouldnt be that hard to implement. Just want clarification before some one (like myself) starts.

That's kind of the point though. It should inform them about what they can
do. The update alerting is a separate thing.

On Tue, Sep 15, 2015 at 7:49 AM woogerboy21 [email protected]
wrote:

I was thinking you wanted something client side, but the problem with that
idea is the list of items would never change to display to the user till
they upgraded there client.

—
Reply to this email directly or view it on GitHub
https://github.com/Cockatrice/Cockatrice/issues/652#issuecomment-140366030
.

screen shot 2015-09-15 at 7 59 14 am

So this covers the key points for me; checkbox to disable it, scroll buttons for when the user wants to see more.

Embedded screenshots are pretty nice but not needed for MVP.

Another idea coming to my mind is...

I know these kind of "Tip of the day" dialog popups at app start. Well, most of the time you are kinda annoyed by them because you open the app to quickly do something and often don't have the time to or just don't want to read about things that don't help you with your particular problem at the moment. Especially if you happen to know/use the app for some time. (you still haven't mastered it yet for sure... but anyway)
A bit like a manual, not as worse for sure. :)

I know from another game, that they have something like changing tips of the day as well, but they are implemented into the loading screen, so you're actually happy getting entertained and read them. This way you learn new stuff and are not annoyed at all.
While we don't have a particular loading screen... we could place our tips here for example:
totd

@tooomm that's reasonable, but I'd like to start with just on-launch tips

I'd like to help out on this if possible :D.

@Beat1823 poke me on gitter tomorrow and I'll walk you through where we are now and what's left.

(Sorry, I don't know why i didn't get this notification.)
I realize this is a month after but I would still like to walk thru how i can help!
I poked you on gitter.

Hey @Beat1823 We'll try to help you out. Weird how you didn't get a notification...

So my idea of where to get the Tips from will be the GitHub wiki, we can create a table on a page and as long as you follow the table the tips can be properly parsed.

ID | ADD_DATE | TIP | IMAGE
--- | --- | --- | ---
0 | 2018-02-16 | There is now a loyalty filter in the deck editor! | N/A
1 | 2018-02-16 | You can check for new client updates by going to ... | Image.PNG

i think this should be in a normal repo instead of the wiki (this one or another; i have no preference). my 2 reasons for this are 1) the wiki should be reserved for information about the client/server/project, not used for storing metadata files, and 2) the wiki is potentially susceptible to vandalism, since it is community-editable without approval (good for documentation, bad for resources that will be automatically download by every client and then parsed)

Not a bad idea!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Gibidinp picture Gibidinp  Â·  7Comments

ShrewMaster picture ShrewMaster  Â·  6Comments

TheMasterpass picture TheMasterpass  Â·  4Comments

dev-id picture dev-id  Â·  6Comments

tooomm picture tooomm  Â·  6Comments