TiConf.us Titanium User Conference June 27th, 2013 Tremont Hotel Baltimore, MD USA
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
30,000,000 New Users of Titanium apps in the past quarter
• 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
• We are in progress on it now:
– Complete regression under way
– Early Apple beta(s), tools pre"y buggy – trying to
understand their stabilizaKon eﬀorts
– First priority is making sure current API and Apps
• We will make a release available as soon as
we can – assuming Apple gives us all Kme
• iOS5 support will be deprecated with release
Recent updates – 3.1.1
• Oﬃcial Tizen support
• BB10 Beta
• Google Maps v2
• Android 2.3.3
• 3.1.2 targeted for August
• EsKmated availability: Fall (or as soon as iOS7)
• Major impacts:
– Android animaKon improvements
– Improvements around Studio Experience
– Expanded CLI capabiliKes
• Win8 in progress – but will be on Ti.next
Big items we’re focused on
• Developer ProducKvity
– Speed of development (such as Alloy, ACS)
– Speed of app execuKon
– Improved tool chain, ﬂexibility
– Improved Studio experience
– Development workﬂow
ACS + Node.ACS Success
• Massive adopKon happening – especially by
– Approaching billion API calls
– One app recently did 2M+ API calls in ~30M
– Autoscaling to ~3,500+ virtual servers
• Big capabiliKes coming:
– More enterprise data connectors
– Monitoring / management
The Appcelerator Platform The only platform build for a mobile first world
Warning: This is not free
and can be quite
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
Ti.Next Company Confidential
100% of the informaKon about Ti.Next
is likely to change and will change. It’s
sKll 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 Jeﬀ Haynie?
• 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
• 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 libﬃ)
– Faster than naKve code (in most situaKons)
• Massive maintenance improvements
• separate teams per plamorm + core runKme team. Many
diﬀerent skills sets required.
• TesKng is very hard, laborious, error prone.
• Linear increase in cost for each new plamorm, version
• Be"er ability to reduce footprint in core runKme which will
oﬀer ease of maintenance and upkeep, easier to test
• Adding new plamorms, features, version - ‐ much faster,
– Today: oﬀers 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 ﬁnd a way to
have some level of module API for portability –
but will likely only work in small % of modules.
– 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
• No idea at this moment J
– Likely will be called Ti 4.0
– As usual, release oqen, release early – and
– Want to have ﬁrst set of developer builds
available soon to GitHub repo – possibly in the
next 45- ‐60 days.
– ProducKon builds are a ways away
• StarKng with iOS, Android and Win8 as
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
• Small footprint “core runKme” based on
– <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 diﬀerent for each plamorm based on