Reward for reporting undocumented bugs.

[Affinity Rat]

Why doesnt Serif offer reward in terms of discount towards future purchases the percentage based on the number of unreported bugs reported.

I wouldnt benefit from this but Serif and ultimately all users might. Certainly some members of forum seem to be actively involved anyway, maybe they should reap some reward for their efforts.

[Meliora spero]

The ultimate reward in this regard can be found at Vectorstyler, where reported bugs are often fixed within the same month or week.

Serif seems willing to lose customers by letting bugs go unresolved for many years. I do not imagine they want to pay money for people to report bugs that just end up hanging in a system. Hundreds of bugs have already been reported.

Note, I am not making any judgments about whether there are intentions behind their business strategy and I do not want to discuss it to death here as it does not help. But this is the result of their business model, their entire business model and approach to the customer-supplier relationship.

[Affinity Rat]

38 minutes ago, Aldus said:

Serif seems willing to lose customers by letting bugs go unresolved for many years. I do not imagine they want to pay money for people to report bugs that just end up hanging in a system. Hundreds of bugs have already been reported.

I wasnt suggesting payment, but merely discount having reached established reporting limits.

Market pressure always pushes developers to release products early they even advertise features they dont offer..YET, then push devs nose to the grindstone to get it done. and then rely on users to help fine tune and debug. Thats software development.

 

 

 

[Meliora spero]

15 minutes ago, Affinity Rat said:

I wasnt suggesting payment, but merely discount having reached established reporting limits.

Market pressure always pushes developers to release products early they even advertise features they dont offer..YET, then push devs nose to the grindstone to get it done. and then rely on users to help fine tune and debug. Thats software development.

Discount is still payment, reward. And no, you simply cannot compare companies in such a generic, overarching, and apologetic way. That is certainly not my long experience with companies.

Read around in this forum. There is plenty of feedback for Serif on this point.

[Affinity Rat]

I disagree, but are you advocating against incentives for my premise of offering rewards that users assist in making a product better?

Just curious, why are you here?

I’m here because I like the company, and their products and like to see them get better and succeed.

ps Wasnt Aldus a software company that originally created desktop PageMaker and vector based Freehand, and was later purchased by Adobe?

https://en.wikipedia.org/wiki/Aldus_Corporation

[NotMyFault]

After about 10 years of Affinity Apps at least for me it is clear that Affinity has absolutely no intention to fix (or identify) all bugs in the way e.g. of D.E. Knuth handles bugs (in software and books). The number of documented unfixed bugs is the dimension of several hundreds or thousands, and the pace of bugfixes is far slower than new bugs gets observed. Affinity was a promoted App by Apple during launch of M1 silicon in 2020, and it is painful that some M1 related rendering bugs seem to not getting fixed before this generation is rated obsolete after 5 years next year. I‘m affected both with Mac and iPad.

So I get to the conclusion that Affinity is not even interested into getting all bugs documented, as this creates effort on Affinity side for user support, and development. Many bugs affect only specific platforms or rarely used tools, so this approach seems to work in general as bugs lading to crash or corrupt files get some attention and fixes (later than sooner).

New features seem to get more ROI vs bug fixing, and 80/20 is the new „perfect“.

[Affinity Rat]

Being aware of bugs at least allow a decision to be made, whether they are worth pursuing..Reporting of numerous bugs would apprise devs which are effecting the most users, allowing them to prioritize their efforts.

I suspect that security on Apple devices, is problem, devs have to constantly circumnavigate.

This is further support for my Pizza restaurant business model as mentioned in other posts, which would allow for core and commonly used

functionality to be relatively bug free.

 

19 minutes ago, NotMyFault said:

New features seem to get more ROI vs bug fixing, and 80/20 is the new „perfect“.

Yes, exactly what I meant regarding software dev, push it out the door.

[Affinity Rat]

43 minutes ago, NotMyFault said:

After about 10 years of Affinity Apps at least for me it is clear that Affinity has absolutely no intention to fix (or identify) all bugs in the way e.g. of D.E. Knuth handles bugs (in software and books). The number of documented unfixed bugs is the dimension of several hundreds or thousands, and the pace of bugfixes is far slower than new bugs gets observed. Affinity was a promoted App by Apple during launch of M1 silicon in 2020, and it is painful that some M1 related rendering bugs seem to not getting fixed before this generation is rated obsolete after 5 years next year. I‘m affected both with Mac and iPad.

So I get to the conclusion that Affinity is not even interested into getting all bugs documented, as this creates effort on Affinity side for user support, and development. Many bugs affect only specific platforms or rarely used tools, so this approach seems to work in general as bugs lading to crash or corrupt files get some attention and fixes (later than sooner).

New features seem to get more ROI vs bug fixing, and 80/20 is the new „perfect“.

In general I wouldnt disagree with with what you are saying, but suspect that some bugs particularly associated with new hardware maybe difficult to repair without a major rebuild. Every new dev cycle introduces more bugs, unless a complete from scratch rewrite, which has its own new bugs it never ends so must be satisfied with core and commonly used functionality to satisfy ROI, as you say perfect.

 

 

[NotMyFault]

10 minutes ago, Affinity Rat said:

Every new dev cycle introduces more bugs, unless a complete from scratch rewrite, which has its own new bugs it never ends so must be satisfied with core and commonly used functionality to satisfy ROI, as you say perfect.

This time I tend to disagree. If you do your DevSecOps properly and include a reasonable amount of testing, most new bugs would be caught and fixed before publishing as beta or retail.

a fair amount of bugs can be identified by automated testing - just open some assorted test documents, take a screenshot of the result, and compare to the reference screenshot. Dead simple. In the company I work for we do a lot of Robotic Process Automation and Application Monitoring. (I‘m not in that Area, but use the service for monitoring some services I’m responsible for)

The big issue of Affinity is the lacking of full scripting (of every UI function).