Serif, fire your Affinity 2.0 interface designers.

[GRAFKOM]

I'm getting tired of working in Affinity 2.0. I use Publisher for my daily work, there are some nice improvements in this version, but the interface is terrible. Why move things that no one complained about?

Among other things, I mean the way of presenting a group of a selected font family. Who was bothered by the good looks in the V1. It was necessary to mess up in the V2 version so that you can't see if the font group is being developed?

Serif please. Hire people to design the interface who have ever worked on graphic programs before and know what a program should look like that does not require special glasses, a magnifying glass and adequate sunlight in the room.

I want to pay for hiring such a programmer - give me the price and account number.

[Tia Lapis]

Care to explain what we are supposed to see here? Looks very similar to me...

[GRAFKOM]

Spójrz na strzałki po lewej stronie - oznaczają rozszerzenie grupy.

Czy dobrze widzisz w nowym interfejsie Affinity 2?

[MikeTO]

Please be kind

I think those light arrows on a light background are a glitch that should be fixed in one of the first patches, there are a few other things like this which have been reported and which Serif has added to their list to fix. The font menus are identical on macOS so I think this was just an oversight.

  

[Tia Lapis]

Looks fine for me on Mac. But I'm running on high contrast.

[GRAFKOM]

I didn't write before, but this feler is present in the Windows 11 version.

And of course, described in other threads - a bad decision to redesign the appearance of the Stroke panel and not entirely accurate changes in the Layers panel.

I just wonder how so many shortcomings were not noticed before the release of the full 2.0 version.

Of course, not releasing the Beta version and keeping the development of the new version 2.0 in great secrecy did not work out for Serif.

[MikeTO]

In my opinion, there are fewer of these UI glitches like this light icon on a light background in the dark mode, so maybe it's time for you to switch to the Dark Side.  🙂 

[Tia Lapis]

29 minutes ago, MikeTO said:

In my opinion, there are fewer of these UI glitches like this light icon on a light background in the dark mode, so maybe it's time for you to switch to the Dark Side.  🙂 

Yeah I have switched to dark mode for the time till fixes come in, too. With high contrast it's useable.

[debraspicher]

On Windows with Dark mode. Same issue as OP.

[Granddaddy]

Thanks for pointing out yet another example of Affinity 2 making things unreadable. High Contrast setting actually reduces contrast for many/most UI elements

https://forum.affinity.serif.com/index.php?/topic/173835-what-ergonomic-design-principles-call-for-minimal-contrast-and-reduced-readability-in-user-interfaces/&do=findComment&comment=1000160

 

[Granddaddy]

Let us not be too hasty when calling for people to be fired. Remember that someone chose and hired the designers, approved their designs,  signed off on their work, and got the designs included in the Affinity code base.

When I was young I thought that some employees in my organization should be fired for various errors or inabilities.  As I progressed into management of larger groups, I learned otherwise. 

I eventually realized that management is always the problem when things do not go well.

A manager's purpose is to make it possible for his subordinates to succeed in their work. Why else would we need managers? Of what use could they possibly be otherwise?

Managers assign tasks to appropriate workers, evaluate that work, and explain to the worker why it is or is not acceptable. If it is not acceptable, the manager explains what must be done to make it acceptable. A manager identifies a worker's abilities and assigns him to jobs where he can succeed. He arranges for the worker to get the training he needs to succeed in his assignments.

As a manager for nearly 40 years, I am most proud of extricating a worker (a college dropout) from a menial clerical position in another department, installing him as a programmer in my department, and rallying my other employees to contribute to his work designing and implementing the system we had conceived to support the users of our services.

After a couple of years he had succeeded beyond our wildest dreams. He left our organization to found his own company,  taking a few other employees with him. As president and CEO of his own company over the past 25 years, he now employs 32 people, including several software engineers. designers, and user support and training specialists for his several innovative software products. I helped him move on by assuring that he retained the intellectual property rights to the software he developed while working in my department. 

So,  I think that firing workers is a last resort and quite often the result of poor management decisions. Managers and the managers of managers might need to reassess their work as managers.

In the case of the regression in the Affinity user interface we might ask:

Who wrote the specifications for the Affinity 2 interface redesign? What were the goals? What were the principles to be followed? How was success to be measured?

Who chose the designers and explained their jobs to them?

Who provided feedback as the work proceeded?

Who approved and signed off on the Affinity 2 interface design as it was delivered? Did it fulfill the original expectations?

What is senior management doing to ensure success in fixing the problems and preventing similar problems in the future?

[deeds]

4 minutes ago, Granddaddy said:

Who approved and signed off on the Affinity 2 interface design as it was delivered? Did it fulfill the original expectations?

What is senior management doing to ensure success in fixing the problems and preventing similar problems in the future?

 

They got the sales they wanted, and then some...

So there's no need for them to consider the problems to be anything other than gripes in the forums. 

[Callum]

Hi All I apologise for the delayed response to this thread it looks as though this might have slipped through the net while we we're busy with the V2 launch. From what I can see this issue doesn't occur on my Windows 2.0.4 build does this issue still occur for you?

Thanks
C