Publishing • Learn the Ext JS framework for developing rich web applications • Understand how the framework works under the hood • Explore the main tools and widgets of the framework for use in your own applications
20% 2m $201bn $6.3bn 75% of IT decision makers increase spending on cloud computing global software as a service market up 21 percent on 2015 of IT budgets will be deployed in mobile and tablet apps of business content will be authored by machines employees will be required to wear health and fitness tracking devices as a condition of employment will be spent on enterprise apps, up from $149.9 billion in 2015 estimated size of the enterprise wearables, up from $128 billion in 2015 of organisations use advanced analytics to improve decision making
10 Years Email Smartphones Social Media Web Browsers Cloud Computing Desktop Apps Video Conference Tools Search Cloud Computing and Storage Tablets Smartphones Social Media Mobile Apps Web Collaboration Tools CMS Wearable Tech
prototyping • Great to show business users what they are getting before investing • Saves rework down the line and improves specification • Gives development team better chance of estimating correctly Rapid Prototyping
getting components on screen • Choose simple scenarios • Consider using other tools such as Sketch and Prototype • Pre-load stores with data • Fully functional prototype in Sencha Ext JS or Touch Rapid Prototyping
part of the transition to mobile development is the understanding of the user interaction models and how they relate to browser events. Remember to always test any complex interaction models with a physical platform - it is only then you can see how they really react to events.
several ways • Great for events or conferences that don’t last forever • Low costs • Targeted data gathering capabilities • Enhanced engagement Throw Away Apps
2 days • Users would download this app on their phone before or during the festival to vote each beer • User could delete the app after the event had finished Throw Away Apps
full advantage of working offline • Benefit to the user • Don’t need to rely on a connection or data • Boosts application performance Connectivity is vital when app can’t be offline • No way of accessing the app if connection lost • A lot of apps require you to have an internet connection to interact with them
possible by using: • HTML offline storage mediums • localStorage and sessionStorage • Cordova • SQL Lite Plugin • Sencha’s new offline functionality with Service Workers
to work offline using Ext JS • Allows users to manage tasks, workflow and risk in heavy industry • Crucial it has offline support as the user is in the field: • on an oil platform • rail companies underground who won’t be able to get a data connection
capacity used • The more components that are active, the more capacity will be used • Call destroy method on a component • Destroy method sets internal references to null • Hint: Keep reference to important elements so they can easily be destroyed Memory Capacity & No. of Components
tab destroys components of previous view • Has a maximum of 10 form fields per page • Events are triggered to render extra fields when required Memory Capacity & No. of Components
amount of data being sent to the browser • Reduce the data complexity - any time spent manipulating complex data will stop the user being able to interact with the app • Deeply nested and complicated data structures are highly discouraged
mobile application you will be developing is running in a browser and therefore has limited power compared to native mobile applications. Remembering this will let you estimate realistic goals for development.
performance issues by keeping it lightweight • Layout appropriately to make things easy to find • Throw away what you don’t need • Collect feedback on a consumers experience using the app • Install analytics to monitor usage
• By using a simple layout for the menu we achieved ease of use • Keeps clutter to a minimum, with the menu taking up the full screen, increasing performance • Consumer survey carried out to make sure expectations were met
size could cause problems • Limits the application to one device • All potential users will have different devices • Could affect the user experience iPhone 6 1334x750 Retina iPad 1536x2048
• Components are not responsive by default to save on performance • Use the responsive plugin on components • Hint: Use the ‘responsiveCls’ config Screen Size
achieved: • Store metadata in backend • Send metadata to frontend, iterate and build screens • Use configuration files, check for updates in backend • Consider validators
Users search for and review results held on a server • Configuration file was used to control the behaviour and look • Config file can be extracted if local copy is not found
ObjectiveC • Faster performance • Access to hardware • HTML5, JavaScript, CSS • Cross-platform • Access to hardware through plugins There may be times when using native more suits the needs of given requirements
andrewmduncan
pluu
bcinarli
jxck
usamik26
lilobase
yammerjp
alexzhukovich
guikingone
utaani
cokaholic
akitotsukahara
manfredsteyer
zenorocha
jensimmons
myddelton
sferik
paulrobertlloyd
pauljervisheath
bkeepers
reverentgeek
roundedbygravity
chriscoyier
samlambert
searls
