Mobile Technology Investigation

linencharmΚινητά – Ασύρματες Τεχνολογίες

10 Δεκ 2013 (πριν από 3 χρόνια και 8 μήνες)

65 εμφανίσεις


Page
1

of
22

Investigation Report





Mobile Technology

Investigation


Feb
/
Mar 2010





Revision History

Date

Revision

Description

Author

11th

March 2010

1.0

Draft

excluding Survey Analysis and Results

Paul Widenka









Page
2

of
22


Table of Contents

Summary

................................
................................
................................
................................
..........................

4

Introduction

................................
................................
................................
................................
....................

4

Approach

................................
................................
................................
................................
..............

4

Vision

................................
................................
................................
................................
....................

4

Investigation

................................
................................
................................
................................
.....................

5

Survey

................................
................................
................................
................................
............................

5

Objective

................................
................................
................................
................................
...............

5

Key Findings

................................
................................
................................
................................
.........

5

SMS Text Services

................................
................................
................................
................................
........

6

Ove
rview

................................
................................
................................
................................
...............

6

Objective

................................
................................
................................
................................
...............

6

Key Findings

................................
................................
................................
................................
.........

6

Clickatell
................................
................................
................................
................................
................................

6

eTXT (Telecom)

................................
................................
................................
................................
....................

7

Twitter

................................
................................
................................
................................
................................
...

7

Mobile Browsers and the Internet

................................
................................
................................
..................

8

Overview

................................
................................
................................
................................
...............

8

Objective

................................
................................
................................
................................
...............

8

Key Findings

................................
................................
................................
................................
.........

8

Mobile Browsers


Third Party

................................
................................
................................
.............................

8

Proxy Browsers

................................
................................
................................
................................
.....................

8

Mobile Browsers
-

Native

................................
................................
................................
................................
......

9

HTML5

................................
................................
................................
................................
................................
..

9

Silverlight

................................
................................
................................
................................
..............................

9

Mobile Development
-

Native Applications

................................
................................
................................
..

10

Overview

................................
................................
................................
................................
.............................

10

Objective
................................
................................
................................
................................
..............................

10

Key Findings

................................
................................
................................
................................
.......................

10

Apple iPhone

................................
................................
................................
................................
.......................

10

Windows Mobile

................................
................................
................................
................................
.................

11

Case Study

................................
................................
................................
................................
..................

12

MIT M
obile Web

................................
................................
................................
................................
.

12

Solution Overview

................................
................................
................................
................................
...............

12

Features Overview

................................
................................
................................
................................
...............

12

Systems A
rchitecture

................................
................................
................................
................................
...........

12

System configuration

................................
................................
................................
................................
...........

13

Additional Information

................................
................................
................................
................................
........

13

Waikato Implementation

................................
................................
................................
.....................

13

Initial Development

................................
................................
................................
................................
.............

13

Resourcing and schedule

................................
................................
................................
................................
.....

13

Current State

................................
................................
................................
................................
........................

14

Future State

................................
................................
................................
................................
..........................

14

Analysis

................................
................................
................................
................................
..........................

15

Option
s
................................
................................
................................
................................
.........................

15

Considerations

................................
................................
................................
................................
.............

15

Proposal

................................
................................
................................
................................
.......................

16

Implement an SMS Text Service
.

................................
................................
................................
........................

17

Catch up and leverage off existing MIT framework.

................................
................................
...........................

17

Re
-
Architect existing services.

................................
................................
................................
............................

17

Develop all new components for browser capability, not hardware category

................................
.....................

18

Provide the best user experience.

................................
................................
................................
.........................

18

Note
-

Native Applications

................................
................................
................................
................................
..

18

Page
3

of
22

Appendix A


Survey and Results

................................
................................
................................
...............

19

Survey

................................
................................
................................
................................
................

19

Appendix B


Outputs, References and Resources

................................
................................
..................

22

SharePoint Wiki

................................
................................
................................
................................
..

22

TFS Source Control

................................
................................
................................
............................

22

SharePoint Document Site

................................
................................
................................
.................

22

TFS Work Items
................................
................................
................................
................................
..

22

Waikato References

................................
................................
................................
...........................

22

MIT References

................................
................................
................................
................................
..

22



Page
4

of
22


Summary

Introduction

A
n
investigation
was requested

by the

ICT Director
into

the
provisioning of Mobile Phone Services
for Students at the
Univers
ity of
Canterbury.


Approach

-

Conduct a
Survey of Students
to gauge
e
xpectations

and
perceived
value of
Key
ICT
Services along with preferred Delivery options to their current
/
future Mobile Devices.

-

Investiga
te SMS Texting,
Smart

P
hone Development
, Mobile
B
rowser

and
Web Site
Development

options

and how the University can utilise these.

-

Investigate the Open Source
Mobile Web
Product provided by MIT
along with its

recent

implementation at the University of Waikato.

-

Conduct Brainstorming
Sessions.

-

Analyse
and
propose options discovered along with considerations
with
other ICTS
initiatives.


Vision

A student receives an SMS Text Announcement regarding a seminar
that is being presented

by a
visiting lecturer
which is
important

to the Students field of research. U
nfortunately the Student is
un
able to attend. The
following day

the Student
is notified
that he can
visit m.canterbury.ac.nz
to

watch a video of the lecture on UCTV
. He does this

via his mobile phone
in

a period

between his
regular lecture
s, enabling
him t
o join in with the discussion with his peers

his next

lecture
.


The Proposal outlined in this investigation
is aimed at providing

a platform
that can
enable Students
and
the University of Canterbury to
realise this vision for Mobile Devices.

Page
5

of
22

Investigation

Survey

Objective

An important
component

of this investigation was to
compose

and conduct
a
Survey
determining

Students
expect
ations

for Mobile Devices
in

a world class learning environment.

Questions were
constructed

to
determine
:




What devices and
devic
e
capabilities are Students currently using?




What are the priority mobile services our Students want from the University?



What
are Student
s

Mobile
Device
aspirations whilst studying at the University
?



What would students preferred delivery options be for
these services?


A copy of the Survey questions and analysis

for this investigation can be
found

in Appendix A

Key Findings

The results of this survey have been used to prioritise the services and to highlight the preferred
delivery
mechanism
. These result
s can be considered in conjunction with the Universities initiatives
of providing services via
all

Interface Device
s

and
User Interfaces
.


Note
Survey Results and Analysis to be completed

Facts and Figures are to be
confirm and will be implemented and rele
vant updates made

throughout
this document
.
This is expected to be completed for the end of March


SMS Services Ranking






Web Services Ranking






Phone Features Ranking






Application
s Ranking





To be completed



(Types of Phones, Brow
ser Usage, Preferred Delivery, Expectations)

Slice 1
Slice 2
Slice 3
Slice 4

Page
6

of
22

SMS Text

Services

Overview

Note Survey to be completed


Facts and Figures to be included

SMS Texts are
valued highly

and
still
a
preferred delivery option for pushed
data and ale
rts
.

Objective

Th
is

investigation looked at various options for the Push and Pull (SMS Request) of data via SMS.
A
Selectio
n

of utilities and Services were

looked into including some prototyping and trialling
.
Details of the key findings are summarised be
low and further
information is detailed in

Appendix
B.

Key Findings

Clickatell



A

leading
SMS Service
provider specializing in bulk messaging services and SMS
gateway connectivity.



Provide
s

a free API which enables developers to send SMS Messages using its
gateway

with

various con
nectivity options.



Features

Include:

Delivery Acknowledgment

Delivery delay

Coverage Query

Stop/Delete Message

Query balance

Query Message Status

Get Message Charge

Batch Sending


SSL Encryption

Two
-
Way Messaging



Integrates with
Virto
’s Web Part for sending SharePoint Alerts via SMS



Cost
s

Uses

credit based
accounting

for sending messages. 1 credit will generally = 1
message
, however,
t
his is dependent on the network operators in

the region
.


Country ⁄ Network

Outbound Messages

(text SMS)

Inbound Messages

(text SMS)

Credit Cost

NZD Cost

Credit Cost

NZD Cost

New Zealand

Telecom New Zealand

1

0.066

0.33

0.022

Telstra New Zealand

0.8

0.053

0.33

0.022

Two Degrees Mobile Limited

0.8

0.053

X

X

Vodafone (BellSouth)

0.8

0.053

0.33

0.022


Cost

based o
n
a

volume
purchase
of

250,000


499,000

credits (March 2010)


Page
7

of
22

eTXT

(
Telecom
)

eTXT
provides limited functionality and service in comparison to Clickatell. It
provides a basic

solution to send a s
ingle message to a number of users.




Replies can be sent back to the PC or mobile which sent the message.



Messages can be sent

to groups or individuals from Outlook, a web browser, or from
a

mobile.


Costs



Set up fee of $99



Monthl
y Access fee of $10
per account



10c per mess
age sent to each Telecom Mobile



17c per message sent to other New Zealand network handsets

Twitter

Twitter is an extremely popular social network
ing website (75,000,000 Registered Users

-

March
2010) which was design with a 140
character limit

so tweets
can

be sent as mobile text messages.
The Twitter service provides a REST API which allows
developers full
interaction with the site
.




During th
e

investigation the Twitter Service

was utilised
to forward Tweets (140 Cha
r Text)
to a

Users mobile phone using the REST API
.



Direct Message Tweets
were sent
using the API
to the user following

a particular
user
/group
.



A proof of concept prototype showed that t
his service could be utilised so Twitter users
could follow University Groups th
at
send out user specific Direct Messages to each of its
followers. The followers can
individually
configure their
profiles

to receive SMS text and/or
Email
s of the Tweets.


Costs

This service
was free once the phone was registered and the user profile was

configured.


Page
8

of
22

Mobile Browsers and the Internet

Overview

Mobile phone browsers vary in capability and
are
designed with
optimis
ation
to display Web
content effectively on small screens
.
This is coupled with

the
history of the
fragmentation in the
mobile de
vice
-
channel
, the
low memory
of mobile devices
and low
-
bandwidth
.


The University of Canterbury does not currently have a

wireless portal
e.g
. m.canterbury.ac.nz

where mobile users
are
directed

to
a Portal of
Services that render to the potential of the de
vice
,

and
more recently, to
more intelligent
browsers that Users install on their devices

instead of the native
browser
.


Common

Solutions to providing a
wireless portal

include
:



Develop
ing/Copying
existing services or web content to a site utilising a
pri
mitive/low level form
in the hope

that it renders on all devices



Limiting support to a subset of devices



Us
ing

WURFL to convert content to the appropriate
mark
-
up

for the device


T
he

need
for users to access

existing web sites, so that
they have
full funct
ionality o
f their

favourite
site
s has, more recently been
addressed by
some Mobile Browsers that are now competing in a
market that is becoming comparable to the
desktop/laptop
Web Browser.

Objective

Mobile browsers are advancing rapidly along with the ca
pabilities Smart Phone devices. Potentially
this reduces the investment need required to render content for devices as users upgrade devices
and/or install the latest Mobile Browsers.


Investigate the

most
popular browsers, their capabilities, recent deve
lopments and the options t
hey
provide

and highlight the
capabilities
direction that
they are taking.

Key Findings

Mobile Browsers


Third Party


Opera Mobile



Available for Windows, Nokia Symbian



Touch screen

Support



I
ntelligently reformats Web pages

Proxy
Browsers



Run on less capable phones and offload rendering to a proxy server



Present Web sites as on a desktop browser



Popular examples are Opera Mini and Skyfire



May not provide end to end security


Opera Mini



Web pages are compressed by up to 90% of their

original size making browsing faster



Available for Android, Windows, Blackberry, Psion, Nokia Symbian and soon available on
the iPhone.



Touch capability

Page
9

of
22


Skyfire



Available for Windows, Nokia Symbian



Renders

Flash 10, Ajax and Silverlight



Touch capability

Mobile Browsers
-

Native


Web
K
it

Many of the native browsers are based on the Web
K
it layout
engine. These include
:



Google
Android



Palm
WebOS



Apple
Safari



Nokia S40 and S60


WebKit is an Open
-
Source rendering engine

with development included from
Apple
,
No
kia,
Google, RIM and Palm. Due to the nature of this engine there is a set of standard capabilities
ava
ilable throughout these devices

HTML5

HTML 5 provides a

range of key capabilities available to mobile devices
. The

native iPhone

and
iPad
, Google Android
, Nokia, and Palm browser
s

are based on the
Web
K
it

browser engine which is
coupled with HTML 5 support. In addition to this, Opera is a leading developer of HTML 5
.

Features of
HTML5 include

offline support
(
AppCache and
Database APIs
)

which
presents a

platform
for building sophisticated mobile Web applications

based on standards.

On the whole this represents a large percentage of the Smartphone market.

Microsoft

has
hinted at
its
future
support for HTML 5 in Internet Expl
orer 9

and
further
announcements are expected at
Mix10


Silverlight

Silverlight’s target is to provide the ability to deploy the same content on multiple platforms
.
Silverlight has the ability to run full web applications. Recent developments and announce
ments
include Silverlight capabilities such as:



V
ideo streaming

on the iPhone



Suppor
t

on Windows Mobile and Nokia S60 Devices



Support on Skyfire


Silverlight already has a range

of capabilities

across the main desktop
browsers
and platforms, and
indication
s are this is expanding and opening up into the competition within the Mobile Device and
Browser market.


Page
10

of
22

Mobile D
evelopment
-

Native Applications

Overview

There is a lot of
activity

and
big
business around mo
bile native applications

across
S
mart

P
hones
a
nd

the
ir
respective

app
lication

stores
.

These applications give users and developers the potential to
leverage off the full capabilities of the device, including
the
features such as GPS and the Touch
screen.

The benefits of this are that the application w
ill be presented and function as designed, on
the flip side they will be device specific.

Objecti
ve

Investigate and trail some of the environments required to develop popular native applications

Key Findings

Apple iPhone

Development




Language: Objective

C2



Environment: X
C
ode or Coda



Requirements: Mac



Develop on

a iPhone Simulator



Develop using an
MVC
pattern


Fo
r further details see Appendix B


Costs

These
assumptions
made
here is
for the
setup
cost
for an environment for a developer to develop

iPhone appli
cations

within the ICTS Solution Delivery
with
in its current operating

environment
.



SDK
-

Free


Mac running Mac OS X Leopard or later



(from $2000)


Developer Program $99 or Enterprise Program $299

which provide the following



Standard

Enterprise

Pre
-
release versions of iPhone SDK

o

o

GM versions of iPhone SDK


o

o

iPhone Dev
Centre

Resources


o

o

Testing on iPhone and iPod touch

o

o

Code
-
level technical support

o

o

Apple Developer Forums Beta

o

o

App Store

o


Ad Hoc Distribution


o

o

In
-
hous
e Distribution


o


Along with this is the potential cost in training although there ar
e some good resources available.
The
investigation included a look at
the
potential learning curve to a .NET C# developer with
understanding of MVC
and would rate this a
s an Easy Learning Experience


There could also be a requirement for a physical iPhone device for testing purposes

Page
11

of
22

Windows Mobile


Development




Language:
C#, VB.Net



Environment:
Visual Studio



Develop on

a
Device Emulator



Develop using
.NET Compact Framewor
k 2.0 SP 1


Fo
r further details see Appendix B


Costs

These assumptions made here is for the setup cost for an environment for a developer to develop
Windows Mobile applications within the ICTS Solution Delivery within its current operating
environment.




.
NET Compact Framework 2.0 SP 1
-

Free



PC

already available



Visual Studio IDE

available


The investigation included the setup of a Windows Mobile development environment along with
the development of a simple windows mobile application. Due to the nature a
nd experience of .NET
this would be rated as an Easy Transition with no training requirements.


At time of writing Microsoft has announced its Windows Mobile 7 platform along with its
development using the Silverlight Platform. This looks like a significan
t change in direction for
Microsoft in the mobile phone market.



Page
12

of
22

Case
Study

MIT Mobile
Web

Solution Overview



MIT have created
the
Web Mobile Platform

an Open Source Project



Designed to meet physical and technical constraints across the
a

spectrum of mobi
le devices



Uses device segmentation to
not

provide lowest common denominator
user
experience



3 Segments

are

targeted for
:

o

Feature Phones

o

Smart Phones

o

IPhone/IPod touch



Designed to meet physical and technical constraints across the whole spectrum of mobile
devices



Open Source Technology using PHP, MySQL, SOAP, RSS,

XHTML and CSS



Uses WURFL to determine device capabilities



Uses a HTML template for each of the 3 segments, each with its own CSS style sheet and
images


Features Overview



People Directory



3Down


S
tatus
of
s
ervices such as internet, email and telephone.



Stellar


Course Details and Announcements



Campus Maps



Shuttle Schedules (Loaded from bus schedule data file)



Emergency Info



Student Careers


Systems Architecture


Source
MIT


Building the
Mobile
Web


Page
13

of
22

System configuration

Hardware (Virtual Server):

CPU: Intel Xeon 3GHz

Memory allocation: 2 GB

Storage: 15 GB

VMWare

Software:


Operating system: Red Hat Enterprise Linux 4

Web server: Apache 2.0.52

PHP 5.2.5, MySQL 5.0.18, Python 2.4.4

Source MIT


Bui
lding the Mobile Web


Additional Information




MIT have
now taken

the approach of developing a Native version of the Application for the
iPhone

http://web.mit.edu/newsoffice/2010/iphon
e
-
app
-
launch.html

(
February 8, 2010
)




Preview

the site
on a desktop browse
r
http://m.mit.edu/about/preview.html



Waikato Implementation


Initial

Development



Reviewed

various versions of the

MIT

framewor
k and
selected the

one that was
a
closest
match
to the infrastructure at Waikato
University


Picked version 2 of the framework
customised by West Virginia



Deployed to a
dev/
test server and began

playing


with
and
reviewing code.



Reviewed Data Sources



Re
-
skinned the front end

and redirected URL’s



Picked the easiest services to migrate

and released an initial basic set of services
. (Excluded
Bus Timetable, Course Timetable and Course Information
)


The complexity and the time taken to implement each of the
services was dependant on the ability
to
:



Obtain
the data as through an XML Queries

or an RSS Feed



Whether the data sources for the services were the same e.g. both using
LDAP



Whether the traditional web site already had the services with feeds



Accessibili
ty to the appropriate service and
the
cooperation
of the

System Administrator
s


Re
sourcing

and schedule

The initial development

was not expected to go live so quickly. The
duration

was around
4
-
6

weeks
utilising:



Team of
Developer
s.
Approximately equ
ating
to 1 FTE

during this period



Open Source experience

including

PHP, MySQL, SOAP, RSS,

XHTML and CSS



2 Database Administrators on an ad
-
hoc basis



Various System Administrators and Server Support on an ad
-
hoc basis


Page
14

of
22

Current State

Have implemented
13 Services

i
ncluding
:



Bus Timetable

This was d
ifficult due to the Service Provider. Had to hard code, scrape web pages and
manipulate data for timetable information. This is easy if the Bus Service provider uses the
Google Transit API.



Campus Maps

This took the Lo
ngest. Although it was easier than it can be as the existing
site
maps were
true to scale
.



Phone Book
,

Easy as the traditional web already used a feed from LDAP




Emergency Info

and
Campus Events

Easy as the traditional web already had feeds



Computer Avail
ability

This has been the most popular and useful item
for

students


See
http://m.waikato.ac.nz/home/


Support



Robust and little additional support require
d



A feedback form is provided when errors occur

or
stude
nts can

provide details of
issues
such as pages

not rendering well



Developers keep an eye on the Open Source site for updates


Security



Cookies are saved to the mobile device after a login process. These are persisted for a period
of 3 hours. This was impl
emented by Waikato and is used only for the ‘Non Public’
information


Student Data



Feeds do not go direct to JadeSMS but use an Interface Database which is populated in a
similar manner as the UCInteface Database

Future State



Currently h
ave a list of requi
rements queued up
that are being implemented along with
other
business as usual operations
.



Page
15

of
22

Analysis

Note Survey Results and Analysis to be completed


The following proposal could be subject to
change.

Options


SMS Text Services



Do nothing.



Provide a B
asic Service
to deliver high level, non user specific
announcements
.



Provide a Push/Pull service that provides user specific messages and alerts that are user
configured and accounted for.



Provide a
service that uses a popular social network to provide ale
rts and details
.


Mobile
Web Portal



Do nothing. Allow Browser and Device Technology to catch up

and
the

University of
Canterbury
web
site and
web
applications to evolve
.



Implement MIT Mobile Web

services
where

available and
if

appropriate
.



Develop an initi
ative using standards that will provide a Mobile Web Portal environment

for
the Smartphone’s
of today and the future
.


Native Smart Apps



Do nothing.



Develop Lightweight front end user Applications connecting real time to University services
for the most p
opular mobile devices
, utilising individual device capabilities

and distribute
them via a Mobile Portal



Develop full native applications for the most popular mobile devices and distribute them via
App Stores and potentially generate revenue for the Univer
sity.


Considerations


SMS Text Services



SMS is still valued highly and is available on all mobile devices



SMS Push can reduce high usage periods and notify users in a timely manner



Clickatell provides a very competitive priced service with message traceab
ility and a fully
featured API which can be build upon.



eTXT
(Telecom) is relatively expensive in comparison to other services and provides a
limited set of functionality.



Twitter provides a cheap, user configurable service which could also establish a pre
sence for
the University on a popular social networking site. During the investigation this service was
not found to be 100% reliable due to service restrictions mainly due to the number of users
connected. This option could be considered for non
-
critical
services.


Mobile Devices

in general



Historically a wide range of devices and capabilities. However due to new browser
capabilities, standards and the demand for devices it is important

and possible
to look
f
orward

and provide applications
and services mor
e
strategically.



Many recent developments and announcements enable
decisions to make a sound mobile
strategy for the future.

Page
16

of
22



University of

Canterbury is playing catch up



Wi
-
Fi capabilities of Students mobile devices



Telephone Network Speeds, Services and C
harges


Mobile Web Portal



Tools, sites, and applications are
currently
fragmented.
A Mobile Web Portal

would provide
a one stop gateway.



Currently the University has n
o mobile presence or mobile home page
.



Development
would be

directed
towards browser capa
bilities meaning that the same
components
,

and the services they are built on,
are likely to be used for mobile device and
desktop browsers

and would use less of a code base meaning reduced ongoing support costs



SharePoint and UCLive
can

be utilised to use

Mobile Device Views and capabilities.



Potentially

Mobile Web applications

will take over Mobile native apps
with
capabilities of
new mobile
browser
s
, standards

such as HTML5 and
the
Silverlight

framework



There is no difference in how you build Silverlight

application
s across Web and mobile
devices

encouraging and enabling re
-
use
.



HTML5
and WebKit provide

standards and disconnected capabilities

which are available on
a majority of Smartphone’s and, by installing specific browsers all the major Smart Phones.



Connectivity requires higher resource usage (e.g. Network and battery)



The University provides a 2GB daily wireless quota to all students.



W
eb browser capabilities on Smartphone’s is robust and a lot of the mobile native apps
could be achieved as web appl
ications as well



More reliant on Wi
-
Fi capabilities of devices and Telephone Network Speeds, Services and
Charges



Native Smart Apps



There is a lot hype and popularity
currently
with native applications and app stores meaning
that there is demand for thes
e applications.



Based on the skill sets of developers it is relatively simple to develop and deploy
Smart
Apps for the most popular platforms and devices
.



Provides an opportunity to make revenue in
a similar

way as
WaikatoLink, the commercial
arm of the Un
iversity of Waikato.



There may be r
easons to develop multi
-
platform apps include client
-
specific needs, specific
platform feature requirements, User Experience such as Look and Feel, disconnection and
limitations of

network bandwidth or availability



Le
vera
ge off specific platform features to provide applications and devices for research
requirements.



Can utilise asynchronous background services to refresh and sync data on the local device to
provide improved performance and data availability for the user ex
perience.

Proposal


In making this proposal the author has
used the considerations
above and taken the following
approach
:


1)

Catch up with other Universities in establishing a Mobile Presence
.

2)

Leverage off
and support
the latest ICTS initiatives, the lates
t technologies available and
build for the future.

3)

Take the lead and present the University of Canterbury as a world class learning
environment.

Page
17

of
22


The

proposal is to take the

following
initiatives
:

Implement an SMS Text Service
.

Establish an SMS Text Servi
ce

which would be available and beneficial

to all Students and Staff
even with the most basic Mobile Device

by:



Build
ing

on top of the Clickatell
S
ervice to deliver SMS Text capability
.



Providing

Component
s
/
SharePoint
Web Part for User Sign up and Self man
agement of
alerts.



Investigating /Integrating

Alerts with SharePoint Alerts using
Virto SharePoint Alerts
Customizer Web Part



Integrating

with RAS (Resource Accounting System) for
a
llocations and
c
harging of
the
txt
services



Implement
ing

the Services as V
alued and Prioritised by Students



Added
Value



Reduce
the
load on ICT Services

through a timely

Push of data
.



Immediate alerts on significant and user defined events
.



Reminders and Notifications of deadlines reducing late submissions and late charges
.



Acc
ount Notifications and Balance Warnings reducing Service Desk calls and minimising
risk to students who are

reaching limits
.



Provides a service to all Students who have any type of mobile phone.


Catch up and leverage off existing
MIT
framework
.

Establish
a Wireless P
ortal

by implementing the
quick wins from the MIT Mobile Web and get a
mobile presence and portal in place

by:



Creat
ing

m.canterbury.ac.nz



Implement
ing

MIT Mobile Web



Implement
ing the quick win
Services
to
seed

a
mobile portal

for additional se
rvices as
prioritised from the Student Survey


Added
Value



Give the University of Canterbury Mobile Presence

and increase visibility and publicity.



Collate Student Tools into one location/portal from a f
ragmented
Web Site

which is
cumbersome on some mobile

browsers
.



Leverage

off an Open Source product which has had many hours invested
.



Open up options to utilise future initiatives of the Open Source product.


Re
-
Architect existing services.

Implement
new services
using a
Services
Oriented
Architecture
over
all these initiatives and
in line
and other
ICTS

initiatives
.

Develop and re
-
write
the

Services that
are
used

for

this and

for

future
initiatives

by
:



Writing
/Rewrit
ing/Reusing

‘traditional’
Web Services to WCF



Securing

with Certificate
s

and Single Sign
On
in
itiative
s



Decoupling

data access and business logic from data presentation

ensuring
a clean
separation between the data model and the user interface
(MVC and REST)


Added
Value

Page
18

of
22



Moves towards and
Enterprise Service

Oriented Architecture

and Security
Model



Future proof services that can be consumed
n
ative applications,
b
rowser
a
pplications,
SharePoint Web Parts, System Services or by
a
pplications
s
tudents
d
evelop



Consolidated code base across all solutions and business logic


Develop
all new components
for
browser capability, not hardware category

Give

the widest audience over multiple browsers

and devices
.
Create and
a
dd
n
ew
c
omponents for
the
W
ireless
Portal

by:



Writ
ing/Rewriting/Reusing

new
p
ortal
c
omponents segmented by
b
rowser
c
apability
.



Build
ing

UI co
mponents solely for
data presentation
.



Build
ing

UI components designed for SharePoint/Student Portal Web Parts so they can be
utilised via desktop
as well as

mobile devices.



Build
ing

components using WebKit and HTML5 standards
.


Added Value



Higher coverage

of devices from one set of code
.



Greater chance of re
-
use between Mobile Portal and Desktop Portal
.



Closes the gap of what can be expected and provided by a Native Application on a single
device and what can be provided on nearly all leading Smartphone’s.


Provide

the best user experience
.

Target the latest
b
rowsers and
s
tandards of today and the future. Develop components that will
present the University of Canterbury as a Leader

by:



Leverag
ing

off standards such as
WebKit and
HTML5
providing an

optimal u
ser experience
and capabilities of the
‘b
rowser
m
ajority
’.



Target
ing

browser capabilities and technologies such as Silverlight for optimal user
experience that users of
n
ative
a
pplications
expect and
utilise.


Added Value



Promote the visibility and capabil
ities of the University of Canterbury
.



Provide easy to use access to valuable resources

across any device.


Note
-

Native Application
s

The consideration for developing native applications for the most popular devices was not seen as
being of
significant

be
nefit to providing the
services
which would also be attainable
through a
Mobile Portal
. However, the ability to provide applications for research

purposes
,
including
disconnected
applications, applications utilising specific device capabilities and the pot
ential to sell
applications to a large market of users should
definitely
still be considered

on a case by case basis
.
If there is any potential in this area, this investigation has provided a level detail of development
environments
, options

and capabiliti
es.

In addition to this, by implementing the proposal as above,
the resulting
Service Orientated Architecture

could

be
used as a base

for the
initiative
to develop
Native Applications on top of these
services providing specific device capability

using
the

MVC
pattern
.

Page
19

of
22

Appendix A


Survey and Results

Survey
Results and Analysis
t
o be completed

Survey


(Draft also available here
http://www.surveymonkey.com/s/FXWLLZS
)


Page
20

of
22


Page
21

of
22


Page
22

of
22

Appendix
B



Outputs
, Reference
s and Resources

SharePoint Wiki


A Wiki was used during this investigation to capture details of communications, student survey,
brainstorming, research notes and references and details of Prototypes and Code Samples.

http://ucbsstfs/Sites/UCMobile/UC%20Mobile/Investigation%20Feb%202010.aspx

TFS
Source Control

The TFS Source Control folder “
Investigation Feb 2010
” includes:

-

A
Windows Mobile device application written
as proof of concept

-

A
Twitter application utilising the Twitter REST API which sends direct messages which
can be configured by users to provide SMS Text alerts

-

Video for Building iPhone Applications

-

MIT Mobile Web Source code

SharePoint Document

Site

-

MIT
Mobile Web Presentations

-

Survey and Drafts

TFS
Work Items

-

Investigation backlog items

Waikato

References

Acknowledgements

to Steve Leichtweis

Waikato University lets students’ fingers do the walking Mobile web environment lets students view info, maps
and
timetables from their mobile phones.
http://pcworld.co.nz/pcworld/pcw.nsf/feature/F706A061A2C1CD25CC2576A4007F36FE

iPhone Apps boom creates opportunities for Waik
atoLink
http://www.waikato.ac.nz/news/archive.shtml?article=985


Online network keeps students in check

http://tvnz.co.nz/technology
-
news/online
-
network
-
keeps
-
students
-
in
-
check
-
3327193


Mobile Software for Waikato Students
-

Stuff

ht
tp://www.stuff.co.nz/technology/digital
-
living/3209359/Mobile
-
software
-
for
-
Waikato
-
students


Waikato Mobile site About

http://m.waikato.ac.nz/about/

Waikato Link

http://www.waikato.ac.nz/news/archive.shtml?article=985

MIT

References

Acknowledgements to Andrew Yu

MIT Web Mobile Platform Download

http://sourceforge.net/projects/mitmobileweb/files/mit
-
mobile
-
web
-
2.0.0.tgz/download

MIT iPhone Native Application

http://itunes.apple.com/us/app/mit
-
mobile/id353590319

MIT Mobile Web Portal

http://m.mit.edu/about/

PHP on Windows 2008 and IIS 7

http://www.microsoft.com/windowsserver/compare/php
-
on
-
windows/