This document discusses mobile mashups, which combine multiple web services or data sources into a single application on a mobile device. It describes how mashups can combine different types of data or services for consumers, businesses, or to display similar data together. Common components of mashups include APIs, data formats like XML and JSON, architectures like client-based or server-based, and interfaces like native mobile apps or web apps. Examples of mobile mashups are provided, including ones for music, maps, and social networks. The document argues that mobile mashups will become more important as mobile devices surpass PCs as the primary internet access point.

1. Mobile Mashups
Cristobal Viedma

2. Mobile Internet

3. "Within 5 years mobile devices will become
the number one gate to access the Internet"
Morgan Stanley

4. Web Mashups

5. Long tail theory

6. Tools

7. "Too complicated for casual users, not
powerful enough for professionals"
Random commentator
at Techcrunch.com

8. What is a Mashup?

10. Mashed potatoes
Inspired by Monzy,
http://webremix.org

11. Music Mashup
Inspired by Monzy,
http://webremix.org

12. Web Mashup
Inspired by Monzy,
http://webremix.org

13. Mashup
Ingredients Tools Idea
Mashup
Inspired by Monzy,
http://webremix.org

14. Components of a Mashup

15. Chicago crime

17. Chicago crime (with CS glasses)

18. Mashups' components

19. Types

20. Types of Mashups
Data
Consumer
Business

21. Data Mashups
Combine many sources
of similar types into a
single representation

22. Data Mashups

23. Consumer Mashups
Combine many
sources of different
types into a visual
representation

24. Consumer Mashups

25. Business Mashups
Similar to consumer
with the aim to solve a
business problem

26. Business Mashups

27. Mashups' components

28. Service Providers

29. APIs

30. Open VS Proprietary
Akismet.com API

31. Terms of Service
"4(e): You will not, without our express prior written
approval, use any Product Advertising Content on or in
connection with any site or application designed or
intended for use with a mobile phone or other
handheld device."
Amazon product advertising API

32. Private VS Public Data
private e-
mails, pictures, etc
Share the password?

33. OAuth
Many luxury cars come with a valet key. It is a special
key you give the parking attendant and unlike your
regular key, will only allow the car to be driven a short
distance while blocking access to the trunk and the on-
board cell phone. Regardless of the restrictions the
valet key imposes, the idea is very clever. You give
someone limited access to your car with a special
key, while using another key to unlock everything else.
http://hueniverse.com/oauth/guide/intro/

34. OAuth

35. Some APIs
Web scraping 2900+ Apis

36. Class work
Make groups of 2-3 persons
What novel Mobile Mashups can you
think of?
Which Web Services could you use?
How will these Mashups be used and in
which context?

37. Mashups' components

38. Protocols

39. Protocols

40. REST
REpresentational State Transfer
On top of HTTP
Based on Resources
Basic methods: CRUD
Stateless

41. REST

42. REST

43. Mashups' components

44. Data formats

45. Many of them...
TXT TeXT
CSV Comma Separated Value
XML eXtensible Mark-up Language
RSS Really Simple Syndication
GeoRSS Geographical RSS
ATOM Atom Syndication Format
KML Keyhole Markup Language
HTML HyperText Markup Language
JSON Javascript Object Notation
YAML Recursive acronym for "YAML Ain't Markup
Language"

46. XML

47. XML overhead
M. Tian, T. Voigt, T. Naumowicz, H. Ritter, and J. Schiller, "Performance considerations for
mobile web services," Elsevier Computer Communications Journal, vol. 27, pp. 1097-1105, 2003.

48. JSON
10x faster parser
Smaller messages
Maps into JS objects
Extra: JSONP!

49. Mashups' components

50. Architectures

51. Architectures
Server based
Client based
Mobile

52. Server based

53. Client based

54. Comparison

55. Mobile

56. Mashups' components

57. Mobile Interface

58. Native VS Web
Native Mashups Web Mashups
Immersive user experience Easy and cheap to create and maintain
Developers can use known
Access to OS and all the hardware
technologies, tools and techniques
Easier to discover, centralized App Easy to publish: There is no need to
stores install any software
No need to update the software: cloud
Easier to scale up
based
Data more confidential when remains Apps stores review processes no
on the phone needed
Faster and offline mode support

59. Web tools

60. Native Web Apps

61. Summary

62. Reference framework

63. Examples

64. Telar

65. Telar Architecture 1

66. Telar Architecture 2

67. Telar Mashup ID

68. SoundSquare

69. SoundSquare

70. Antipodes

71. Antipodes

72. Thank you!