Post on 18-Dec-2014
description
Introduction
Ike EllisSenior Software Architect
Brownie DavisApplication Development Manager
Fish & Richardson, P.C.
History of iPads at the Firm
• Last Year – No real mobile development initiatives
• This Year – Five applications written, countless more coming in the pipeline
• 29% of our attorneys have iPads• 80% have iOS.
“How did that happen?”
Ways We Exploredto Write
• HTML5– HTML/JavaScript/MVC (PhoneGap)
• Native - Objective C/XCode• Native – MonoTouch
HTML5/Web
• 300 millisecond lag time on events• Good for replace to web application• Can reuse code on other platforms
Native - Objective C
• Lots of ways to train• More responsive/More Control• Typical developer only needs a few weeks to a
month of training• Recruit developers outside of the Microsoft
stack
Native - MonoTouch
• Use the .NET Framework (huge)• Reuse some existing code• Take advantage of training of existing
Microsoft developers (fast rampup)• Responsive
Might Not Even Need to Write
Unexpected Bonus of iPad Apps
Hey Baby, I wrote
Mobile Device Management
• Encryption of Data• Expiration of Data• Authentication• Remote Device Wipe of Selective Data• Application Delivery (based on version of OS)• Variety of devices
Shared Data/Logic
• Microsoft Web API• Built on ASP.NET MVC• Replaces WCF• Simple• Restful• Uses HTTP like it was meant to be used
Think about Framework
• Data Encryption• Data Expiration• Authentication• SSL
Other Apps Not Shown
• APS/Document Management• Time Entry• Marketing Business Intelligence• Budgeting• Firm-wide Business Intelligence