RE: Steemit Roadmap 2018: Community Input Requested
1- Improve the signup process
Not only by accelerating the signups volume, but by making it easier. Most users are newbies, they don't have a sense of the complexity of Steem. Many lose their passwords minutes after getting approved. More information needs to be pushed to guide them on what to do. Simply mentioning to read the FAQ doesn't help, rarely do they read the FAQ. They need to be schooled in a quick and informative way (welcome video, tutorial page), before they start blogging.
2- Improve the UI layout
Steemit's UI is very basic and lacks an attractive punch. Every major website has a signature look that can be spotted from a mile away. Steemit.com doesn't. It's a header with a white background, not very appealing. Condenser must look good, sexy and attractive. Colors play a major psychological role that must be harnessed. It's one thing to push for advertising, but if the site looks bland, it's a turn-off. Image is everything.
3 - Optimize the header sections
The trending page is the worst of all. Always the same people are featured there with the same subjects. There's no diversity. Either remove the trending page or find a way to give more focus to other quality non-repetitive posts. Honestly I don't care about @sweetsssj's pretty face, where she travels, or what she eats. We need to see content with REAL value trending.
4 - Optimize the steemd resource requirements
This is already being worked on, as announced in HF20 months ago, i.e. multi-threading. Would be nice to have it implemented soon, as well as reduce the RAM usage.
The promoted Tab should include all whale and dolphin bot-enabled posts, while the Trending Tab should be actual organic views with lots of human activity.
You haven't switched to night-mode yet? You are missing out ;)
Oh I did try night mode, there' nothing innovative about reversing colors 😉. I think the website needs a signature design that people can remember and appreciate.
Great points, you said it better. Up vote!
Yeah, I think number 4 is pretty important. The blockchain API access has too much lag and too many errors. This is particularly important for app developers on top of the blockchain. There's a couple of well known services that I've used in my app development that have unacceptably high levels of failure and errors. I'd put it down to those services themselves, but I've seen similar error rates from my own programming interfacing directly with the steem API. It makes app development (and debugging) very hard.
Very true sir
Try to say something meaningful before upvoting yourself! You're spamming this post with useless lines.