User data preservation needs to be prioritized. I no longer trust product updates.
I appreciate these things can be frustrating but I donât believe using language like that in a public forum, is ever necessary.
Is this more appropriate⌠Losing data sucks, its as simple as that. The postman development team has a track record of not respecting user data. This is not a new problem.
Is the team even aware that data is commonly lost? Iâve lost entire workspaces when upgrading versions and now when being forced to create an account.
Iâve lost trust in new versions of the product to the point that I go out of my way to avoid updates.
Unfortunately, sometimes those updates are forced. Is that what you want the end user experience to be?
They donât care even one bit. They knew this would piss off a huge chunk of the user base, calculated the effect on the bottom line, and did it anyway. The shills on these forums can only make excuses âuse the new offline modeâ, âbut it sucksâ, âÂŻ_(ă)_/ÂŻâ
Find another product to use. Postman is dead.
The offline Lightweight API Client is there for you to use completely for free, the same goes for the signed version. There is no cost associated with this on your part. The âshillsâ on this site and saying that because thatâs whatâs available to you.
I could list all of the various features that you get with the free version which includes an Enterprise grade app, Team Based Collaboration functionality, Multiple protocol request capabilities, Collection Runner, Monitors, Mock Servers, Flows, Postbot, the use of our Postman CLI, Postman API and the vscode extensionâŚand I havenât even scratched the surface of whatâs available to you for free.
As well as that, you get the free use of this Community Forum, the support team, all of our content across YouTube, the Learning Center, The Academy and other training courses and material.
If just not fair to say that we donât care.
If all of that free stuff is not for you, thatâs perfectly fine. You need to make the choices that are relevant and in line with your own context.
We provide export features for you to extract your data to use wherever you feel is right for you.
If required, I will personally make myself available for a call next week, if there is anything else youâd like to discuss. We can jump on a video call and talk about it all.
Youâre a shill because you make excuses while actively avoiding addressing the core of what Iâm saying. I had a whole library of pre-defined API calls made that I used frequently. Postman offered me a âchoiceâ of store that in the cloud, or lose access to it. No, the JSON export does not count as having retained access. You deliberately crippled your own product to force account signups - the least you could do is own up to it and provide an archival version that isnât crippled.
I understand your âin the cloudâ offering is probably great, however it was your ânot in the cloudâ offering that Iâd been using for years and had invested time and effort in that I am now pissed off about losing with no alternative given except âwell, sign upâ
If you care, make an old, uncrippled, version of Postman available and link to it here, otherwise, save your sales pitch and platitudes for someone who cares.
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.