4. What is a design pattern?
“…a description or template for how to solve a problem that can be used in many different
situations.” (Design Patterns Explained Simply)
Characteristics:
• Not a solution
• Not a law
• Based on deep thinking and consideration
• Illustrates best practices or optimized approach
5. “I can’t refresh [x]
when changes take place.”
“I can just build [x] in
Visualforce.”
“Javascript buttons and URL
hacks don’t work.”
3 Common Problems
…when transitioning from Aloha
6. Think apps vs pages Leverage actions Code for context
3 Design Patterns
…available in Lightning
7. App All The Things!
Every ‘page’ is an app
Lightning App Builder:
• Page ‘types’: App Page, Record Pages, Home Page
• Drag-and-drop WYSIWYG editing (with live* data)
• Complex, nested UI components
• Native AppExchange connection
• Support for context (record data in report charts, flow components, custom components)
8. Accelerate with Actions
Less clicks and faster forms
Global & Quick Actions:
• Creating or updating related* records (with field values pre-populated!)
• Launch custom Lightning components
• Launch Visualforce pages
• Launch Canvas apps
11. Resources & Kudos
Work those apps!
https://trailhead.salesforce.com/modules/lightning_app_builder
Go deep with actions!
https://trailhead.salesforce.com/en/lex_migration_customization/lex_migration_customization_acti
ons?id=lex_migration_customization
Slip into context!
https://trailhead.salesforce.com/projects/workshop-lightning-restaurant-locator