2. Forward-Looking Statements
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.
3. Blue Wave Group and Me
Based in the UK and Ireland
Salesforce Silver Cloud Alliance Partner
30 Employees
• 20 Certified Salesforce Professionals
• 11 Salesforce University Instructors
IBM Partner (since 2000)
@bluewavegroup.eu
4. Who are you?
Intended Audience
You are familiar with Salesforce Lightning Design System
Have created Lightning Components
Retrieved data for a Lightning Components via apex
Have customers that have requirements to satisfy
5. DEV601 – Programming Lightning Components
Topics included in the course
Component Basics
Surfacing Components (SF1)
Creating and Destroying Components
{!v.Body} design patterns
Application and Component Events
Inheriting from other Components
Form Validation and theming
Improvements since Spring 16
LEX, Record Home Pages & Utility Bar!
Caching Data & Applications
SLDS included in the Lightning Framework
Lightning Base Components
Comprehensive Form Validation
30% less code to complete course exercises.
Developers can deliver better Lightning functionality than they could 12 months ago
6. Forming Solutions For Customers
Most Training material available on Lightning Component
Development is very workshop-like in nature.
To Deliver Components to Customers, there are a
number of considerations
User Interface & Customer Acceptance
Component Design & Data Integration
Creating Bridges between Administrators and Customers
From a blank screen to a solution
7. User Interface Design
An excellent tool introduced at Dreamforce 16 by the SalesforceUX team
Workshop: http://sfdcworkshop.com/workshop/rapid-prototyping-with-slds
Github: https://github.com/salesforce-ux/design-system-starter-kit
Rapid Prototyping using SLDS, HTML and SASS
8. Lightning Design System Starter Kit
Rapid Prototyping using SLDS, HTML and SASS
Has replaced Balsamiq Mockups in making mock screens for our clients
Provides a near-final mock-up of the solution that is easily changed
Provides HTML and mark-up for the Components
9. Lightning Design System Starter Kit
Rapid Prototyping using SLDS, HTML and SASS
Demo
Can be deployed to Heroku (with Username and Password authentication) or customers to view,
discuss and provide feedback before development starts.
Webinar: https://youtu.be/oJm2nQz-tKM
Nunjucks: https://mozilla.github.io/nunjucks/
10. Lightning Design System Starter Kit
Rapid Prototyping using SLDS, HTML and SASS
Updated in Spring 17
Sharing json data among pages has
been added.
Any improvements to SLDS can be added
(eg) Utility Bar
11. Component Design
Factors to Consider
Structural Components
Components should be as small as possible
Sandbox a specific function
Simplify your code!
Allows developers to separate out work
Should make testing more efficient
Re-usability is the primary reason to create a
component.
..but Cost/Benefit and Deliverability are
factors too!
Development of components (and events)
takes time (and cost)
Re-usability where can my component be
useful?
14. Component Design
Checkbox Group code
available at
github.com/barryhughes1
- also available as a tutorial
Re-usability Use Case: The ‘All’ Checkbox
15. Developers! Build Bridges!
... Code for the overall solution
The Setup menu remains the Salesforce platform’s key feature set
Developers are required when a requirement cannot be provided via the setup menu
The answer is no longer – ‘Make a Visualforce Page’!
• Replacing entire screens.
• Maintenance costs.
• Breaks the relationship between the Administrator and the Customer.
With Lightning, a Developers Role is now to enhance the solution
and not replace it with customised code.
17. Best Practices Resources
Lightning Component Development
Modularizing Code in Lightning Components http://sforce.co/2qk2DiL
Advanced Lightning Apps http://sforce.co/2h6WulP
Component Performance http://sforce.co/2qashpf
Caching Data with Storable Actions: http://sforce.co/2phEqei
Toolkit for Creating and Deploying Bots: http://sforce.co/2oKimKs
Using Third-Party Libraries http://sforce.co/2m5jbJ1
Communicating with Visualforce http://sforce.co/2phEuux
Data Service & Base Components http://bit.ly/2pSv0Yn
DEV601 Programming Lightning Components http://sforce.co/2qnHo2f
Editor's Notes
Talk TrackBefore I begin, just a quick note that you should base your purchasing decisions on products and services that are currently available. Key Takeaway
Salesforce is a publicly traded company. Customer should make buying decisions only on the products commercially available.