Abstract
Why do some native applications seem so fast while others do not? There is an old adage in auto racing. “Speed is money. How much do you want to spend?” It doesn’t take long for iPhone programmers to rub up against a similar problem, one perhaps expressed as, “Speed is time. How much do you have left to spend before release?” Given the limitations of processor power, RAM, and network bandwidth, not to mention battery drain, writing iPhone applications that display lots of data is hard. Clever caching, prefetching of data, and optimized drawing are the keys to removing the variable response times that make an app that’s consuming nonlocal or large amounts of data seem slow to the user.KeywordsInternet ConnectionCache DataSample CodeMain ThreadContent ViewThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
