developing for the geoweb: notes from the field dev summit 2009
DESCRIPTION
Describes the thought process and concepts needed to create compelling and successful "geoweb" applications. Presented at the 2009 ESRI Developer Summit in Palm Springs, CATRANSCRIPT
notesfrom the
field
mostof
aretechnologists
we
we arecomfortable
complexitywith
impactdoes this
our projects
how
February 2005
Techical:Google Maps is releasedJesse
So what?
web 2.0
expectationschanged
forever.
we(technologists)
whatbox?
“data”
“interface”
“tools”
“tasks”
we
throw out…must
simple tools
complex questionsanswering
February 2005the lesson of
wheretostart?
GeoWeb
address
businessin a
browser
problems
spatial
publish&
servicesconsume
but…
to besuccessful…
we
understand…must
featurestrumps
usability
we
master…must
XHTMLCSS Ajax
JavascriptRSS
XML
.NET
JSONREST
TDD
WMS
WFS
GeoRSS
Atom
moreto learn
Same toolsSame workflowsSame terminologyWorse performance
Todays Lesson Plan
1. Object Oriented Javascript2. Ajax: GETting and POSTing3. Intro to JQuery and Dojo4. Designing RESTful services5. JSON and JSONP6. CSS and browser tweaks7. Silverlight & Flex
moretools
we
understand…must
whatuserswant
userswant
howdo we
tacklethis?
designideas
please!examples
ArcGIS Server 9.2
Internal workflow application
SAP integration
Road Project Management
OpenLayers + WMS + Dojo
1
ArcGIS Server 9.3 REST
workflow application
multi-service “mash-up”
Emergency Response
ESRI JS API + Dojo
2
ArcGIS Server 9.2 + Custom Tile Server
public facing
focused search tools
avian influenza tracking system
virtual earth + dojo
3
interfacedesign
fewerlayers
Cram desktop intoA browser
Screen shot of CDOT
providefeedback!
whatshould
I do?
handle
“null-case”the
make itfast!
SAP Get Project List
hold theirhand
hide thedetails
languagematters
Locate structures near my project.
reallymeans…
generic tool could
work…
fortechnologists
reassurethe user.
validate
possibleas soon as
SAP Ref Selection
pre-validate
possiblewhenever
protectusers fromthemselves
whew!
systemdesign
projectprocess
lowvalue
just-enoughdesign
map theworkflow
iterate
paperon
• Create wireframes
choose
canvasa map
keep itsimple
defineservices
REST API
customservices
notavailable
possible
optimalbut not
“chatty”
faster
detailsplease!
use theSOAP API 1
Web Server ArcGIS Server
AG
S SO
AP
AP
I SOC Process
ASP
.NET
MV
C A
pp
IIS
Co
ntr
olle
r
SOAP
JSON
COM utilities& 2
server objectextensions
Web Server ArcGIS Server
Web
Ser
vice
AD
F C
on
nec
tio
n SOC Process
COMUtility
ASP
.NET
MV
C A
pp
IIS
Co
ntr
olle
r
SOAP
JSON
can wecode now?
startcoding!
match
modelthe
MARC SCREENS
releaseearly
releaseoften
listenfeedback
Summary:
expectations: changed
kung-fu: needed
design: workflow
focus: usability
performance: critical
details: hidden
