Forum | Appery.io

I personally struggled for two days trying to adapt and understand this new topology and even had it working. Now I wake up to find that the guts have been stripped out of my project. It was a COMPLETE rebuild of its predecessor using the new upgrade which we had no say over whether we got it or not.

Now I'm afraid to proceed, or should I say start over again. You are making enemies of your own customers.

Might I suggest that NEXT rollout be in the format of 'choice'. Give them two websites to choose from. Let them continue their current projects in the OLD format if they so choose. Or, if they want to be beta testers, allow them free access to the new site while your work the bugs out. Then, over time, as people complete their OLD projects, make the NEW technology website mandatory. At least it will allow more time to test in a live environment without effecting so many people.

This was so wrong. Damage like this, you simply cannot just apologize your way out of. That fixes nothing.

I suggest releasing a statement that reinforces your next plan of action. Something at will reassure everyone that this will never happen again.

I want to sing praises about appery.io and how great it is. But cannot as long as such things are occurring.

Hi Dave, I completely agree with you, as I stated in one of my previous post as a professional developer I can understand that Appery is in a difficult moment with this deploy/rollback affair, but as a customer paying their service I'm disappointed because we users are working as Appery's beta testers at the moment, but we are NOT Appery's beta-testers, we are customers. They should test their routines and procedures and not rely to us for it. Appery is an amazing platform, but please try to learn a lesson from this accident. I suggest to plan next major update with better and strong release procedure that inform customers in the right way. Testing things in a live environment IS mandatory before releasing any important update.

I agree with Dave and Enzo. I've been put in a position where the service I rave about and commit my client's interests to (Apperio.io) has not allowed me to move ahead on a critical project for days now. I've tried a bunch increasingly simplifying and clarifying forum posts on what should be an extremely easy issue for support - to no avail. I and my client continue to twist in the wind. I'm not in a position to stop client work for days on end to handle what should be a routine support issue last raised in the post =14328267#reply_14328267]https://getsatisfaction.com/apperyio/....

Hi Enzo... you are so right. As I said, two sites would be nice. One, our live 'working' site for continuing our projects, and one OPTIONAL site for beta testers until they get the bugs fixed.

And RobertJay, I too experience quite often what appears to be a language barrier beyond 'tech speak'. I post a question and get an answer that appears they never read my entire post or really ever understood my question. To me what I was asking was obvious. I would love to finish and publish my app. But can't keep a solid technology in front of me long enough to work my way through it.

Let's be diligent brothers in arms. That they will work out these issues and make this THE go to product for mobile device app creation.

Hi All,

We are so sorry about all these problems in your projects and all the inconvenience. We understand your disappointment. We really screwed up, and we are very sorry about this situation. We are doing everything possible to restore the files/data and keep you posted.

One more thing that it is definitely going to be considered beta testing for significant upgrades going forward.

Once again sorry about that.

Absolutely. And I truly do believe this update/rollback was the exception to the rule and continue to believe unequivocally in the service. But it's just so frustrating to have to grind to a halt on important client work on what I've got to believe is a trivial support issue.