How to Get Started With Dev Studio in Salesforce?

Published: Aug 03 2026

Last Updated: Oct 23 2026

Get Started with Dev Studio

Salesforce development isn’t always about building complex applications. Sometimes, it’s a small change to an Apex class, a quick fix in a trigger, or an update to a Lightning Web Component. Yet, even routine tasks can involve switching between tools, locating files, and moving between a local development environment and your Salesforce org.

For developers handling frequent updates, these extra steps can interrupt the workflow and add unnecessary effort.

What if you could manage your Salesforce code directly inside your org, without setting up a separate local environment for routine tasks?

That’s where Dev Studio comes in. It provides a native workspace to create, edit, and manage supported Salesforce code components, including Apex Classes, Triggers, Lightning Web Components, Aura Components, Visualforce, and Static Resources.

In this guide, you’ll learn how to get started with Dev Studio, navigate its interface, and manage your Salesforce code step by step.

Before You Begin

Make sure you have the following:

  • BOFC installed in your Salesforce org, with latest 8.3495 version or later that supports Dev Studio.

  • Permission to create, view, edit, or delete Salesforce metadata and code.

  • Access to the BOFC application.
Quick Install

Follow these simple steps to use Salesforce Dev Studio

01

step 1

Open BOFC app in Your Salesforce Org

Once installed, navigate to the App Launcher in Salesforce (the nine-dot grid icon in the top-left navigation bar) and search for “Bulk Object Field Creator”. Click to open the application

Open BOFC app in Your Salesforce Org

02

step 2

Navigate to Dev Studio

Inside the BOFC application, locate Dev Studio in the main navigation menu.

Navigate to Dev Studio

Click it to open the Dev Studio dashboard.

open the Dev Studio dashboard

The dashboard displays all supported metadata types — LWC, Aura Components, Apex Classes, Apex Triggers, Visualforce Pages, Visualforce Components and Static Resources— as clearly labelled entry points.

03

step 3

Choose Your Metadata Type

Click on the metadata type you want to work with — for example, Apex Classes, or Lightning Web Components to work on your LWC codebase.

Dev Studio will load a list of all existing components or files of that type currently in your Org.

LWC Components

LWC Components

Aura Components

Aura Components

04

step 4

Add, Edit, Delete or Download

From the loaded list, choose your action:

  • To create a new component: Click the “New” button. Dev Studio will open a creation form or code editor where you can define the component name, API version, and some basic configuration before saving directly to the Org.

    LWC Components
    Aura Components
  • To add a file to an existing component: Click the settings icon next to the component. Dev Studio opens the drawer with a set of options. Click “Add File” to add a new file to an existing component.

    add a file to an existing component
  • To edit an existing component or file: Click the file name or component. Dev Studio opens the component’s full code in an in-browser editor. Make your changes and save — the update is applied directly to the Org. Use a shortcut key like “ctrl + S” or “cmd + S” to save the file.

    edit an existing component or file
  • To delete a component or file: Click the “Delete” button next to any listed item. A confirmation prompt will appear before the deletion is executed, ensuring no accidental removals.

    delete a component or file
  • To download a component or file: Click the“download” button next to any listed item. A confirmation prompt will appear before the deletion is executed, ensuring no accidental removals.

    download a component or file

05

step 5

Verify Your Changes in Salesforce

Once saved or deleted, Dev Studio reflects the updated state of your Org immediately. Navigate to the relevant Setup page (e.g., Apex Classes in Setup, or Lightning Components) to verify your changes are live in the Org.

Dev Studio vs Other Salesforce Development Tools

Capability BOFC Dev Studio VS Code + SFDX Developer Console Lightning Studio
Works directly inside Salesforce ✅ ❌ ✅ ❌
Local installation required ❌ ✅ ❌ ❌
Salesforce CLI required ❌ ✅ ❌ ❌
Browser extension required ❌ ❌ ❌ ✅
Separate authentication ❌ ✅ ❌ ❌
LWC Support ✅ ✅ ❌ ✅
Aura Components ✅ ✅ Limited ✅
Apex Classes ✅ ✅ ✅ ✅
Apex Triggers ✅ ✅ ✅ ✅
Visualforce Pages ✅ ✅ ✅ ✅
Visualforce Components ✅ ✅ ✅ ✅
Static Resources ✅ ✅ Limited Limited
Unified interface ✅ ✅ ❌ Partial
Free ✅ ✅ ✅ ✅

Which Salesforce Development Tool Should You Choose?

Dev Studio is designed for developers who want to work with supported Salesforce code components directly inside their org, without configuring a separate local development environment for everyday editing tasks.

VS Code with Salesforce CLI is suitable for development workflows involving local source files, version control, team collaboration, and automated deployment pipelines. Salesforce Developer Console remains useful for certain in-org development and debugging tasks.

The right choice depends on your development workflow. Dev Studio provides an additional option for developers who want to manage supported code components from within Salesforce.

What Can You Do Next With Dev Studio?

Once you are comfortable navigating Dev Studio, explore its supported code types and development workflows to find the capabilities most relevant to your Salesforce projects.

You can also configure Claude AI to assist with code generation, code explanations, and debugging within the supported Dev Studio workflow.

Read the guide: How to Connect Claude to Dev Studio for Faster Salesforce Development.

For a broader overview of its capabilities, visit the BOFC Dev Studio feature page.

Like what you see? Share with a friend.