4 ms·
So maybe you'd like to share what do you think of LStack UX? Regarding password fields - that was conscious choice not to mask them. Do you think it could have
by seele 15y ago
So maybe you'd like to share what do you think of LStack UX?
Regarding password fields - that was conscious choice not to mask them. Do you think it could have negative impact on users acquisition?
- jollyjerry 15y agoSome notes as I go through the app: The bookmarklet popup is spot on. Everything I need, nothing I don't. The home tab shows signup info even when I'm logged in, should hide after I'm logged in. For passwords, I think it'd be best to hide them because it's the convention, and add a js link to "show password" for users who want to see it.
- seele 15y agoThanks for the advices! How about the service itself? Do you find the smart tags (parameters attached to bookmarked link) useful in your use cases?
- jollyjerry 15y agointeresting idea, but haven't formed an opinion yet. Tagging's always such a personal preference. I like hierarchical tags (e.g. code:ruby), but that's just me
- seele 15y agoI think of them as parameters rather than tags, maybe should change the name in descriptions (using "smart tags" can be misleading).
- seele 15y agoSign up button for logged in users not displayed from now.