Lightning in a Bottle
Jeff Goree, CodeScience Solution Architect, jeff@codescience.com
Architecting Packages with Lightning Components
What we’ll cover
Design Build Package Deploy Maintain
Time
and Cost
6’0” 6’0”
5’0” 5’0”
4’0” 4’0”
3’0” 3’0”
2’0” 2’0”
1’0” 1’0”
The usual suspects…
Architect Developer Product Owner
A use case…
https://bit.ly/sfmailchimp
What we’ll cover
Design Build Package Deploy Maintain
Time
and Cost
Lightning Design System - www.lightningdesignsystem.com
ISVForce Guide – https://bit.ly/isvforce
SLDSX – Sample Lightning Components – https://bit.ly/sldsx
3 Approaches:
1. Visualforce
2. HTML/CSS Framework (Bootstrap)
3. Lightning Components
UX, UX, UX
Design
Considerations
1. Visualforce
2. HTML/CSS Framework (Bootstrap)
3. Lightning Components
UX, UX, UX
Design
Approaches
~40 Existing Visualforce pages
Identify use of custom styles
Identify use of advanced javascript
Determine which approach
1. How many apex tags are used?
2. Has the framework been customized?
3. <apex:actionFunction /> should be treated carefully
Any Mailchimp users?
Design
Use Case
What we’ll cover
Design Build Package Deploy Maintain
Time
and Cost
1. Prototype
2. Build
3. Test
Build
Approach
dev
int
pkg
Prototype
Build
Demo and Walk-thru
Build
Code
Test
Build
What we’ll cover
Design Build Package Deploy Maintain
Time
and Cost
Package
Considerations
Component Upgradeable
Subscriber
Deletable
Developer
Deletable
Protectable IP Protection
Lightning Application
Yes No No No No
LightningComponent
Yes No No No No
Lightning Event
Yes No No No No
Lightning Interface
Yes No No No No
ISVForce Guide – https://bit.ly/isvforce
CRUD/FLS and Sharing – Force.com Security Library – https://bit.ly/sfdcsecure
Source Scanner – https://bit.ly/sfdcscanner
ZAP Scanner – https://bit.ly/sfdczap
Package
Security
What we’ll cover
Design Build Package Deploy Maintain
Time
and Cost
Considerations
Deploy
What we’ll cover
Design Build Package Deploy Maintain
Time
and Cost
You NEED customer service
Opportunity to train junior team
Push upgrades are powerful… QA
Proper source control
Considerations
Maintain
Some of my favorite things:
1. Connected apps with multiple devs
2. Callouts from javascript in lightning
3. Namespacing LDS
Considerations
Maintain
What we’ll cover
Design Build Package Deploy Maintain
Time
and Cost
Time and Cost
Considerations
Design Build Package Deploy Maintain
Traditional
Thank you
Share Your Feedback, and Win a GoPro!
3
Earn a GoPro prize entry for
each completed survey
Tap the bell to take a
survey2Enroll in a session1

Lightning in a Bottle: Architecting Packages with Lightning Components

Editor's Notes

  • #2 Minions for who was out the latest?
  • #5 Architects? Front end dev? Back end dev? Product Owner?
  • #7 Who has seen Lightning UI …Design system? …SDSX?
  • #9 Review design guide to make sure this is compatible
  • #12 Integration branch, no integration branch?
  • #13 Nice tie in: Get blog post – “How we designed the new Salesforce at scale”… review Lightning video (Greg…) https://www.salesforce.com/blog/2015/08/how-we-designed-the-new-salesforce-at-scale.html
  • #14 Show old UI, new UI, here is what we did with lightning components Review UX version of mapping Review real version of mapping Review lightning component
  • #17 Mention API transactions, data usage
  • #20 Users have to use the waffle Upgrading prior versions can be tricky APEX – properly use an install script Work with metadata API from setup/getting started page
  • #22 You need customer service Opportunity to train JR devs, BA’s, admins Push upgrades are powerful…test, test, test Some things we’ve encountered… connected apps
  • #23 You need customer service Opportunity to train JR devs, BA’s, admins Push upgrades are powerful…test, test, test Some things we’ve encountered… connected apps
  • #25 Mention reuse driving reduction in build costs – DRY and lightning architecture drives reusing components – Tell story of patient details reused throughout HCLS application