my disney experience app needs to run faster

[Gomer]

I believe most of the Disney site and app issues are related to backend data lookups, and nothing to do with the actual front end guest facing site. Either way though, it still impacts the usability greatly.

Understood. In a way that makes the problem more complicated, but the solution more readily apparent. The company I work for had a similar problem with our website. It was bogged down by years of customer specific data and ancient back end systems. So, we scratched our in house version and paid good money to poach someone who had worked magic on some websites for some of the biggest online retailers in the world. They redesigned everything form the ground up. Now our site flies.

Problem is its expensive. Disney may not have a choice though. It was one thing when I had to stare down Tinkerbelle for 5 minutes while making hotel reservations. But, when you are dealing with the high demand that FP+ is going to put on the system, you have to cough up the cash for the back end systems to support it.

 

[flynnibus]

It's not the apps per se, it's all the database transactions and lookups they have to do on the other end. It is sluggish.

I doubt it... the great thing thing about wait times is they are the same for everyone.. which means you don't need to keep looking up the same data for every user request. You generate the latest times and make that available in memory for fast recall.. and you update those times on your own schedule, not when users ask for it. Pulling up things like ADR is customized... but things like maps, wait times, schedules, etc.. those are all uniform so they should be cached and readily available. Then the challenge becomes the content delivery being up to snuff to answer all the requests.

 

[stevehousse]

Been here all week and have not had any problems with the app or wifi...

 

[DeanFinder2.0]

Ran perfectly fine on my Virgin Mobile LG Optimus (terrible service). Only thing that sucks for me is the resort wifi

 

[Lord_Vader]

The app appears to run native HTML5 with a lot of backend lookups that create the slow responses for the most part. Disney has to reduce the latency between the devices, web servers and database servers to speed things up, all of which require a very high amount of bandwidth, responsive servers and low latency from the end-user to the web server.

Individual phones may impact rendering especially when trying to pull maps or high memory required portions but the general reservations and FP+ data is going to be slow until they add more bandwidth, move the servers closer to WDW and increase server capacity.