View source for Building for change by using App Studio

Building for change by using App Studio / ← Build for change using App Studio

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in one of the groups: Users, editor, pegaemployee.
• The action you have requested is limited to users in one of the groups: pegaemployee, editor, Administrators.

---

You can view and copy the source of this page.

{{Design pattern |Title=Build for change using App Studio |Description=Building applications using App Studio using configuration rather than customization |Version=8.4 |Applications=Pega Platform |Capability Area=Case Management |Owner=}} Living the #AppStudioLifestyle means starting all Pega application development in [[App Studio]] using capabilities available out of the box. It means that regardless of your skill level or technical prowess with Pega Platform™, you see the value of App Studio and you do everything you can to maximize the value you can get from building in App Studio rather than Dev Studio.</p><div style="font-weight: 400;"><p>As much as possible, you configure your application rather than customizing it.</p></div><div style="font-weight: 400;"><h2><span class="mw-headline" id="What_this_means_for_experienced_developers:"><span class="mw-headline" id="What_this_means_for_experienced_developers:">What this means for experienced developers</span></span></h2></div><div style="font-weight: 400;"><p>We understand that everything you may want to do isn’t available in App Studio. For experienced Pega developers, there are many things that you can only accomplish using Dev Studio – and that is okay!</p></div><div style="font-weight: 400;"><p>Think about the people that are building in App Studio as you build components in Dev Studio so you can ensure that they surface themselves appropriately in App Studio. We don’t want to box-out users or degrade the value proposition of our model-driven environment by not allowing edits to be made in App Studio because a component had been built or changed in Dev Studio in a way that’s not compatible.</p></div><div style="font-weight: 400;"><p><span style="font-family: -apple-system, BlinkMacSystemFont,">This means:</span></p></div> * creating data pages that are compatible with App Studio Data Objects * using templatized UI as much as possible and always wrapping custom capability in a way that it can be accessed via App Studio  * above all: testing that what you building Dev Studio can be leveraged in App Studio.<span id="Why_is_this_important?"></span><span class="mw-headline" id="Why_is_this_important.3F"><span id="Why_is_this_important.3F"></span></span> == <span class="mw-headline" id="Why_is_this_important.3F"><span class="mw-headline" id="Why_is_this_important.3F">Why is this important?</span></span> == === <b>Focus on the highest value work</b> === <div style="font-weight: 400;"><p>If citizen developers are able to do basic configuration of applications in App Studio, that means experienced developers can spend time doing more detailed and difficult work that is only possible in Dev Studio. This is the value-added work that more experienced developers should be working on.</p></div><div style="font-weight: 400;"> === <b>Upgrade and get the latest features</b> === </div><div style="font-weight: 400;"><p>If an application is built in App Studio, it will be more upgradable in the future. Keeping applications current on the latest version of Pega Platform allows them to take advantage of our latest features.</p></div>

Return to Build for change using App Studio.