Jump to content

Talk:MyFitnessPal regressive upgrade: Difference between revisions

Add topic
From Consumer Rights Wiki
 
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== To what extent is this anti-consumer, vs just being a skill issue from the company? ==
==To what extent is this anti-consumer, vs just being a skill issue from the company?==


There's a good level of detail here (and i've removed the stub notice as such) but having read through it I'm left wondering to what extent this is an anti-consumer issue as opposed to a simple case of a product update being bad. it doesn't sound like they are refusing refunds, or otherwise doing anything beyond pushing a bad update (and moving free features to paid is also not really anti-consumer on account of free users not having paid anything in the first place).
There's a good level of detail here (and i've removed the stub notice as such) but having read through it I'm left wondering to what extent this is an anti-consumer issue as opposed to a simple case of a product update being bad. it doesn't sound like they are refusing refunds, or otherwise doing anything beyond pushing a bad update (and moving free features to paid is also not really anti-consumer on account of free users not having paid anything in the first place).


I suppose the strongest case for this article's relevance is that subscribers had something they bought made worse by the company after they bought it (although presumably the users would actually be expecting the service to change, just only in ways they liked) but this is weakened on account of it being a subscription rather than a purchase. [[User:Keith|Keith]] ([[User talk:Keith|talk]]) 18:03, 5 November 2025 (UTC)
I suppose the strongest case for this article's relevance is that subscribers had something they bought made worse by the company after they bought it (although presumably the users would actually be expecting the service to change, just only in ways they liked) but this is weakened on account of it being a subscription rather than a purchase. [[User:Keith|Keith]] ([[User talk:Keith|talk]]) 18:03, 5 November 2025 (UTC)
:Hi Keith,
:I haven't finished it yet - I suffer from quite severe health conditions so I have to work on it iteratively.
:Yes I agree the first pass it's not obvious what the consumer abuse is. It leans too far into "I didn't like the update"
:I will be working on that to fix it - the issue is squarely that they rug pulled critical features that paid long term subscribers depend on, without which their workflow becomes not just hard, actually completely impossible.. so they are stuck sitting on their thumbs, unable to use the product while the dev team says "please wait"
:So a paid service has suddenly become completely unusable - due to removed required features, and an interface that is so sluggish that it is literally not usable.. like its not slow.. it's unusable - and then the support team just gaslights, and refuses refunds.
:You can see my own report for that:
:https://mdbin.pages.dev/2hkttm [[User:Jmorgannz|Jmorgannz]] ([[User talk:Jmorgannz|talk]]) 22:40, 5 November 2025 (UTC)
:Being weakened on account of it being a subscription - this is annual for many.
:This is part of the core issue. They have retracted core functionality and then people have actually prepaid for up to 12 months, and are being refused refunds. [[User:Jmorgannz|Jmorgannz]] ([[User talk:Jmorgannz|talk]]) 22:42, 5 November 2025 (UTC)
:I have updated the article to forefront the core consumer rights breaches. [[User:Jmorgannz|Jmorgannz]] ([[User talk:Jmorgannz|talk]]) 00:04, 6 November 2025 (UTC)
:Hi Keith,
:I have now made my final update.
:There is a section in there about "Impact on User Health and Well-being" - I felt this was important, but was concerned about sticking to the Wiki guidelines. I made sure to substantiate any claims made with references - however if this section is just not suitable it can be dropped. [[User:Jmorgannz|Jmorgannz]] ([[User talk:Jmorgannz|talk]]) 06:06, 7 November 2025 (UTC)
::Thanks for working on it! I think the only thing that might be worth doing from this point is putting front and centre (maybe in the intro) the lack of refunds towards customers who've purchased their subscription in advance as this is, in my mind, the central actionable consumer rights issue. The customers bought a year of service x, only to have it swapped out for the inferior updated service after y without any reasonable ability to opt-out. [[User:Keith|Keith]] ([[User talk:Keith|talk]]) 13:47, 7 November 2025 (UTC)

Latest revision as of 13:47, 7 November 2025

To what extent is this anti-consumer, vs just being a skill issue from the company?

[edit source]

There's a good level of detail here (and i've removed the stub notice as such) but having read through it I'm left wondering to what extent this is an anti-consumer issue as opposed to a simple case of a product update being bad. it doesn't sound like they are refusing refunds, or otherwise doing anything beyond pushing a bad update (and moving free features to paid is also not really anti-consumer on account of free users not having paid anything in the first place).

I suppose the strongest case for this article's relevance is that subscribers had something they bought made worse by the company after they bought it (although presumably the users would actually be expecting the service to change, just only in ways they liked) but this is weakened on account of it being a subscription rather than a purchase. Keith (talk) 18:03, 5 November 2025 (UTC)Reply

Hi Keith,
I haven't finished it yet - I suffer from quite severe health conditions so I have to work on it iteratively.
Yes I agree the first pass it's not obvious what the consumer abuse is. It leans too far into "I didn't like the update"
I will be working on that to fix it - the issue is squarely that they rug pulled critical features that paid long term subscribers depend on, without which their workflow becomes not just hard, actually completely impossible.. so they are stuck sitting on their thumbs, unable to use the product while the dev team says "please wait"
So a paid service has suddenly become completely unusable - due to removed required features, and an interface that is so sluggish that it is literally not usable.. like its not slow.. it's unusable - and then the support team just gaslights, and refuses refunds.
You can see my own report for that:
https://mdbin.pages.dev/2hkttm Jmorgannz (talk) 22:40, 5 November 2025 (UTC)Reply
Being weakened on account of it being a subscription - this is annual for many.
This is part of the core issue. They have retracted core functionality and then people have actually prepaid for up to 12 months, and are being refused refunds. Jmorgannz (talk) 22:42, 5 November 2025 (UTC)Reply
I have updated the article to forefront the core consumer rights breaches. Jmorgannz (talk) 00:04, 6 November 2025 (UTC)Reply
Hi Keith,
I have now made my final update.
There is a section in there about "Impact on User Health and Well-being" - I felt this was important, but was concerned about sticking to the Wiki guidelines. I made sure to substantiate any claims made with references - however if this section is just not suitable it can be dropped. Jmorgannz (talk) 06:06, 7 November 2025 (UTC)Reply
Thanks for working on it! I think the only thing that might be worth doing from this point is putting front and centre (maybe in the intro) the lack of refunds towards customers who've purchased their subscription in advance as this is, in my mind, the central actionable consumer rights issue. The customers bought a year of service x, only to have it swapped out for the inferior updated service after y without any reasonable ability to opt-out. Keith (talk) 13:47, 7 November 2025 (UTC)Reply