client technology directions

Client Technology Directions

Rob McAveney

Chief Architect


Session Format

Minimal prepared content

▫ Just a few slides

▫ No conclusions, just ideas

Open discussion

▫ Are we headed in the right direction?

▫ What are we missing?

▫ What else is the community doing?


Current Client Landscape

Browser clients: IE, FF, Chrome, Edge (soon)

▫ Browser extensions

Mobile: Aras Flow, Component Search

Connectors: Office, CAD, etc.

Desktop apps: Aras Update, Batchloader, etc.

Client SDK

▫ IOM.dll

▫ Xamarin: iOS, Android, RT


Challenges

WAN / High Latency

Sync / Async

Client API


Over the Wire

SOAP vs. REST

AML vs. JSON vs. HTML

OData


Browser Clients

Design Patterns

▫ MVC

▫ MVVM

Toolkits

▫ Dojo

▫ Jquery

▫ Angular

▫ Others?


Mobile Clients

Approaches

▫ Native code on each platform

▫ Cross-platform toolkits – Xamarin

▫ HTML-based apps: Cordova / PhoneGap

▫ Web-only with responsive design

Platform support

▫ iOS, Android, Windows

▫ Tablet vs. phone


Open Discussion


Thank you for your input

for making

ACE 2016

a great success

Special thanks to all

who participated at

ACE 2016

YOU

THANK

Look for the

ACE 2016 Survey

in your email and

please fill it out

THANK for making

ACE 2016

a great successYOU

See you next year

@ ACE 2017!

THANK for making

ACE 2016

a great successYOU