The app in question uses LLMs to analyze golf swings from recorded videos. Users were still getting their analysis (which can saved to your photo gallery), it's just that the data wasn't being stored as part of the users account. The core functionality was working perfectly.
This is the perfect example of what I was trying to illustrate: technical experts would immediately flag this as "broken" because data persistence failed, but from the user's perspective, the app was delivering what they paid for.
Yes, it's not perfect, but the users didn't seem to mind as it was still solving their problem.
saith the "programmer",
but it works on my laptop!?
If your backend is returning "empty responses" for a week and people are paying for it, that's just ripping people off.
In this case, they were quite clearly NOT doing that - it wasn't WORKING!The app in question uses LLMs to analyze golf swings from recorded videos. Users were still getting their analysis (which can saved to your photo gallery), it's just that the data wasn't being stored as part of the users account. The core functionality was working perfectly.
This is the perfect example of what I was trying to illustrate: technical experts would immediately flag this as "broken" because data persistence failed, but from the user's perspective, the app was delivering what they paid for.
Yes, it's not perfect, but the users didn't seem to mind as it was still solving their problem.