Ibrussels For Stedenlink
Upcoming SlideShare
Loading in...5
×
 

Ibrussels For Stedenlink

on

  • 1,166 views

presentation given to the Dutch Stedenlink organisation on the i-Brussels project

presentation given to the Dutch Stedenlink organisation on the i-Brussels project

Statistics

Views

Total Views
1,166
Views on SlideShare
1,165
Embed Views
1

Actions

Likes
0
Downloads
7
Comments
0

1 Embed 1

http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Ibrussels For Stedenlink Ibrussels For Stedenlink Presentation Transcript

  • Mobile applications for your customers
  • Case study: Brussels community website • Customer – Brussels hoofdstedelijk gewest – CIBG (central IT department of Brussels) • Goals – Reinforce economy by creating a digital local community – Monetise services / platform (in the long term) • Must-have features – Works offline: permanent presence on the user’s phone – Automatic update of content through web services – Easy distribution (SMS “MyService” to 3236) – Website integration – Works on 80% of mobile phones www.citylive.be 2
  • Functionality: online city community Local Governe- IT Citizens Visitors shops ment companies www.citylive.be 3
  • Solution architecture: Citylive Community Services Platform • Functionality – Service creation – Service delivery – Service management • Technical – SOA architecture – SQL server 2000 DB – MS .NET 3.0 framework backend / ASP.NET frontend – Web services (JSON, REST, SOAP) through WCF – Session management and telco service integration through Microsoft Connected Services Framework 3.0 www.citylive.be 18
  • Solution hardwarde • Hosting:Kangaroot datacenter with Global Crossings, Tiscali and FreeBIX 1GB connections • Servers: HP cluster with SAN as virtual server host • Mobile phones: everything that runs Windows Mobile or Java J2ME www.citylive.be 19
  • Solution software: Hydra • Functionality: – Collection of enabling services out- of-the-box – Central & secure repository for profile and application data – Provides abstraction layer for applications & websites using simple API’s – Controlled environment handling privacy/authentication/authorizati on • AD based authentication of services (internal or external) • Impersonation for non- authenticated service consumers • Authorisation: own service or CSF www.citylive.be 20
  • Solution software: Application creation www.citylive.be 21
  • Solution software: Glowe explained http://www.youtube.com/watch?v=_XlHH0SJjv8 www.citylive.be 22
  • Solution software: Mobile Widget engines • Reference implementation on .NET Compact Framework • After validation, porting to J2ME, Javascript, Flash • Symbian: tried, but too fragmented / difficult process / weird architecture www.citylive.be 23
  • Challenges / lessons learned Things to do Things to avoid • Make mock-ups FIRST • Stay out-of-control – – – Mobile apps have no set expectation ? You can’t predict what will work Do extensive user testing ? – With mobile, the user is in control – You can’t manage his device. Forget it. – Give users tools so they can DIY. – Be prepared to change your concept • Avoid the bigger picture – Technical POC alone is not enough – Focus on a concrete function with an immediate value add for the user • Use the internet & its protocols – – A mobile does not live in your network ? VPN’s are a thing of the past ? – Trying to change work processes, integrate with business intelligence, cover a larger scope: it will all fail – Mobile is new: create demand first – SOAP is nice when critical, XML is easier – When it’s time for the bigger picture, – Use the universal firewall bypass port (80) current technology will be obsolete • Think Multi-platform • Translate the web to mobile – In some cases, mobile websites are OK – 1 platform only is not realistic ? – When you can: move up an abstraction layer or two (but web browser might be too thin) ? – But: don’t just convert existing web tools – Mobile has a different usage model then fixed (“browsing” is done on a desk) www.citylive.be 24