Lightning Components: The Future
1 like1,228 views
The document discusses the future of Lightning components in Salesforce, highlighting the importance of usability, performance, and security within the Aura framework. It includes details on developer productivity tools, such as the Lightning Component Inspector and Cloud9 IDE, aimed at enhancing the development experience. The presentation also emphasizes the need for awareness regarding forward-looking statements and various risks associated with product development and service delivery.
Lightning Components: The Future
- 1. Lightning Components The Future Skip Sauls Director of Product Management [email protected] @SkipSauls Doug Chasman Distinguished Engineer, Force.com Architect [email protected] @dougchasman
- 2. Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward- looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements. Safe Harbor
- 3. • Dreamforce 2014 Recap • Themes • Performance • Security • Developer Productivity • Tools • Q&A Agenda Lightning Components – The Future
- 4. Dreamforce 2014 Recap Lightning Components – The Future ✓ ✓ ✓ ✓ ✓
- 5. Metrics Service • No more Jiffy marks Compiled FCVs • {!v.one + v.two} -> cmp.get(“v.one”) + cmp.get(“v.two”); Unbound Expressions • {#v.value} Component Classes • ltng$myComponent() Action Caching • Replayable actions without server trips Performance– Aura Framework Lightning Components – The Future
- 6. Access Checks • Anything meant to be accessed by others should be marked as access=“GLOBAL” • Components, Apps, Attributes, Interfaces, and Events • Warnings in 198/Winter ‘16 when debug is enabled (post-Dreamforce patch) • Targeting errors in 200/Spring ’16 • Essential for anything that is to be consumed by other users, tools, or apps • Components published to the AppExchange for Components (.design files are not enough!) • Components used within other namespaces • Components used in Visualforce • Components used in Lightning Out • Design for access=“GLOBAL” today and save yourself the trouble tomorrow! Security – Aura Framework Lightning Components – The Future
- 7. Usability – Lightning Data Service Lightning Components – The Future Opportunity List Opportunity Record + hover on related Account Account Record
- 8. • Load a record with <force:record/> • Specify layout and/or fields • Incrementally loads records • Consolidates API calls • No Apex or SOQL Usability – Lightning Data Service Lightning Components – The Future <aura:component> <aura:attribute name="recordId" type="String"/> <aura:attribute name="record" type="Object"/> <force:record recordId="{!v.recordId}" targetRecord="{!v.record}" layout="COMPACT" fields="custom__c"/> </aura:component>
- 9. • Performance boost from client cache • Data available offline • Data consistency across components • Automatic record refresh from server • Automatic notification when records change • Components can be entity-agnostic Usability – Lightning Data Service Lightning Components – The Future <aura:component> <aura:attribute name="recordId" type="String"/> <aura:attribute name="record" type="Object"/> <force:record recordId="{!v.recordId}" targetRecord="{!v.record}" layout="COMPACT" fields="custom__c"/> </aura:component>
- 10. Usability – Lightning Data Service Lightning Components – The Future 0 200 400 600 800 1000 1200 1400 1600 Opportunities Accounts Users
- 11. • Aura method for advanced loading: load() • Aura methods for save() and delete() • Securely save as draft when offline • Friday 12:15pm at Innovation Theatre. Lightning Data Service: Eliminate Your Need to Load Records Through Controllers Usability – Lightning Data Service Lightning Components – The Future <aura:component> <aura:attribute name="recordId" type="String"/> <aura:attribute name="record" type="Object"/> <force:record aura:id="record" recordId="{!v.recordId}" targetRecord="{!v.record}" layout="COMPACT" fields="custom__c"/> </aura:component> ({ saveOrDelete: function(cmp) { cmp.find("record").save(); } })
- 12. Developer Productivity – Components Lightning Components – The Future Chevrons Tabs Activity Timeline Related List Highlights Tree Chatter Feed Grid
- 13. Tools – Lightning Component Inspector Lightning Components – The Future Chrome DevTools Extension http://sfdc.co/inspector Early Access Docs http://git.io/ltng-insp-doc
- 14. Lightning Components – The Future Tools – Cloud9 for Salesforce Developers
- 15. A full-featured cloud IDE: • zero setup – connect and start working • runs in a private Ubuntu Linux workspace dedicated to you First-class Lightning developer tools: • code synchronized between SFDC and Cloud9 • autocomplete: tags, expressions, references, JS • snippets, code outline, quick-jump • built-in documentation • live preview Friday 3:00pm at Innovation Theatre. Intro to Cloud9: Salesforce Web-Based IDE Toolchain: • Run Sass, LessCSS, Ant, Maven from your workspace terminal Collaborate: • Live coding with multiple cursors Complete Salesforce workflow: • Lightning • Apex • Visualforce • Other metadata types Lightning Components – The Future Tools – Cloud9 for Salesforce Developers http://get.c9.io
- 16. Q&A
- 17. Thank you