If you expect the browser to help you manage your various workflows beyond generic containers (tabs, tab groups), then you become tied into the browser's way of doing things. Are you sure you want that?
I'm not saying your hopes are bad, exactly. I'm interested in what such workflows might look like. Maybe there _is_ a good UX for a web shopping assistant. I have an inkling you could cobble something interesting together quite fast with an agentic browser and a note-taking webapp. But I do worry that such a app will become yet another way for its owner to surveil their users in some of the more accurate and intimate areas of their lives. Careful what you wish for, I reckon.
In the meantime, what's so hard about curating a Notepad/Notes/Obsidian/Org mode file, or Trello/Notion board to help you manage your projects?
shopping assistant was a specific example, but in the process of research, brainstorming, etc theres a bunch of different ways id like to see visualization and record of how i got somewhere, what was discarded, summary of what was retained, whats coming next, options for branching.
the web is a document structure, but browsing it doesnt need to be linear.
How can a PM do their job if they don't *care* about UX?
I mean... I know exactly happens because I've seen it more than once: the product slowly goes to shit. You get a bunch of PMs at various levels of seniority all pursuing separate goals, not collaborating, not actually working together to compose a coherent product; their production teams are actively encouraged to be siloed; features collide and overlap, or worse conflict; every component redefines what a button looks like; bundles bloat; you have three different rendering tools (ok, I've not seen that in practice but it seems to be encouraged by many "best practices") etc etc
Oh, I agree completely with you, sorry if that wasn't clear. The PM should, must, care about UX. Still, they don't always do, or at least end up not caring eventually, for various reasons.
I'm just responding to this:
> what were your Product Managers doing in the first place if tech writer is finding out about usability problems
They might very well be doing their job of caring about UX, by using the available expertise to find problems.
It's a bit like saying (forgive the imperfect analogy): what are the developers doing talking about corner cases in the business logic, isn't the PM doing their job?
Yes, they are. They are using the combined expertise in the team.
Let's allow the PMs to rely on the knowledge and insights of other people, shall we? Their job already isn't easy, even (or especially) if they care.
In my limited experience interacting with someone struggling with schizophrenia, it would seem not. They were often resistant to new information and strongly guided by decisions or ideas they'd held for a long time. It was part of the problem (as I saw it, from my position as a friend). I couldn't talk them out of ideas that were obviously (to me) going to lead them towards worse and more paranoid thought patterns & behaviour.
Allegedly the next gen MBPs will have a touch screen. I think Apple have pushed a touch-enabled macOS UI out a year ahead of the hardware: maybe to iron out issues; maybe 'cos they could... I worry that we're stuck with this shit for a few more years, 'til the touch screen goes the way of the touch bar.
These rumors about touchscreen MacBooks have been going around for at least 10 years. At this point I don't believe any of it. Especially with how they sell keyboards for iPads.
Guessing: it's not Blink, but it's easier to work with than Firefox's engine. I know people fork FF, but I vaguely recall hearing the engine itself was harder to separate and integrate into other systems. I'm sure someone closer to the issues can correct me.
I’m dumb and don’t understand the distinction you’re making.
elem.style.setProperty(‘—var-name’, newValue);
… will set a new value for the “constant”. The element will rerender with the new value. You can animate/automate these changes and the element will continue to rerebder with the updated value.
To me, that justifies the name “variable” from the perspective of the CSS.
It’s not obvious to me how black on yellow is a mistake. It’s quite readable, the contrast is broad enough for clarity but not so broad the background overwhelms the foreground. Yellow’s a recommended “light” background for visually impaired people so the choice has precedance (although I confess that many other examples of it I’ve seen use a softer pastel yellow which is more comfortable).
The huge area of intense yellow (or any highly saturated color actually) is very jarring. The eyes get tired quickly. It's really a weird choice coming from a person who is apparently into visual communication.
Btw, I'm using a desktop PC with a large browser window. Maybe on a small mobile screen the problem is less apparent.
Sure, but "white" has a pretty similar effect, especially on modern high lumen screens. "Dark mode" is popular for a reason.
Personally, anecdotally, I find the black-on-yellow easier to work with than most sites' black-on-white. I just tested it with my screen at two or three brightness levels, and it was more comfortable than similar content against white. I'm over-sensitive to glare because my eyes lack pigment. I _think_ this makes me more susceptible to contrast issues (it certainly feels like it, but I am only n=1 and I've not done careful study). I'm open to being challenged on this but you'll have to come with broad audience data to contradict a lot of lived experience.
It's fair that you might not like the black-on-yellow; you might feel it's a poor branding choice; but I still contest that it's not "wrong" for any technical, perceptual reason.
Academia should be for exploration, research, or preservation/archival. It’s about knowledge, not profit.
Academic attainment should be about the subject.
It’s business that should deal with the application, the short cuts, the “ends” rather than the means.
I’m sure there’s a formulation of this which also allows for AI in acedemia. I’m not srguing for that kind of purity. But I am saying that acedemia shouldn’t be treated as the training ground for employment.
I'm not saying your hopes are bad, exactly. I'm interested in what such workflows might look like. Maybe there _is_ a good UX for a web shopping assistant. I have an inkling you could cobble something interesting together quite fast with an agentic browser and a note-taking webapp. But I do worry that such a app will become yet another way for its owner to surveil their users in some of the more accurate and intimate areas of their lives. Careful what you wish for, I reckon.
In the meantime, what's so hard about curating a Notepad/Notes/Obsidian/Org mode file, or Trello/Notion board to help you manage your projects?
reply