1. Building Lightning Apps
Kitchener, Canada Developer Group
Speaker
Date
Venue/Link
Daniel Peter
August 25th, 2018 @ 10:00 AM EST
https://zoom.us/j/391873868
3. Who Am I?
Sudipta Deb
● Technical Architect with Appirio Inc., a Wipro Company
● 2.5X Trailhead Ranger
● 7x Salesforce Certified
● Blogging at www.sudipta-deb.in
● Co-Organizer of Kitchener, Canada Developer Group
● Follow me @sudipta_1984
4. Our Speaker
Daniel Peter
● Salesforce MVP
● 24x Salesforce Certified
● Bay Area Salesforce Developer Group Leader
● Independent Consultant
7. Think hard about containers
● Lightning Component
● Stand alone Lightning app
● Lightning Component tab, within Lightning Experience
● Lightning Component, inside of an existing record page
● Lightning out in Visualforce
● Utility Bar
8. Think hard about containers
● Design so it can be used for one or more of these.
Maintain the core code in one place.
● Consider developing in a Lightning app, even if that
isn’t the final container
● Not all features work in all containers.
● Classic? Stand alone app, switch over, lightning out
11. Interfaces
flexipage:availableForAllPageTypes
lightning pages, record pages, utility bar
flexipage:availableForRecordHome
record pages
Give it an SVG icon for app builder
force:appHostable
lightning tab in lightning experience or standalone app
force:lightningQuickAction, force:lightningQuickActionWithoutHeader
forceCommunity:availableForAllPageTypes
Community Builder
force:hasRecordId
context of a record, you get v.recordId for free
12. Binding, State
How data “flows” or is referenced between the components.
<c:child childAttr="{!v.parentAttr}" /> (bound)
<c:child childAttr="{#v.parentAttr}" /> (unbound)