For Solid to have a solution that “anyone” including my father can use, the experience must really be much less technical than it is today. I know there is some very skilled people working on a UI right now, so this is not a UI proposal, just some thoughts from what I have seen today and what could be done to make it easier to adapt for the masses.
The main concept is a Dashboard that is interactive and also shows you relations between things, for example who/what you shared your data with. Be able to call instantly from contacts, add appointment directly to calendar and so on.
Please feel free to chat with me on Gitter and/or add comments to this interactive Prototype, that includes a login and a Dashboard that visualise some of my ideas.
We will continue hacking on the React App improved experience, mainly logic stuff, rewrite some solid libs to ES6 etc…, but we will not put any UI focus until the Solid UI will arrive. We could always use a hand, we have big day time projects to deliver as well, senior level ES6+ and React is required.
Dashboards are a really cool concept, and something we usually see more as an app-specific dashboard(one that just one website on its own would implement).
General user dashboards haven’t yet reached a climax in terms of innovation, I personally think, so it’s cool that you’re working on this.
In terms of the design: I really like how you have the colored blocks on each div section(ex. the blue indicator next to My Profile). I also really like how you set this grid up and are demonstrating all of the different features of Solid, mainly who you choose to share your data with.
The two things I’d watch out for is spacing, especially on the navbar, and content nesting(how much content you put in each panel), especially for calendar and health. What I’m getting from the design is that you want the user to get a general feel for the content and then have an expanded view when they click at it, so it might be more important for your own purposes to capitalize on how captivating you can make the panel’s design can be.
@adventure, nice it could help for a quick start but I encountered a bug : I was logged as holacratie.solid.community and want to explore smag0.solid.community/public . When I want to see subfolders, as smag0.solid.community/public/blog but altought this folder is public, I’ve no right.
It looks that the part ‘public’ in the URL as disappear and it looks at smag0.solid.community/blog
. See this pics
But it looks ok if I put the trailing / as https://smag0.solid.community/public/
I’ve not been thinking about design though - still fermenting. I’ve not given up but also not sure if my idea is worth continuing with, as it would be a lot of work. So I was not planning to think more about this part, and was going back to play with a different area of the concept that lead me to think about that. The original seed was more spoggy like stuff (visualisation and interactive UI), so I’m going to look at and play with visualisation stuff I think.
I understand, it is sensitive, you have put the / at the end, like: https://smago.solid.community/ I do have a version that does not require / if you think that would be bettor. It’s in the mashlib, I could probably edit that feature out for the instance of this use?