Where the design community meets.
Berlin Joined almost 3 years ago
Hi Jasper, that looks very promising! What I miss for it to become useful for me:
What I think could be a problem (and why I really want Figma integration) is that the strings are not shown in context. Let's say we use 'Go' as a call to action in several places and then realize that's not a very good button label. How do we know which ones to change to "Sign up now" and "Send"?
About the commit messages: in my experience people find it difficult to write good commit messages. To be honest, I would also find it difficult to come up with a more useful example than used in the video: 'Demo test' without spending a significant amount of time on commit messages. Perhaps the default message should not be editable? Perhaps the default message could provide context to the developer? Perhaps the default message should have the same pattern that it has already, but authors can add an additional, optional comment that is used in the second line of the commit message?
Hey Mark, because it's already 2 months ago that you asked this and there's nothing specific you're asking for, here a few first impressions:
If you create a Wikipedia account, you can choose the mobile style as a default. That one is much less cluttered. You can also add custom CSS there so you don’t need that plugin.
I tried to figure out what the design process is at Wikipedia. I still don’t fully understand it, but it involves a lot of consensus building and making little changes. Looks like design by committee, where the committee is hundreds if not thousands of volunteers.
I found the reason for why there’s no max-width applied to the main body text on two discussion pages. A few people didn’t like it for reasons unrelated to legibility (‘I have a huge 21” screen and want to use all of it’—this was several years ago).
Just like in many other projects, the real design challenge is not about the graphic design, but about putting a user-centered design process in place.
I can’t see the image, but going by your description, “pannable canvas” or “endless canvas” perhaps?
Consider that your users may use nightshift/f.lux because they don’t want to look at blue light in the evening. I also found that especially dark blues tend to look very different with those modes enabled. It really becomes greenish, even when you’re used to the white balance shift.
To me they’re all confusing! Perhaps something like ‘12h ago?’
Hi Alex, what do you want to actieve with your writing? If it’s content marketing, if makes sense to write to the interests of your target group. I write mainly for myself and to just share whatever I’ve learned recently. The for myself part works best when I publish it in some form, because it makes me more careful to check sources, see the other side of things and it forces me to be precise in my writing and thus thinking.
As for topics I’d like designers to write about: less about tools and outcomes, more about ethics, collaboration, future visions, inclusiveness, design as a profession, aesthetics and applied behavior psychology.
For my own writing I use my notes app to collect ideas. I let them sit there for a while and whenever I have time, I go through them and pick one that I believe I can write something about from a perspective I haven’t seen before.
I think the usefulness of the concept depends on the application and users, so I’d try to do a bunch of tests with actual people.
My impression: 1. If the tabs look like tabs I guess they’re familiar enough. Right now they look like actions, the plus button in the center adds to that. 2. I find it counterintuitive to scroll up to get the bottom nav.
I like the creativity in the solution to work around that awful iOS Safari behavior. I don’t think it solves the problem you’re stating though. In the initial solution with the standard bottom nav, they’re a clear indication for users where to tap. In your new solution there isn’t. Another problem you had with the initial solution was that there are two actions necessary that aren’t 100% intuitive, because the buttons jump. With the new solutions you haven’t really solved that: it still requires 2 actions and the behavior of the nav appearing and disappearing is likely less predictable as it’s not standard iOS Safari behavior.
But that’s just me.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.