Is the next wave of mash-ups rising with the advent of Android? The best known mash-ups are “Google maps”, which is everywhere now-a-days. However, it seems like these are all of olden days. A new dawn is breaking…The new types we will see in future are mobile mash-ups. However recent announcement of “Android” from Google will definitely lead to the raise in mash-ups on mobiles.
What are the main motives to mash-up services on mobile devices?
One motive is similar to the “Google Maps” API. The other motive is to extend all services to the mobiles domain, because mobile era is started. Instead of engineering/migrating every application into mobile domain, just build it once as a core ability, and use as services which mashes up with other APIs. The mash-ups created for mobiles can blend enterprise and Web data to meet the specific needs of a user. This is the area now the business is focusing on.
One motive is similar to the “Google Maps” API. The other motive is to extend all services to the mobiles domain, because mobile era is started. Instead of engineering/migrating every application into mobile domain, just build it once as a core ability, and use as services which mashes up with other APIs. The mash-ups created for mobiles can blend enterprise and Web data to meet the specific needs of a user. This is the area now the business is focusing on.
What can we expect from Mash-ups on mobiles?
The next phase of mobility for business will go definitely beyond e-mail. Online interactive business applications need enterprise level modules which minimizes the application data management and ensures reduced costs related to maintaining and updating your own data repositories which suit mobiles. Getting these unlimited data sources is based on standards, since all providers are based on same industry standards, these advancements will promote a deeper partnership between businesses and operators who offer these new types of services and mobile devices.
The next phase of mobility for business will go definitely beyond e-mail. Online interactive business applications need enterprise level modules which minimizes the application data management and ensures reduced costs related to maintaining and updating your own data repositories which suit mobiles. Getting these unlimited data sources is based on standards, since all providers are based on same industry standards, these advancements will promote a deeper partnership between businesses and operators who offer these new types of services and mobile devices.
What do you need to build a Mash-up for mobiles?
The first and foremost thing that we have to know is what kind of mashing we are trying to do. As per my knowledge we can try for the following mash-ups:
Front- end mash-up: building web front ends like dashboards using widgets/gadgets and little to no programming (iGoogle, PageFlakes)
Back-end mash-up: combining web-accessible data and services into more useful web services that can be called easily using a REST-full interface (Kapow, Yahoo pipes)
Integrated mash-up: building end-to-end applications that link widgets/gadgets to data and services.
Considering above points the core abilities that we have to build for mash-ups are:
· Register with each service provider
· Deal with service limitations and restrictions
· Learn the in's and out's of each data service
· Registering with mobile carriers.
· Pre-built components for customizing according to the mobile carriers. (end-user forms)
· Security(role) designer
· System orchestration designer
The first and foremost thing that we have to know is what kind of mashing we are trying to do. As per my knowledge we can try for the following mash-ups:
Front- end mash-up: building web front ends like dashboards using widgets/gadgets and little to no programming (iGoogle, PageFlakes)
Back-end mash-up: combining web-accessible data and services into more useful web services that can be called easily using a REST-full interface (Kapow, Yahoo pipes)
Integrated mash-up: building end-to-end applications that link widgets/gadgets to data and services.
Considering above points the core abilities that we have to build for mash-ups are:
· Register with each service provider
· Deal with service limitations and restrictions
· Learn the in's and out's of each data service
· Registering with mobile carriers.
· Pre-built components for customizing according to the mobile carriers. (end-user forms)
· Security(role) designer
· System orchestration designer
The steps are simple, but each one comes with its quirks.
We have so many tools (Kapow, Yahoo pipes) and platforms like JackBe, IBM or Serena to support above core activities, but unfortunately these are not reaching all the way down into unstructured content.
We have so many tools (Kapow, Yahoo pipes) and platforms like JackBe, IBM or Serena to support above core activities, but unfortunately these are not reaching all the way down into unstructured content.
So which method/product is right for the development?
Though this is a tough question, my answer is certainly not to use the existing tools. Certainly these tools/platforms provide a good jumpstart for a limited community of mash-up builders, but they may not reach all the audience/communities. My view point is to recombine a host of disparate architectural mash-up patterns to benefit as large audience/communities as possible.
Though this is a tough question, my answer is certainly not to use the existing tools. Certainly these tools/platforms provide a good jumpstart for a limited community of mash-up builders, but they may not reach all the audience/communities. My view point is to recombine a host of disparate architectural mash-up patterns to benefit as large audience/communities as possible.
0 comments:
Post a Comment