TiConf.us

Titanium User Conference
June 27th, 2013
Tremont Hotel
Baltimore, MD USA

h"p://www.flickr.com/photos/ktylerconk...
Fundamental Shifts
Mobile is disrupting everything
Huge opportunity & massive disruption
Mobile is redefining speed
Rate of change and disrup...
Mobile Requires
a Fundamentally
Different Approach
30,000,000 
New Users of Titanium apps in the past quarter
iOS7 Update
Yeah!	
  	
  :<	
  
•  We	
  all	
  get	
  to	
  change	
  our	
  apps,	
  all	
  over	
  again!	
  
•  Great	
  thing	
  ...
When?	
  
•  We	
  are	
  in	
  progress	
  on	
  it	
  now:	
  
– Complete	
  regression	
  under	
  way	
  
– Early	
  A...
Ti.Current
Recent	
  updates	
  –	
  3.1.1	
  
•  Official	
  Tizen	
  support	
  
•  BB10	
  Beta	
  
•  Google	
  Maps	
  v2	
  
•  A...
Ti 3.2
3.2	
  Release	
  
•  EsKmated	
  availability:	
  Fall	
  (or	
  as	
  soon	
  as	
  iOS7)	
  
•  Major	
  impacts:	
  
–...
Big	
  items	
  we’re	
  focused	
  on	
  
•  Developer	
  ProducKvity	
  
– Speed	
  of	
  development	
  (such	
  as	
  ...
Cloud Update
ACS	
  +	
  Node.ACS	
  Success	
  
•  Massive	
  adopKon	
  happening	
  –	
  especially	
  by	
  
big	
  companies.	
  
...
The Appcelerator Platform
The only platform build for a mobile first world
Warning:	
  This	
  is	
  not	
  free	
  
and	
  can	
  be	
  quite	
  
expensive	
  
Dashboard
DEVELOPMENT PRODUCTION
Users
Cloud Test Performance Analytics
Cloud Foundation
PRODUCT
MANAGER
DEV MANAGER QA MA...
Company Confidential
Company Confidential
Ti.Next
Company Confidential
Warning!	
  Disclaimer!	
  
100%	
  of	
  the	
  informaKon	
  about	
  Ti.Next	
  
is	
  likely	
  to	
  change	
  and	
 ...
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	
  generaKon	
  architecture	
  for	
  Titanium	
  
– Leverage	
  over	
  4	
  years	
  of	
  learning...
Ti.Next	
  Goals	
  
•  Massive	
  performance	
  gains	
  
– Reduce	
  footprint	
  in	
  terms	
  on	
  physical	
  size...
Ti.Next	
  Goals	
  
•  Massive	
  maintenance	
  improvements	
  
–  Today:	
  	
  
•  separate	
  teams	
  per	
  plamor...
Ti.Next	
  
•  Extensibility	
  
– Today:	
  offers	
  same	
  challenges.	
  Each	
  module	
  
requires	
  naKve	
  langu...
Ti.Next	
  
•  Tooling	
  
– Unique	
  tooling	
  per	
  plamorm	
  -­‐>	
  one	
  set	
  of	
  tooling	
  
for	
  all	
  ...
Quick	
  Demo?	
  
Ti.When?	
  
•  No	
  idea	
  at	
  this	
  moment	
  J	
  
– Likely	
  will	
  be	
  called	
  Ti	
  4.0	
  
– As	
  usu...
Ti.Next	
  Approach	
  
•  StarKng	
  with	
  iOS,	
  Android	
  and	
  Win8	
  as	
  
reference	
  architecture.	
  
•  C...
Ti.Next	
  Architecture	
  
•  Small	
  footprint	
  “core	
  runKme”	
  based	
  on	
  
JavaScriptCore	
  and	
  libffi	
  ...
Ti.Next	
  Architecture	
  
•  Titanium	
  APIs	
  all	
  implemented	
  in	
  JavaScript	
  
•  Compiler	
  at	
  opKmiza...
THANK YOU

@jhaynie
Titanium Conf Baltimore Keynote 2013
Titanium Conf Baltimore Keynote 2013
Titanium Conf Baltimore Keynote 2013
Titanium Conf Baltimore Keynote 2013
Titanium Conf Baltimore Keynote 2013
Titanium Conf Baltimore Keynote 2013
Titanium Conf Baltimore Keynote 2013
Upcoming SlideShare
Loading in...5
×

Titanium Conf Baltimore Keynote 2013

8,470

Published on

Jeff's keynote for TiConf Baltimore on June 28, 2013 in Baltimore, MD, USA.

Published in: Technology
2 Comments
16 Likes
Statistics
Notes
  • Great, but keep going on BlackBerry 10 support. It's useable right now for the core TI APIs, but to get 'Built for BlackBerry' certified you need to be able to integrate with BlackBerry 10 specific stuff like BBM or their 'invoke' (share) API.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Tx so much Jeff. Very interesting
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
8,470
On Slideshare
0
From Embeds
0
Number of Embeds
16
Actions
Shares
0
Downloads
0
Comments
2
Likes
16
Embeds 0
No embeds

No notes for slide

Titanium Conf Baltimore Keynote 2013

  1. 1. TiConf.us
 Titanium User Conference June 27th, 2013 Tremont Hotel Baltimore, MD USA h"p://www.flickr.com/photos/ktylerconk/3181331268/  
  2. 2. Fundamental Shifts
  3. 3. 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
  4. 4. Mobile Requires a Fundamentally Different Approach
  5. 5. 30,000,000 New Users of Titanium apps in the past quarter
  6. 6. iOS7 Update
  7. 7. Yeah!    :<   •  We  all  get  to  change  our  apps,  all  over  again!   •  Great  thing  for  Titanium  developers  (sort  of)   •  Lots  of  interesKng  capabiliKes   – Background  processing   – Auto  layout   – Fullscreen  
  8. 8. When?   •  We  are  in  progress  on  it  now:   – Complete  regression  under  way   – Early  Apple  beta(s),  tools  pre"y  buggy  –  trying  to   understand  their  stabilizaKon  efforts   – First  priority  is  making  sure  current  API  and  Apps   works   •  We  will  make  a  release  available  as  soon  as   we  can  –  assuming  Apple  gives  us  all  Kme   •  iOS5  support  will  be  deprecated  with  release  
  9. 9. Ti.Current
  10. 10. Recent  updates  –  3.1.1   •  Official  Tizen  support   •  BB10  Beta   •  Google  Maps  v2   •  Android  2.3.3   •  3.1.2  targeted  for  August    
  11. 11. Ti 3.2
  12. 12. 3.2  Release   •  EsKmated  availability:  Fall  (or  as  soon  as  iOS7)   •  Major  impacts:   – Android  animaKon  improvements   – Improvements  around  Studio  Experience   – Expanded  CLI  capabiliKes   – iOS7   •  Win8  in  progress  –  but  will  be  on  Ti.next  
  13. 13. Big  items  we’re  focused  on   •  Developer  ProducKvity   – Speed  of  development  (such  as  Alloy,  ACS)   – Speed  of  app  execuKon   – Improved  tool  chain,  flexibility   – Improved  Studio  experience   – Development  workflow  
  14. 14. Cloud Update
  15. 15. ACS  +  Node.ACS  Success   •  Massive  adopKon  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  capabiliKes  coming:   – SynchronizaKon   – More  enterprise  data  connectors   – Monitoring  /  management  
  16. 16. The Appcelerator Platform The only platform build for a mobile first world
  17. 17. Warning:  This  is  not  free   and  can  be  quite   expensive  
  18. 18. Dashboard DEVELOPMENT PRODUCTION Users Cloud Test Performance Analytics Cloud Foundation PRODUCT MANAGER DEV MANAGER QA MANAGER EXECUTIVE APP App Studio Appcelerator Platform DESIGNER DEVELOPER QA ENGINEER DEVELOPER
  19. 19. Company Confidential
  20. 20. Company Confidential
  21. 21. Ti.Next Company Confidential
  22. 22. Warning!  Disclaimer!   100%  of  the  informaKon  about  Ti.Next   is  likely  to  change  and  will  change.  It’s   sKll  a  lab  experiment  today.  
  23. 23. How Titanium feels as an App developer?
  24. 24. How Titanium feels as an App developer?
  25. 25. How Titanium feels as a core platform developer?
  26. 26. How Titanium feels if you’re Jeff Haynie?
  27. 27. Ti.Next   •  Next  generaKon  architecture  for  Titanium   – Leverage  over  4  years  of  learning   – Complete  re-­‐write  of  core  engine   – Ti  API  compaKble  (for  the  most  part)   – One  JS  engine  and  core  runKme  to  rule  them  all  
  28. 28. Ti.Next  Goals   •  Massive  performance  gains   – Reduce  footprint  in  terms  on  physical  size  of   binary  and  in-­‐memory  footprint   – Reduce  garbage  collecKon  overhead  to  minimal   – Simplify  threading  model  and  context  switching   – Increase  per  operaKon  performance  by  several   orders  of  magnitude:  ~20+ms/op  -­‐>  ~100+μs/op   – Move  from  naKve  language  to  ASM  generated   code  (ObjC-­‐>ASM  via  libffi)   – Faster  than  naKve  code  (in  most  situaKons)  
  29. 29. Ti.Next  Goals   •  Massive  maintenance  improvements   –  Today:     •  separate  teams  per  plamorm  +  core  runKme  team.  Many   different  skills  sets  required.   •  TesKng  is  very  hard,  laborious,  error  prone.   •  Linear  increase  in  cost  for  each  new  plamorm,  version   combinaKon   –  Tomorrow:   •  One  main  skillset:  JavaScript   •  Be"er  ability  to  reduce  footprint  in  core  runKme  which  will   offer  ease  of  maintenance  and  upkeep,  easier  to  test   •  Adding  new  plamorms,  features,  version  -­‐  much  faster,   easier  
  30. 30. Ti.Next   •  Extensibility   – Today:  offers  same  challenges.  Each  module   requires  naKve  language  skills  and  complexity.   – Tomorrow:  leverage  same  JS  API  to  create  cross-­‐ plamorm  modules   – Impact:  Module  API  will  change  dramaKcally,   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.  
  31. 31. Ti.Next   •  Tooling   – Unique  tooling  per  plamorm  -­‐>  one  set  of  tooling   for  all  plamorms.  Invest  our  Kme  in  new   capabiliKes  vs.  maintaining  mulKple  integraKons   – Much  faster  build  Kmes  and  packaging.   – Increased  deployment  and  authoring  opKons  
  32. 32. Quick  Demo?  
  33. 33. Ti.When?   •  No  idea  at  this  moment  J   – Likely  will  be  called  Ti  4.0   – As  usual,  release  oqen,  release  early  –  and   transparently.   – Want  to  have  first  set  of  developer  builds   available  soon  to  GitHub  repo  –  possibly  in  the   next  45-­‐60  days.     – ProducKon  builds  are  a  ways  away  
  34. 34. Ti.Next  Approach   •  StarKng  with  iOS,  Android  and  Win8  as   reference  architecture.   •  Core  runKme  is  based  on  JavaScriptCore  (VM   part  of  WebKit).   – Leverage  new  iOS7  ObjecKve-­‐C  Framework   – Ported  new  ObjecKve-­‐C  APIs  to  C#,  Java   – Built  gyp-­‐based  build  tools  for  Win,  Android  
  35. 35. Ti.Next  Architecture   •  Small  footprint  “core  runKme”  based  on   JavaScriptCore  and  libffi   –  <5,000  LOC  (vs.  100K+)   –  Micro-­‐kernel  design   –  Heavily  opKmized  for  performance,  memory  footprint   –  Very  stable,  won’t  change  oqen   –  Exposes  2  APIs:     •  Core  RunKme  API  same  for  plamorms,  very  few  methods   •  Core  Plamorm  API  different  for  each  plamorm  based  on   underlying  plamorm  API  (Cocoa,  Android,  Win8)   •  Same  design  pa"erns  and  idioms  
  36. 36. Ti.Next  Architecture   •  Titanium  APIs  all  implemented  in  JavaScript   •  Compiler  at  opKmizaKon  phase  will  convert   plamorm  APIs  into  naKve  code  (ASM)   •  New  plamorm  APIs  can  be  accessed  without   upgrade  to  new  APIs  (before  Ti  API  work).   •  Similar  to  how  node.js  is  built  (from  an  API   standpoint)   •  During  development  phase,  no  (naKve)   compiler  required  
  37. 37. THANK YOU @jhaynie

×