Quote:
Originally Posted by samcohen
This mistake was my fault. I knew that it wiped my own library on a test flight and after mentioning it to the team we simply could never get it fixed. I didn’t choose to release this update yet but my development team decided to push it without asking me if I thought it was ready. Overall still my fault because I should have made it clear that we were not ready even though they seemed to think so.
My heart sank reading how upset people are about losing their books. I should have realized how important this was. I keep such a small library it didn’t matter to me when I lost the books I simply redownloaded them.
The subscription model is sort of a negligible price and is only going to be $.99 a month which is less than a can of soda from a vending machine. I think this is very reasonable and most will end up joining us.
We are doing our best to right our wrongs. We cannot currently roll back to the old version because the old version is from Xcode 9 so apple has rejected it.
Let me know if there is anything we can do to make things right.
|
As I developer and have experienced the "Oh, Crap" moment when something escapes into production by mistake, I tend to be fairly forgiving. As I said, CC for iOS is actually a lot faster, so it didn't take quite as long as I feared to reload everything.
My personal take is just learn from the mistake.
I would also say a bit of communication would be a good idea. Put out something about why you are going to a subscription model and what your vision of where CC is going. Do you expect to bring the iOS versions of CC up to the functionality of the Android version? What changes do you plan to do?
I totally understand the need to refactor the code to bring it up to date with the current release of iOS and swift. Perhaps a lot of non programmers don't understand what they get out of it, it's something you really have to do in order to move forward.
My guess is that some people will resist the subscription model and you will never be able to convince them. Just warn them when you plan to implement subscriptions so they can stop updating their app at that point.