Subpage under development, new version coming soon!
Subject: »[info]Dev Diary #82: Automatic release of NT-players from
We are not confused, a little bit of trust please:)
Navigation is a seperate part of our work, its quite advanced, but still during our work we have small adjustments, graphic designers are working on previous mock ups (becouse often our work is going in pararell)- thats why sometimes navigation presented on the screenshot is not 100% final one - especially in screens that are dedicated to give you news about graphic design.
Our question from current dev diary is simple, its just a discussion about one widget, not whole page - notification box:)
Navigation is a seperate part of our work, its quite advanced, but still during our work we have small adjustments, graphic designers are working on previous mock ups (becouse often our work is going in pararell)- thats why sometimes navigation presented on the screenshot is not 100% final one - especially in screens that are dedicated to give you news about graphic design.
Our question from current dev diary is simple, its just a discussion about one widget, not whole page - notification box:)
I totally agree. a notification system is absolutely necessary. for new and experienced users. on the other hand, to be useful, the notifications will have to be reduced to those that are really important :)
its just a discussion about one widget, not whole page - notification box:)
You are right, i did not read well your announcement. I was fooled by the fact that the mockup presented the whole page, when it was only the box, and by the particular mockup of this box. But, sorry, its remain confuse ^^
This box should be MAINLY an entry point to a so-called "notification center" page (and i assume the icon bell too?) like any other "widget" box; and not only entries point for each events because this box can't show all (important) events at once, never. Its a slider. We can't click and click and click (or waiting the auto-slide) to discover all and many events. We need a list of ALL events to read at once : a "notification center" page. That's why i didn't understand the usefulness of this box and didn't not understand your whole announcement.
In term of data this box should show, in order :
1) A box header ("Last events", or "New events, or "notification", anyway). NOT in your mockup.
2) The title of the event. OK *
3) The description of the event. OK *
4) a direct link associated with the event. OK *
5) a button to "all events" (notification page). NOT in your mockup.
* Due to the UX limitation (Its a pain to slide too many events, once by once) this box should be limited to 4 URGENT task. So this box cant be a notification overview page.
You are right, i did not read well your announcement. I was fooled by the fact that the mockup presented the whole page, when it was only the box, and by the particular mockup of this box. But, sorry, its remain confuse ^^
This box should be MAINLY an entry point to a so-called "notification center" page (and i assume the icon bell too?) like any other "widget" box; and not only entries point for each events because this box can't show all (important) events at once, never. Its a slider. We can't click and click and click (or waiting the auto-slide) to discover all and many events. We need a list of ALL events to read at once : a "notification center" page. That's why i didn't understand the usefulness of this box and didn't not understand your whole announcement.
In term of data this box should show, in order :
1) A box header ("Last events", or "New events, or "notification", anyway). NOT in your mockup.
2) The title of the event. OK *
3) The description of the event. OK *
4) a direct link associated with the event. OK *
5) a button to "all events" (notification page). NOT in your mockup.
* Due to the UX limitation (Its a pain to slide too many events, once by once) this box should be limited to 4 URGENT task. So this box cant be a notification overview page.
agree, thats why we proposed few in dev diary, but its good to verify them here before we will develop that page, so thanks to all for input:)
We just decided, that as long as you will find there only urgent and crucial events, in most cases you will have 1-3 alerts, and all of them will be important enough to solve them one by one - but sure, thats a good tip, to make an option to show them all.
You are right with the header, but maybe we can mark that widget by graphic design (like different color, etc.) to ensure proper stand out. If not - there will be still a space for upgrade.
You are right with the header, but maybe we can mark that widget by graphic design (like different color, etc.) to ensure proper stand out. If not - there will be still a space for upgrade.
Don't agree at all actually..
For whatever you can there should be a notification. It's up to the user to decide which notifications he wants to receive and which he doesn't.
If (as an application) you limit the possibilities, then you don't give the user the opportunity enjoy the game at its fullest.
For whatever you can there should be a notification. It's up to the user to decide which notifications he wants to receive and which he doesn't.
If (as an application) you limit the possibilities, then you don't give the user the opportunity enjoy the game at its fullest.
perfect! if they can be customized, so that each user can select only the ones they want, it seems perfect.
but if that is not possible, then only the really important ones should be received.
most users would get tired of receiving notifications with very little importance and, in the end, they would not even see the ones that are important
but if that is not possible, then only the really important ones should be received.
most users would get tired of receiving notifications with very little importance and, in the end, they would not even see the ones that are important
If you can't select which notifications to receive, then imo you simply shouldn't implement notifications at all...
in most cases you will have 1-3 alerts
It can be more than 4 'urgent' alerts usually ? Just in your announcement i count 6. All 6 can happens at a same time (a week)...
You are right with the header, but maybe we can mark that widget by graphic design
Well... that's a problem with "mockups", it should be content first. All should be describe with content and not graphic things. Graphics design can't solve content design and could introduce constraint (is my content can "fit inside this particular visual box". for example...since when graphic design decide content that we need? )
In this particular mockup, we can use a "bell icon" as header, but graphic are not as strong as words to define things. Colors, requires convention and learning before understanding. And we can't save so much space with graphic, in contrary, graphic can add noises and take spaces. But is it really important to save spaces ? for what?
In the end we need a link in this box to reach a notification page (since i can count 20-30 type of "urgent or not" events, it's impossible to display all this).
It can be more than 4 'urgent' alerts usually ? Just in your announcement i count 6. All 6 can happens at a same time (a week)...
You are right with the header, but maybe we can mark that widget by graphic design
Well... that's a problem with "mockups", it should be content first. All should be describe with content and not graphic things. Graphics design can't solve content design and could introduce constraint (is my content can "fit inside this particular visual box". for example...since when graphic design decide content that we need? )
In this particular mockup, we can use a "bell icon" as header, but graphic are not as strong as words to define things. Colors, requires convention and learning before understanding. And we can't save so much space with graphic, in contrary, graphic can add noises and take spaces. But is it really important to save spaces ? for what?
In the end we need a link in this box to reach a notification page (since i can count 20-30 type of "urgent or not" events, it's impossible to display all this).
There are few places where game will give you different informations.
1. overview page - we should focus only for most urgent ones, crucial for game (like if you will not take that action, it will hurt you somehow). So, here we need a list of top important alerts, i belive its quite short.
2. Ring bell at the top right of menu - its current notifications system, so all "small" events during the game - someone bid yor transfer offer, etc.).
3. Pressroom - its a place to use some storytelling, but also inform about important events in the game, we belive here is a great potential to engage users - from my perspective, in pressroom you can get informationas about: NT games, health reports (injuries status), club records, league summaries, and lot more.
@Oliver Aton and jeetn - here is also an answer for your concerns - i think point 2 & 3 would be able to customize and set for your own needs, urgent alerts (point 1) are few and important for all.
So i think we end with max 10 types of "urgent" alerts on overview page.
It can be more than 4 'urgent' alerts usually ? Just in your announcement i count 6. All 6 can happens at a same time (a week)...
Well, for experienced user probably it will be hard to get to many alerts here, but for newcomers it could be more (and thats good, to help them start). Anyway - i get your point, its already transmited to our UX designer, so give us a while.
1. overview page - we should focus only for most urgent ones, crucial for game (like if you will not take that action, it will hurt you somehow). So, here we need a list of top important alerts, i belive its quite short.
2. Ring bell at the top right of menu - its current notifications system, so all "small" events during the game - someone bid yor transfer offer, etc.).
3. Pressroom - its a place to use some storytelling, but also inform about important events in the game, we belive here is a great potential to engage users - from my perspective, in pressroom you can get informationas about: NT games, health reports (injuries status), club records, league summaries, and lot more.
@Oliver Aton and jeetn - here is also an answer for your concerns - i think point 2 & 3 would be able to customize and set for your own needs, urgent alerts (point 1) are few and important for all.
So i think we end with max 10 types of "urgent" alerts on overview page.
It can be more than 4 'urgent' alerts usually ? Just in your announcement i count 6. All 6 can happens at a same time (a week)...
Well, for experienced user probably it will be hard to get to many alerts here, but for newcomers it could be more (and thats good, to help them start). Anyway - i get your point, its already transmited to our UX designer, so give us a while.
hey raul:
how is it going the match viewer ?
is the most important think to solve by far on the game. i think that flash will be useless at the end of the december and not at the begining...
how is it going the match viewer ?
is the most important think to solve by far on the game. i think that flash will be useless at the end of the december and not at the begining...
if our predictions will be accurate, we will have current match viewer rewritten from flash maybe with the end of this month (probably for tests).
In pararell we are working with new match viewer, and here our deadline is and of december.
So for now it looks quite safe.
In pararell we are working with new match viewer, and here our deadline is and of december.
So for now it looks quite safe.
Will we have the new match viewer in december?
Will the current (rewritten) disappear? Does it mean that rewritten match viewer only will be available for a month?
(edited)
Will the current (rewritten) disappear? Does it mean that rewritten match viewer only will be available for a month?
(edited)
We will rather keep both for a while and see how many users still uses old one.
"and see how many users still uses old one. "
In the first week everybody will try the new one, at least 2-3 times.
So, better start counting how many users still use the old one, on the second week after the release.
In the first week everybody will try the new one, at least 2-3 times.
So, better start counting how many users still use the old one, on the second week after the release.