Been a bit of a silent month, due to a mix of holidays and very hard work.
As promised a month ago in the August Roadmap Update, we have allocated more resources to making II pretty-as-can-be (and functional, too). Thanks to David A. we’ve been able to restructure most of the styling code which will allow us to easily give II more personality and a more “modern” feel.
Speaking of modern, we’ve submitted a proposal to upgrade II’s UI slightly; the kind of upgrade where you go “I can’t put my finger on what’s changed but I like this more”:
Please feel free to try it out here before voting! (use this link if you want to authenticate from another dapp)
Ok, so what’s next?
Well, now that we’ve cleaned up the code, we’ll be moving fast and trying various new design ideas. As mentioned, this proposal/upgrade is conservative on purpose, but here’s something to whet your appetite…
We’ve got a ton more ideas which we’re looking forward to implementing and putting out here to get your feedback on. Please don’t be gentle, let us know what you think!
Very glad to see important UI/UX changes are been made to eliminate the previous classic feels that users get while using ICP tools and embrace a more modern approach.
Great work!
Please be! Well, maybe not a downer, but accessibility is important and the point of sharing those upgrades and ideas here is to gather feedback.
Cool, noted. We’ll try to find a way to work around that. Just to clarify, the screenshots with the gradients are still work in progress and won’t be released as part of this proposal.
Yeah that’s a very good point. We’ve been trying to figure out the best way to retrofit a footer in the current design and generally make II look more like a website/app as opposed to just an auth wizard
We’ve fixed the issues brought up here and some here, and submitted a follow-up proposal: 78551
Note that we went ahead with some of the new design (though a little improved) because some people really, really liked it! We left out the dark mode for now until we figure out the best way to work around the usability and accessibility issues mentioned here.