TiConf Australia 2013

on

  • 7,859 views

This is my keynote presentation from TiConf Australia in Melbourne, Australia. Held at the Smart Artz Gallery on August 20th, 2013. TiConf is a community-led conference for passionate developers, ...

This is my keynote presentation from TiConf Australia in Melbourne, Australia. Held at the Smart Artz Gallery on August 20th, 2013. TiConf is a community-led conference for passionate developers, partners and customers using Appcelerator Titanium and related products.

Statistics

Views

Total Views
7,859
Views on SlideShare
6,913
Embed Views
946

Actions

Likes
4
Downloads
29
Comments
0

7 Embeds 946

http://storify.com 786
https://twitter.com 65
http://eventifier.co 37
http://eventifier.com 29
http://thoughts.applificationhq.dev 18
http://baywatch-preprod.projects.jolicode.com 7
http://translate.googleusercontent.com 4
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Build amazing user experiences across multiple operating systems and devicesLeverage a true Mobile First cloud that includes:A rich set of pre-built mobile APIs Custom services for orchestrating data to ensure performance and data securityAutomatic scalabilityAutomated testing across multiple operating systems and devicesReal-time insights into how applications are performing and being used
  • Build amazing user experiences across multiple operating systems and devicesLeverage a true Mobile First cloud that includes:A rich set of pre-built mobile APIs Custom services for orchestrating data to ensure performance and data securityAutomatic scalabilityAutomated testing across multiple operating systems and devicesReal-time insights into how applications are performing and being used
  • 1M+ projects createdCompanies are using Appcelerator to power mobile businesses (e.g., mFoundry, Denso, instaDM, etc.)Developers in the community have started new companies around Appcelerator

TiConf Australia 2013 TiConf Australia 2013 Presentation Transcript

  • TiConf.au Titanium User Conference August 20th, 2013 Smart Artz Gallery Melbourne, Australia
  • Major Technology Disruptions 1990s - Today Internet Mobile PC Enterprise Data Enterprise Middleware Internet Explosion of Devices Explosion of Data Internet Characteristics • One-to-Many • Weak UX (HTML-based) • Server-centric computing • Global network Characteristics • Many-to-Many • Rich UX (driven by mobile OSs) • Distributed computing • Global network Rise of User Experience PC Enterprise Data Client/Server Characteristics • One-to-One • Rich UX (introduction of GUI) • Distributed Computing • Local Network
  • Fundamental Shifts
  • Mobile is disrupting everything Huge opportunity & massive disruption Mobile is redefining speed Rate of change and disruption is unprecedented The User is King Users are the driving force behind the mobile revolution
  • Mobile Requires a Fundamentally Different Approach
  • Explosion of Devices Explosion of Data Keys to Mobile Success Master the Three A’s of the New Mobile Enterprise Apps APIs Analytics Deliver amazing, cross-platform user experiencesSecurely mobilize any data sourceImprove ROI with real-time visibility across the mobile lifecycle
  • Explosion of Devices Explosion of Data The Appcelerator Platform Master the Three A’s of the New Mobile Enterprise IDE App SDKs Pre-built APIs New APIs Common Mobile Services Integrated Dashboard Automated Testing User Analytics Performance Management Sync Caching Security Auto- Scale
  • Company Confidential
  • Company Confidential
  • When moving at the speed of mobile, vision matters Appcelerator named “Visionary” company with highest placement for vision and execution in Gartner’s 2013 Magic Quadrant for Mobile Application Development Platforms
  • 60,000,000 New Users of Titanium apps in the past 6 months
  • Ti.Current
  • Recent updates – 3.1.2 • GA Blackberry 10 • Android 4.3 support • iOS7 support • Android GCM support • Alloy 1.2: – Dynamic Styling – List View with data binding • 3.1.3 targeted on day Apple makes iOS 7 Generally Available
  • Ti 3.2
  • Big items we’re focused on • Developer Productivity – Speed of development (such as Alloy, ACS) – Speed of app execution – Improved tool chain, flexibility – Improved Studio experience – Development workflow
  • Cloud Update
  • ACS + Node.ACS Success • Massive adoption happening – especially by big companies. – Approaching billion API calls – One app recently did 2M+ API calls in ~30M – Autoscaling to ~3,500+ virtual servers • Big capabilities coming: – Synchronization – More enterprise data connectors – Monitoring / management
  • Ti.Next Company Confidential
  • Warning! Disclaimer! 100% of the information about Ti.Next is likely to change and will change. It’s still a lab experiment today.
  • How Titanium feels as an App developer?
  • How Titanium feels as an App developer?
  • How Titanium feels as a core platform developer?
  • How Titanium feels if you’re Jeff Haynie?
  • Ti.Next • Next generation architecture for Titanium – Leverage over 4 years of learning – Complete re-write of core engine – Ti API compatible (for the most part) – One JS engine and core runtime to rule them all
  • Ti.Next Goals • Massive performance gains – Reduce footprint in terms on physical size of binary and in-memory footprint – Reduce garbage collection overhead to minimal – Simplify threading model and context switching – Increase per operation performance by several orders of magnitude: ~20+ms/op -> ~100+μs/op – Generate as much code into native language
  • Ti.Next Goals • Massive maintenance improvements – Today: • separate teams per platform + core runtime team. Many different skills sets required. • Testing is very hard, laborious, error prone. • Linear increase in cost for each new platform, version combination – Tomorrow: • One main skillset: JavaScript • Better ability to reduce footprint in core runtime which will offer ease of maintenance and upkeep, easier to test • Adding new platforms, features, version - much faster, easier
  • Ti.Next • Extensibility – Today: offers same challenges. Each module requires native language skills and complexity. – Tomorrow: leverage same JS API to create cross- platform modules – Impact: Module API will change dramatically, require new modules. Trying to find a way to have some level of module API for portability – but will likely only work in small % of modules.
  • Ti.Next • Tooling – Unique tooling per platform -> one set of tooling for all platforms. Invest our time in new capabilities vs. maintaining multiple integrations – Much faster build times and packaging. – Increased deployment and authoring options
  • Ti.When? • No idea at this moment  – Likely will be called Ti 4.0 – As usual, release often, release early – and transparently. – Want to have first set of developer builds available soon to GitHub repo – possibly in the next 45-60 days. – Production builds are a ways away
  • Ti.Next Approach • Starting with iOS, Android and Win8 as reference architecture. • Core runtime is based on JavaScriptCore (VM part of WebKit). – Leverage new iOS7 Objective-C Framework – Porting JavaScriptCore to Android, Win8 – New Objective-C OO Layer port to C#, Java – Built gyp-based build tools for Win, Android
  • Ti.Next Architecture • Small footprint “core runtime” based on JavaScriptCore – <2,500 LOC (vs. 100K+) – Micro-kernel design – Heavily optimized for performance, memory footprint – Very stable, won’t change often – Exposes 2 APIs: • Core Runtime API same for platforms, very few methods • Core Platform API different for each platform based on underlying platform API (Cocoa, Android, Win8) • Same design patterns and idioms
  • Ti.Next Architecture • Titanium APIs all implemented in JavaScript • Compiler at optimization phase will convert platform APIs into native code • New platform APIs can be accessed without upgrade to new APIs (before Ti API work). • Similar to how node.js is built (from an API standpoint) but without native modules
  • THANK YOU @jhaynie