You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the projects github.io webpage, there is an image of the mobile UI.
However, when you click on it to view the entire UI, the UI is a bit different: the graph is different and the white text is not on the same line anymore.
I think it would be better if the both pictures were the same and if the entire UI screenshot had the iPhone mockup border. The reason for the iPhone border is that since the UI is pretty minimalistic/flat, it looks bad when it's just hanging out against the white browser background.
In writing this, it might even be better to just have the image get larger (modal/lightbox-style) and have arrows pointing to different parts of the UI (e.g. what is the graph showing, what is the search box for). It wouldn't be a huge in-depth UI explanation, but just a teaser informational kind of thing.
The text was updated successfully, but these errors were encountered:
Great observation Tanner, I didn't notice as I was making both of these at different times :)
I will make sure to adopt your recommendation once I get behind Photoshop, and I'll leave this issue open as a reminder.
On the projects github.io webpage, there is an image of the mobile UI.
However, when you click on it to view the entire UI, the UI is a bit different: the graph is different and the white text is not on the same line anymore.
I think it would be better if the both pictures were the same and if the entire UI screenshot had the iPhone mockup border. The reason for the iPhone border is that since the UI is pretty minimalistic/flat, it looks bad when it's just hanging out against the white browser background.
In writing this, it might even be better to just have the image get larger (modal/lightbox-style) and have arrows pointing to different parts of the UI (e.g. what is the graph showing, what is the search box for). It wouldn't be a huge in-depth UI explanation, but just a teaser informational kind of thing.
The text was updated successfully, but these errors were encountered: