Build You First App in 5 Easy Steps

Build Your First Custom Lightning
App in Five Easy Steps
An Admin’s Guide
Dreamforce 2017
#DF17

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.

Rebecca Saar
Sr. Manager, Admin Marketing
Salesforce
@RebeccaSaar Customer or
Salesforce Logo

My Lightning App Building Journey in 5 Steps
Identified
the
Problem
Gathered
Requirements
Became a
Builder
Rolled
Out App
Maintain &
Expand

My Lightning App Building Journey
Identified
the
Problem
Gathered
Requirements
Became a
Builder
Rolled
Out App
Maintain &
Expand

My Problem: A Spreadsheet
I was managing content production for
admin.salesforce.com using a spreadsheet.
The cons were:
• Hard to make edits and change schedule
on the fly
• Not great for collaboration
• Hard to do reporting As any #AwesomeAdmin would, you should
be reacting to the word spreadsheet in horror

Tips to Identify Problems
1. Listen for people talking about spreadsheets
2. Confront them
3. Ask many questions:
Practice SABWA!
Salesforce
Administration by
Walking Around
• What are your paint points?
• What is the current process?
• Who is involved? Who is affected?
• How is the spreadsheet being used?
What works? What doesn’t?
• What does the future look like? How
can you plan ahead?

My Requirements: Manage Production of Content
I had a vision of what it could look like,
but nailing it down exactly was the trick:
• Calendar view of our upcoming content
• Visualization of the process and status
of content
• Ability to report on content produced
• Easy collaboration on content

Tips for Gathering Requirements
• Interview your stakeholders:
• Dig deeper than the surface level request, figure out the
underlying reasons behind the request
• Take diligent notes
• Determine what data you need to capture in order to:
• Manage processes
• Do reporting
• Automate things
• Think about future requirements & scalability:
• More Users? Multiple teams? Different Content?
Keep Asking Why!
Eventually you’ll get
to the real
requirement

I Became a Builder
I started with the data model
because I knew a strong
foundation would be key to
success.
• Created 4 custom objects, 4
record types, 36 custom fields
• Used junction objects to create
many-to-many relationships
• Created validation rules to
ensure users follow the process
• Built different reports to ensure
I captured data correctly

Customizing My App
The design of the record
layouts and homepages was
very important to me
because I knew it would help
drive adoption.
I got very familiar with
Lightning App Builder to
achieve that!

Key Features in My App
I used awesome features to
make my fully functioning
content management app!
• Calendar anything
• Path
• Custom home pages
• Reports & Dashboards

Tips for Building
• Think about the data you want to capture and how it
relates to other data
• Use a DE org and start trying things out
• Design a data model that is scalable and future-proof,
consider:
• Objects vs Record types vs Page Layouts
• Standard vs custom
• Use tools like Lightning App Builder to thoroughly
customize your app
Draw It Out
Use paper, PPT or an
app to visualize how
data is connected.

Identified
the
Problem
Gathered
Requirements
Became a
Builder
Rolled
Out App
Maintained
&
Expanded

My Rollout Experience
1. Built out everything in a
Sandbox
2. Created a test user to see what
end-users see
3. Demoed the app during our
team meeting
4. Added the team as users
5. Continued to optimize

Tips for Rolling Out Your App
• Don’t build in production!
• Create a test user to troubleshoot issues before
your real users runs into them
• Demo your app live, leave room for questions
• Find great tips for demoing here:
bit.ly/rockyourdemo
• Add users who are ready and schedule time to
check-in
Plan a Great Demo!
A thoughtful demo
will result in high
user adoption.

Identified
the
Problem
Gathered
Requirements
Became a
Builder
Rolled
Out App
Maintain
& Expand

Future of My App
Now:
• Have a high-level calendar view
• Manage content production process, review upcoming
content during our weekly meetings
• Report on how much content we’re producing
Next:
• Adding automation and alerts to some of our processes
• Packaging my app

Tips to Maintain & Expand Your App
• Incorporate use of the app into how you and
your team work
• Use Salesforce Optimizer to understand how
effective your app is
• Be on top of release notes to see what new
features you can incorporate
• Plan further iterations
Use Optimizer!
Run the report to
understand how your
app is performing.

Now It’s Your Turn!
Complete my trailmix for in-depth guidance:
• bit.ly/buildanapptrailmix
Share your apps with me!
• Tweet me (@RebeccaSaar) tag #AwesomeAdmin

Build You First App in 5 Easy Steps

Build You First App in 5 Easy Steps

More Related Content

What's hot

What's hot (20)

Similar to Build You First App in 5 Easy Steps

Similar to Build You First App in 5 Easy Steps (20)

Recently uploaded

Recently uploaded (20)

Build You First App in 5 Easy Steps