charly1310

3 hours ago, Hemant Kumar said:

Thanks for your feedback, guys!

That was what we started with. The UWP app was the one that was working for both Windows 10 mobile and Windows 10 desktops. But the problem was very limited functionality and API support in UWP app to support the browser extension and deep system related APIs like keeping the app running efficiently in the background. For more than 8 months we were in discussion with the Microsoft to provide APIs to connect UWP app with Win32 apps (Firefox, Chrome) and extensions in them. Even there was no API to keep the connection between UWP app with the Edge browser (UWP) live for more than 30 seconds. So due to all these issues we had to bring our Win32 app to Store using the Bridged architecture and that alone was a huge task; just to support extensions for our beloved users. Now being a separate app, the in-app purchases of UWP are not restorable in Bridged, otherwise, we would have definitely done it.

I appreciate your detailed explanation of API issues and the reasoning behind bringing the bridged Win32 version to the store. I fully understand and see your point, but I'd also like to get your opinion on the "lifetime license" issue. You guys are pretty mum on this topic and all that's been said is something along the line "it's a different platform, so you have yo pay again". Give us one good reason why we should keep investing in a company with a broken value proposition?

On 12/30/2018 at 12:00 AM, Vinod Kumar said:

Hi @frustrateduser,

Even though past UWP version and current version are on same store, they are completely different products. There is no way to restore in-apps of one product to another. Similarly, iOS and Mac apps are different products. So, we are limited here by technology and restrictions of respective app stores. Apple has clearly defined this in their documentation

Historically, We never charged for UWP desktop and mobile version separately because both were same product. We never charged for Chromebook separately because it is same product as  Android app.

The only possible way for us to migrate in-app purchases across platforms/products is keep a central server where you will need sign-up  and register your in-app receipts. Some of you might like this thought but what people loves about Enpass is anonymity.

Thanks.

 

 

 

Sorry, but this is utter BS. Blaming Microsoft for being "limited by technology and restrictions" is a pretty bad excuse for screwing over your valued customers, who have paid for the now worthless lifetime license. YOU chose to create a new product, not Microsoft. You could have easily kept the app on the UWP platform and update 5.x to 6.x without making your customers pay again. But no, YOU chose to create version 6.0 with a different underlying platform, so of course it's considered a new/different product. Regardless, you could have worked out something to let users upgrade for free, but again YOU chose this path deliberately in order to create a new stream of revenue. I'd be totally fine paying for an upgrade hadn't you advertised and sold the previous version with a "lifetime license". The current situation is simply NOT ACCEPTABLE and should be considered SCAM.