MobileMashup
From MashupCamp
Mobile Mashups
This session was led by CV Vick
Discuss this topic in an online threaded forum
notes from : Cindy H. Lu
- portable - device (resource)
- power
- modality
- bandiwdth
- mobile - context
- wireless
- offline
additional comments
- timing, distance & speed are issues
- the limitation of the lowest common denominator is an issue when it comes to designing apps for portable devices
- there are so many different types of portable devices
- choosing between thick and thin clients, or something inbetween
- will change the data that is best for the device
- customization of content by invidividual prodivders
- the device should be independant of the mashup
- problems with a mobile mashup
- limited to only Javascript?
- solution to the google maps; back end apps
- mashing up to your solution
- are the mobile and the mashup related
- related in an "out-of-the-box" way
- specific factorization of content for device
- not the same content slightly reformatted
- "menu" options are differnet
- not the same content slightly reformatted
- server can decide the content for the device
- you can classify portable devices into a few general categories
- currently there are limitations with US carrier data rate plans with mobile devicers
- cost to prohibitive for high bandwidth consumption
- adaptation with view
- location & context (what's around you)
- how do build a basic mobile mashup?
- things are different for the consumber vs. enterprise
- should apps work if it's offline
- more necessary for the enterprise
- you have to assume your connection will break
- the carriers prevent you for staying online for a certain amount of time
- even with carrier rules they will not let you be online
- offline apps can be cool
- technology usage: example you can still continue what you are working on if you become disconnected, and not loose work
- schwag is good :)


