Describes the thought process and concepts needed to create compelling and successful "geoweb" applications. Presented at the 2009 ESRI Developer Summit in Palm Springs, CA

1. notes
from the
field

2. most
of

3. are
technologists

4. we

5. we are
comfortable
with
complexity

6. how
does this
impact
our projects

7. February 2005

8. Techical:
Google Maps is released
Jesse

10. So what?

11. web 2.0

13. expectations
changed

14. forever.

15. we
(technologists)

16. what
box?

18. “data”

19. “interface”

20. “tools”

21. “tasks”

22. we
must
throw out…

24. simple tools
answering
complex questions

25. the lesson of
February 2005

26. where
to
start?

27. GeoWeb

28. address
spatial
business
problems
in a
browser

29. publish
&consume
services

30. but…

31. to be
successful…

32. we
must
understand…

33. trumps
features
usability

35. we
must
master…

36. Atom
WFS
.NETXHTML
CSS
Ajax
TDD
Javascript
RSS JSON
REST XML
GeoRSS
WMS

37. more
to learn

38. Todays Lesson Plan
Same tools Javascript
1. Object Oriented
2. Ajax: GETting and POSTing
Same workflows
3. Intro to JQuery and Dojo
4. Designing RESTful services
Same terminology
5. JSON and JSONP
6. CSS and browser tweaks
Worse performance
7. Silverlight & Flex

39. more
tools

41. we
must
understand…

42. what
users
want

43. users
want

47. how
do we
tackle
this?

48. design
ideas

49. examples
please!

50. 1
Road Project Management
Internal workflow application
SAP integration
OpenLayers + WMS + Dojo
ArcGIS Server 9.2

51. 2
Emergency Response
workflow application
multi-service “mash-up”
ESRI JS API + Dojo
ArcGIS Server 9.3 REST

52. 3
avian influenza tracking system
public facing
focused search tools
virtual earth + dojo
ArcGIS Server 9.2 + Custom Tile Server

53. interface
design

54. fewer
layers

55. Cram desktop into
A browser

56. Screen shot of CDOT

58. provide
feedback!

60. what
should
I do?

63. handle
the
“null-case”

66. make it
fast!

73. SAP Get Project List

76. hold their
hand

83. hide the
details
language
matters

84. Locate structures
near my project.

85. really
means…

87. generic
tool
could
work…

88. for
technologists

91. reassure
the user.

92. validate
as soon as
possible

93. SAP Ref Selection

96. pre-validate
whenever
possible

99. protect
users from
themselves

106. whew!

107. system
design

108. project
process

109. low
value

110. just-enough
design

111. map the
workflow

113. iterate
on
paper

114. • Create wireframes

117. choose
a map
canvas

118. keep it
simple

125. define
services

126. REST API

127. custom
services

129. not
available

130. possible
but not
optimal

131. “chatty”

132. faster

133. details
please!

135. 1
use the
SOAP API

136. ArcGIS Server
Web Server
ASP.NET MVC App
SOAP
SOC Process
AGS SOAP API
Controller
IIS
JSON

137. 2
COM utilities
&
server object
extensions

138. IIS
ASP.NET MVC App
Controller
JSON
Web Server
SOAP
Web Service
ADF Connection
COM
Utility
SOC Process
ArcGIS Server

139. can we
code now?

141. start
coding!

142. match
the
model

143. MARC SCREENS

149. release
early

150. release
often

151. listen
feedback

153. Summary:

154. expectations: changed

155. kung-fu: needed

156. design: workflow

157. focus: usability

158. performance: critical

159. details: hidden

160. Dave Bouwman
dbouwman@dtsagile.com
http://blog.davebouwman.net
http://twitter.com/dbouwman