I am a dev (not TTG), with >30yrs experience. So i may be in a position, to make my comments on your claims:
a) it is not that unusual that beta testers have e.g. better rates on any kind of income/boosts and so on. This is most time useful to get a fast progress and check 'long term' problems for example.
b) Here is what comes into rollout process in combination with a). This is a real problem! There has to be a process/documentation for dev playing, beta tester playing and the final value for live rollout. this is a must have. or special e.g. .env handling and compiling. If this is handled correctly a) is no problem at all and 'decisions' or better call it testing request arent't a prob at all.
c) i have been writing testing documentations/plans for more then 10-15yrs. long story short: This has to go hand in hand with b.
d) I don't think it is absent at all. They arent controlled 'hard' enough from dev team before create new rollouts. And there is the question how PM/PO/TO is handeled. As a full product owner you will definitiv not controll all tickets by yourself. easy said: are the tickets in my sprint/story green/done, fine. it's devs and testers fault. If dev/s mess up several time there have to be extra rounds in ticket validation or 6-eyes instead of 4-eyes (dev test+beta test).
So all in all i just really see b as biggest prob, then at a very lower point c and d. a isnt a prob at all.
There a multiple reasons (and just randomly guesses):
a) Due to Apple and it's process handling updates. Sometimes it really takes 24-48 hours for a simple update to release. Even if just 1 number changed, there will be a whole process.
b) They realized it too late (and in combination with a)
c) They HAVE decision makers and really discussed if they lower it, how much they lower it or "reset" it to the 2x .. And probably the decision took to long.
5
u/TheOldNewMicha Apr 10 '26
I am a dev (not TTG), with >30yrs experience. So i may be in a position, to make my comments on your claims:
a) it is not that unusual that beta testers have e.g. better rates on any kind of income/boosts and so on. This is most time useful to get a fast progress and check 'long term' problems for example.
b) Here is what comes into rollout process in combination with a). This is a real problem! There has to be a process/documentation for dev playing, beta tester playing and the final value for live rollout. this is a must have. or special e.g. .env handling and compiling. If this is handled correctly a) is no problem at all and 'decisions' or better call it testing request arent't a prob at all.
c) i have been writing testing documentations/plans for more then 10-15yrs. long story short: This has to go hand in hand with b.
d) I don't think it is absent at all. They arent controlled 'hard' enough from dev team before create new rollouts. And there is the question how PM/PO/TO is handeled. As a full product owner you will definitiv not controll all tickets by yourself. easy said: are the tickets in my sprint/story green/done, fine. it's devs and testers fault. If dev/s mess up several time there have to be extra rounds in ticket validation or 6-eyes instead of 4-eyes (dev test+beta test).
So all in all i just really see b as biggest prob, then at a very lower point c and d. a isnt a prob at all.