Skip to main content
Question

🚀 The Next Philadelphia Qrew Virtual Meetup: Let’s Talk Application Lifecycle Management!

  • November 3, 2025
  • 0 replies
  • 28 views

Forum|alt.badge.img+1

Hey Philly Qrew! 

I’m thrilled to be facilitating our next Philadelphia Qrew Virtual Meetup, and we’re diving into a topic that’s a game-changer for anyone building in Quickbase — Application Lifecycle Management (ALM).  Damon Walls, our guest speaker who also happens to be a Quickbase solutions architect, will lead us through the demonstration answering all of your questions.

Whether you're just starting your journey as a citizen developer or you're a seasoned Quickbase pro, ALM is something that can seriously level up how you build, manage, and evolve your apps.

đź’ˇ What is Application Lifecycle Management?

Let’s break it down in simple terms:

Application Lifecycle Management is all about managing the life of your Quickbase apps — from the moment you start building, through updates and changes, all the way to retirement (if that ever happens!). Think of it like taking care of a garden:

  • You plant the seeds (build your app),
  • You nurture it (make updates, add features),
  • You protect it (test changes before going live),
  • And you grow it (scale it for more users or use cases).

Quickbase’s ALM tools help you do all this in a controlled, scalable, and compliant way. That means fewer surprises, smoother rollouts, and better governance.

đź”— Want to dig deeper? Check out the official Quickbase guide here:
👉 Quickbase Article

🙋‍♀️ Why Should You Care?

Because ALM helps you:

  • Avoid breaking things when making changes
  • Collaborate better with your team
  • Stay compliant with governance policies
  • Deliver faster with confidence

And the best part? You don’t need to be a developer to benefit. Quickbase is all about upskilling citizen developers — giving you the tools to build digital solutions with best practices baked in.

đź§  What Questions Might You Have?

We want this meetup to be interactive and tailored to YOU.

No question is too basic. We’re all at different stages in our journey, and the Qrew culture is all about learning together and lifting each other up.  

Drop your questions about ALM below in the comments!

🎯 What’s Next?

During the meetup, we’ll also brainstorm ideas for our next virtual session. So bring your thoughts, your curiosity, and your energy!

Whether you’re curious, confused, or already crushing it with Quickbase — this is your space to grow.

Are you in? đź’Ą

Forum|alt.badge.img+1
  • Author
  • Registered
  • November 3, 2025

Philadelphia Qrew​ 

Don't forget to register!!!!

November 20th - 4:00 - 5:00 PM EST - Register HERE

Philadelphia Qrew​ 


Forum|alt.badge.img+1
  • Registered
  • November 5, 2025

Here are some thoughts/questions that I had about ALM:

  • What if features are not included in QBL?
    • Do you just make changes to those features in production instead of the development environment?
    • Example: Notification emails or document generation.
  • How are pipelines handled/organized?
    • We have an app with 100 pipelines.
    • If we push that app to “dev” does it create a copy of those 100 pipelines (so we have 200 now)?
    • After publishing from “dev” to “prod” do we now need to go delete all those duplicates? Or will they automatically get deleted the next time we push back to “dev” as part of the cleanup?
    • We try to keep our pipelines organized and seeing duplicates of them all could be confusing as we’re not sure which ones to work on?
  • Can we see a demo which involves pushing to dev, making a change and then pushing back to prod?
  • I heard in the future that Quickbase will have native ALM features in the console itself – and that we won’t need to use a separate app anymore.
    • Can we get a preview of that?
    • When is that coming?
  • Has anyone suggested that Quickbase have a feature where we can document what changes are being made as part of the “push to prod” and display that to end users?
    • When pushing changes to prod – we need to communicate those changes to people.
    • It would be good to have a built-in place to document it so that when we do the push – it displays for users.
    • Obviously, we could build something custom – but I’m thinking more like “Version Notes” where it displays a version number and you can click on it to see what was changed in this version.