![Incorporating Web Services in Mobile Applications ,[object Object],[object Object],[object Object]](https://image.slidesharecdn.com/web2sfwebservicesmobilepres-090825162838-phpapp02/85/incorporating-web-services-in-mobile-applications-web-20-san-fran-2009-1-320.jpg)
![Disclaimer ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (18)
Destacado
Destacado (13)
Similar a Incorporating Web Services in Mobile Apps
Similar a Incorporating Web Services in Mobile Apps (20)
Último
Último (20)
Incorporating Web Services in Mobile Apps
- 31. Proxy Landscape Web Service Web Service Proxy Server
- 32. Designing your WS/API Destiny
Notas del editor
- Abstract Most of the APIs available to developers today have been coded for robust web server integration with little thought of incorporation into light weight mobile applications. This talk will look at the pitfalls of using these APIs directly and methods of incorporating APIs, such as Amazon, eBay, Google and other API sets into mobile and lightweight applications, while maintaining a quality user experience. First we will review the challenges of incorporating these APIs including; * Retrieval of large data sets * Multiple round trip communications * Security issues of calls * Display of information For each of these challenges we will show specific examples with sample functionality, API flows, and XML blocks. Some examples will include web user authentication techniques, media retrieval lists, and interface usability issues. Once we understand the challenges of incorporating various web APIs we will then look at techniques for handling APIs properly including caching methods, large data set handling, paging, filtering, just in time techniques, information on demand and speed testing. Throughout we will look at pseudo code, and detailed examples of real life examples. With the proper techniques mobile applications can take advantage of a wide array of third party and home grown APIs without degradation of performance, memory, and overall usability.
- The iPhone now accounts for 50 percent of mobile Web traffic from smartphones in the U.S., according to an AdMob Mobile Metrics report released this morning. Over the past six months, the iPhone has taken share from Blackberry and Windows Mobile. In August 2008, the iPhone made up only 10 percent of mobile Web traffic from smartphones. During the same time, Blackberry’s share has gone from 32 percent to 21 percent (with the Curve and the Pearl coming in stronger than the Storm), while Windows Mobile has taken an even bigger hit, declining from 30 percent to 13 percent. Palm is also down to 7 percent from 19 percent six months ago. The only other smartphone operating system that is showing gains in mobile Web usage is Android, which has captured a strong 5 percent share just three months after launch. And that is up from 3 percent in January. The gains shown by the iPhone and Android show what is possible when phones are built with fully capable browsers and support a rich array of Web apps. iPhone Makes Up 50 Percent of Smartphone Web Traffic In U.S., Android Already 5 Percent 31 Comments by Erick Schonfeld on March 24, 2009 – Techcrunch
- Focused on: Lessons learned from specific case studies Bet practices reinforcing ideas of web services in browser based apps Will cover the business side and then technology / code
- Is there a fee? What is the timeframe? What resources are required? Do you need to furnish equipment?
- One note here – even though the object based XML parser available with Cocoa runs in the iphone simulator it is not included as part of the iphone SDK and thus is unavailable on the iphone
- Caching of the processed results to serve same client or other clients – in memory or database Can help with reducing call volume to WS service providers Especially helpful with statistical information which changes on a periodic basis Must be careful with storage and refresh rules Banking and financial information perfect example of this FRED – US Federal Reserve Economic Data
- Remember you are the consumer of the api – play nice – the owner of the api can always turn your access off “ Starting later this week we’ll be limiting those on the whitelist to 20,000 requests per hour. Yes, you read that right: twenty THOUSAND requests per hour. According to our logs, this accounts for all but the very largest consumers of our API. This is essentially a preventative measure to ensure that no one API client, even a whitelisted account or IP, can consume an inordinate amount of our resoures.” 1/21/2009 We will see more of this – our duties as coders to play nicely with the api – use the right API