architecting packages with lightning components
TRANSCRIPT
Lightning in a Bottle
Jeff Goree, CodeScience Solution Architect, [email protected]
Architecting Packages with Lightning Components
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
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
Package
Considerations
Component UpgradeableSubscriber
Deletable
Developer
DeletableProtectable IP Protection
Lightning ApplicationYes No No No No
LightningComponentYes No No No No
Lightning EventYes No No No No
Lightning InterfaceYes 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
You NEED customer service
Opportunity to train junior team
Push upgrades are powerful… QA
Proper source control
ConsiderationsMaintain
Some of my favorite things:
1. Connected apps with multiple devs
2. Callouts from javascript in lightning
3. Namespacing LDS
ConsiderationsMaintain