1) Login with Google is just a way to make it simpler for us for an MVP (and as you note we need the photos as we don't have a direct photo upload in this product just yet).
2) The graph is a reflection of intensity of the story (basically the more photos you take, the more interesting stuff is going on around you) and it gives you a time context for how things went.
We will definitely add an explanation in the interface.
3) What kind of customization do you mean? Structural (move things around) or cosmetic (colors, etc).
Basically the graph is firstly a navigation tool. You click on the event names to move to that moment in all the views of the app (album photo grid/large photo view/album edit mode).
4) The map widget starts centered in Slovakia (center of Europe) for non-geotagged photos. This does not mean that the location was assigned to the album, it is just how the widget renders. (Does it look like we automatically assign the position? Any idea on how the map widget could look to avoid this confusion?)
For geotagged we are of course working on using this information (it is no there yet).
5) It is all about the context (graph - time context, info boxes - POI in the area or related concepts).
6) The problem with empty space in the timeline is that once you start 'stretching' and 'compressing' it, the time axis will stop being homogeneous which sort of ruins the effect of 'at-a-glance' time awareness.
If there was a big block of down-time on the holiday, why do you want to mask it by covering the gap in the graph? The representation loses faithfulness that way. But maybe a faithful representation is not that desired here, hmm :-D
2) I see, but that still means that the data is shown twice, doesn't it? Once in the little bar-graphy-thingy to the right and once in the name placement.
3) Both structural and cosmetic would be nice. I know that at the moment the graph is for navigation only, but why not make it another tool to tell an aspect of my story? Don't worry about it at the moment, that's something for the roadmap.
4) Wow, yeah, that is confusing. Why don't you start out with an empty map widget (without the location marker) or just a link that says "add a location" or something of that sort.
5) Yes, it is, and that's why it's important to let the user enter them. That you add them automatically is nice, but not always perfect, as you can see on one of your demos, http://mystorify.com/a/BjYb08qE. The first and the last fields are obviously not what you'd want there. Also, again the question, why not allow it as a tool to complement my story?
6) Exactly. =) Start out with a good automatic timeline, but let me edit it anyway. What if I have highly inhomogenous events? Perhaps, I don't know, two vacations to the same place. That would probably show up as a month or even a year display, but a gapped timeline would be better in that case.
Comments
Wow terrific feedback, definitely appreciated!
1) Login with Google is just a way to make it simpler for us for an MVP (and as you note we need the photos as we don't have a direct photo upload in this product just yet).
2) The graph is a reflection of intensity of the story (basically the more photos you take, the more interesting stuff is going on around you) and it gives you a time context for how things went.
We will definitely add an explanation in the interface.
3) What kind of customization do you mean? Structural (move things around) or cosmetic (colors, etc). Basically the graph is firstly a navigation tool. You click on the event names to move to that moment in all the views of the app (album photo grid/large photo view/album edit mode).
4) The map widget starts centered in Slovakia (center of Europe) for non-geotagged photos. This does not mean that the location was assigned to the album, it is just how the widget renders. (Does it look like we automatically assign the position? Any idea on how the map widget could look to avoid this confusion?)
For geotagged we are of course working on using this information (it is no there yet).
5) It is all about the context (graph - time context, info boxes - POI in the area or related concepts).
6) The problem with empty space in the timeline is that once you start 'stretching' and 'compressing' it, the time axis will stop being homogeneous which sort of ruins the effect of 'at-a-glance' time awareness. If there was a big block of down-time on the holiday, why do you want to mask it by covering the gap in the graph? The representation loses faithfulness that way. But maybe a faithful representation is not that desired here, hmm :-D
2) I see, but that still means that the data is shown twice, doesn't it? Once in the little bar-graphy-thingy to the right and once in the name placement.
3) Both structural and cosmetic would be nice. I know that at the moment the graph is for navigation only, but why not make it another tool to tell an aspect of my story? Don't worry about it at the moment, that's something for the roadmap.
4) Wow, yeah, that is confusing. Why don't you start out with an empty map widget (without the location marker) or just a link that says "add a location" or something of that sort.
5) Yes, it is, and that's why it's important to let the user enter them. That you add them automatically is nice, but not always perfect, as you can see on one of your demos, http://mystorify.com/a/BjYb08qE. The first and the last fields are obviously not what you'd want there. Also, again the question, why not allow it as a tool to complement my story?
6) Exactly. =) Start out with a good automatic timeline, but let me edit it anyway. What if I have highly inhomogenous events? Perhaps, I don't know, two vacations to the same place. That would probably show up as a month or even a year display, but a gapped timeline would be better in that case.