Healthcare organizations (HCOs) face mounting pressure to boost operational efficiency, improve health and wellness, and enhance experiences. To drive these outcomes, leaders are aligning enterprise and business goals with digital investments that intelligently automate processes and optimize the health journey.
Clinical intelligence plays a pivotal role in this transformation. It unlocks advanced data-driven insights that enable intelligent healthcare organizations to drive health innovation and elevate impactful health experiences. This approach aligns with the healthcare industry’s quintuple aim to enhance health outcomes, reduce costs, improve patient/member experiences, advance health equity, and improve the work life of healthcare teams.
Our industry experts were recently interviewed by Forrester for their April 2025 report, Clinical Intelligence Will Power The Intelligent Healthcare Organization, which explores ways healthcare and business leaders can transform workflows to propel the enterprise toward next-gen operations and experiences.
We believe the fact that we were interviewed for this report highlights our commitment to optimize technology, interoperability, and digital experiences in ways that build consumer trust, drive innovation, and support more-personalized care.
We combine strategy, industry best practices, and technology expertise to deliver award-winning results for leading health plans and providers:
Every individual brings with them an ever-changing set of needs, preferences, and health conditions. Now more than ever, consumers are flat out demanding a more tailored approach to their health care. This means it is imperative to know your audience. If you do not approach people as individuals with unique, personal needs, you risk losing them to another organization that does.
Becoming an intelligent healthcare organization (IHO) takes more than just a technology investment; it is a complete restructuring of the enterprise to infuse and securely utilize clinical intelligence in every area and interaction.
In its report, Forrester defines an IHO as, “A healthcare organization that perpetually captures, transforms, and delivers data at scale and creates and seamlessly disseminates clinical intelligence, maximizing clinical workflows and operations and the experience of employees and customers. IHOs operate in one connected system that empowers engagement among all stakeholders.”
Ultimately, consumers – as a patient receiving care, a member engaging in their plan’s coverage, or a caregiver supporting this process – want to make and support informed health care decisions that cost-effectively drive better health outcomes. IHOs focus on delivering high-quality, personalized insights and support to the business, care teams, and consumers when it matters most and in ways that are accessible and actionable.
Digital-first care stands at the forefront of transformation, providing more options than ever before as individuals search for and choose care. When digital experiences are orchestrated with consumers’ expectations and options in mind, care solutions like telehealth services, find-care experiences, and mobile health apps can help HCOs deliver the right care at the right time, through the right channel, and with guidance that eases complex decisions, supports proactive health, and activates conversions.
The shift toward digital-first care solutions means it is even more crucial for HCOs to understand real-time consumer expectations to help shape business priorities and form empathetic, personalized experiences that build trust and loyalty.
In its report, Forrester states, “And as consumer trust has taken a hit over the past three years, it is encouraging that 72% of healthcare business and technology professionals expect their organization to increase its investment in customer management technologies.”
Clinical intelligence, leveraged well, can transform the ways that consumers interact and engage across the healthcare ecosystem. IHOs see clinical intelligence as a way to innovate beyond mandated goals to add business value, meet consumers’ evolving expectations, and deliver equitable care and services.
Interoperability plays a crucial role in this process, as it enables more seamless, integrated experiences across all digital platforms and systems. This interconnectedness ensures that consumers receive consistent, coordinated care, regardless of where they are seeking treatment and are supported by informed business and clinical teams.
Mandates such as Health Level 7 (HL7) standards, Fast Healthcare Interoperability Resources (FHIR), and Centers for Medicare & Medicaid Services (CMS) Interoperability and Patient Access Final Rule are creating a more connected and data-driven healthcare ecosystem. Additionally, CMS price transparency regulations are empowering consumers to become more informed, active, and engaged patients. Price transparency and cost estimator tools have the potential to give organizations a competitive edge and drive brand loyalty by providing a transparent, proactive, personalized, and timely experience.
The most successful organizations will build a proper foundation that scales and supports successive mandates. Composable architecture offers a powerful, flexible approach that balances “best in breed,” fit-for-purpose solutions while bypassing unneeded, costly features or services. It’s vital to build trust in data and with consumers, paving the way for ubiquitous, fact-based decision making that supports health and enables relationships across the care continuum.
Success in Action: Empowering Healthcare Consumers and Their Care Ecosystems With Interoperable Data
As the population ages, caregivers play an increasingly important role in the healthcare journey, and their experience is distinct. They may continually move in and out of the caregiver role. It’s essential to understand and engage these vital partners, providing them with important tools and resources to support quality care.
Clinical intelligence can provide HCOs with advanced insights into the needs of caregivers and care teams, helping clinical, operational, IT, digital, and marketing leaders design systems that support the health and efficacy of these important care providers.
Integrated telehealth and remote monitoring have become essential to managing chronic conditions and an aging population. Intuitive, integrated digital tools and personalized messaging can help mitigate potential health barriers by proactively addressing concerns around transportation, costs, medication adherence, appointment scheduling, and more.
A well-planned, well-executed strategy ideally supports access to care for all, creating a healthier and more-welcoming environment for team members to build trust, elevate consumer satisfaction, and drive higher-quality care.
Success in Action: A Digital Approach to Addressing Health Equity
HCO leaders are investing in advanced technologies and automations to modernize operations, streamline experiences, and unlock reliable insights.
Clinical intelligence paired with intelligent automations can accelerate patient and member care for clinical and customer care teams, helping to alleviate stress on a workforce burdened with high rates of burnout.
In its report, Forrester shares, “In Forrester’s Priorities Survey, 2024, 65% or more of healthcare business and technology professionals said that they expect their organization to significantly increase its investments in business insights and analytics, data and information management, AI, and business automation and robotics in the next 12 months.”
It’s clear the U.S. healthcare industry stands on the cusp of a transformative era powered by advanced analytics and holistic business transformation. AI-driven automations can reduce administrative costs, while AI-enabled treatment plans offer hyper-personalized precision medicine. As technology continues to shape healthcare experiences, Felix Bradbury, Perficient senior solutions architect, shares his thoughts on the topic:
“Trust is crucial in healthcare. Understanding how to make AI algorithms interpretable and ensuring they can provide transparent explanations of their decisions will be key to fostering trust among clinicians and patients.”
AI can be a powerful enabler of business priorities. To power and scale effective use cases, HCOs are investing in core building blocks: a modern and secure infrastructure, well-governed data, and team training and enablement. A well-formed strategy that aligns key business needs with people, technology, and processes can turn data into a powerful tool that accelerates operational efficiency and business success, positioning you as an intelligent healthcare organization.
Success in Action: Engaging Diverse Audiences As They Navigate Cancer Care
Discover why we have been trusted by the 10 largest health systems and the 10 largest health insurers in the U.S. Explore our healthcare expertise and contact us to learn more.
]]>There´s no doubt that certifications can speed up and accelerate business growth in many ways. Of course, it´s not the only factor but certainly they play a big part in being a partner-certified consultancy like Perficient is. Certifications provide a reliable technical validation that demonstrates expertise. So, in a competitive market, when a client is looking for a high degree of skill or competence, certifications can contribute as a differentiator in the “big tech ecosystem” showing not only commitment to quality standards but also concern for keeping skills up to date.
In nature, the key to success in ecosystems is the interaction between the parts, linking them to balanced cycles where energy flows and nature flourishes.[1] Technology ecosystems are like natural ones, representing interconnected networks of platforms, applications, developers, partners, and users that collaborate to create greater value than any single part could achieve independently. As in nature, in today’s hyperconnected world, the most successful organizations cannot afford to be isolated. Interaction also is the key to success, leveraged by collaboration, integration and continuous evolution. At Perficient, we know exactly that real impact is always driven through connections among the parts, carefully cultivated to make the difference in the “big tech ecosystem”. Like living ecosystems, we maximize interaction knowing that technology ecosystems outstand whenever they work together so they can thrive on diversity, interdependence, and continuous adaptation.
A fundamental part of tech ecosystems is how expertise is being demonstrated. Certifications whenever they are aligned with business projections excel proficiency, elevating business across multiple dimensions to rocket fuel growth. At Perficient, we champion progress through our commitment to certification investments aligned with our market positioning and target client needs, not only because it represents growth for everyone, but also because it vouches our expertise. So, in this virtuous cycle, every time that a colleague takes a certification, value is added for all the parts in favor of the ecosystem.
As mentioned, certifications have a direct impact in multiple dimensions. They serve as market differentiators for better positioning when clients are evaluating options, highlighting unique advantages that contribute to standing out from competitors. They can also expand service offerings, as the knowledge gained by a certification leverage for new service lines or enhancing ones. Therefore, they open doors to new co-selling opportunities and accelerate sales cycles as capabilities are easy to verify. And if we´re talking about sales, they can definitely improve profit margins. They are also a powerful tool to help colleagues with upskilling and reskilling with a direct impact on their professional development and adaptability to the market, encouraging their willingness to accredit skills, continue learning and evolving with the industry. They boost professional growth, promoting the adherence of best industry practices through standardized methodologies, contributing to career advancement. Consequently, this conducts to operational excellence that has a direct effect on project outcomes creating consistent quality frameworks, reducing implementation variations, streamline solution development processes and rework costs.
Conclusively there´s no doubt that certifications rocket fuel growth for everyone. They play a significant role in tech ecosystems, whenever they are aligned with business projections, demonstrating expertise and acting as differentiators in the “big tech ecosystem”. Certifications not only speed up and accelerate business growth delivering substantial measurable value to clients creating exceptional business results but also have a direct impact on career development for colleagues. So, in the end they´re a win-win for everyone.
]]>As technology continues to advance, patients and care teams expect to seamlessly engage with tools that support better health and accelerate progress. These developments demand the rapid, secure, scalable, and compliant sharing of data.
By aligning enterprise and business goals with digital technology, healthcare organizations (HCOs) can activate strategies for transformative outcomes and improve experiences and efficiencies across the health journey.
Perficient is proud to be included in the categories of IT Services and SI services in the IDC Market Glance: Healthcare Provider Operational IT Solutions, 1Q25 report (doc #US52221325, March 2025). We believe our inclusion in this report’s newly introduced “Services” segmentation underscores our expertise to leverage AI-driven automation and advanced analytics, optimize technology investments, and navigate evolving industry challenges.
IDC states, “This expansion reflects the industry’s shift toward outsourced expertise, scalable service models, and strategic partnerships to manage complex operational IT and infrastructure efficiently.”
IDC defines IT Services as, “managed IT services, ensuring system reliability, cybersecurity, and infrastructure optimization. These solutions support healthcare provider transformation initiatives, helpdesk management, network monitoring, and compliance with healthcare IT regulations.” The SI Services category is defined by IDC as, “system integration services that help deploy technologies and connect disparate systems, including EHRs, RCM platforms, ERP solutions, and third-party applications to enhance interoperability, efficiency, automation, and compliance with industry standards.”
We imagine, engineer, and optimize scalable, reliable technologies and data, partnering with healthcare leaders to better understand consumer expectations and strategically align digital investments with business priorities.
Our end-to-end professional services include:
We don’t just implement solutions; we create intelligent strategies that align technology with your key business priorities and organizational capabilities. Our approach goes beyond traditional data services. We create AI-ready intelligent ecosystems that breathe life into your data strategy and accelerate transformation. By combining technical excellence, global reach, and a client-centric approach, we’re able to drive business transformation, boost operational resilience, and enhance health outcomes.
Success in Action: Illuminating a Clear Path to Care With AI-Enabled Search
Whether you want to redefine workflows, personalize care pathways, or revolutionize proactive health management, Perficient can help you boost efficiencies and a competitive edge.
We combine strategy, industry best practices, and technology expertise to deliver award-winning results for leading health systems:
Discover why we have been trusted by the 10 largest health systems and the 10 largest health insurers in the U.S. Explore our healthcare expertise and contact us to learn more.
]]>If you are a Game of Thrones fan, you are probably familiar with the “winter is coming” phrase. When it comes to Oracle Fusion, the Redwood experience has been coming for years, but now it’s almost here.
Oracle is in the process of overhauling the whole fusion suite with what they call the “Redwood Experience.” The newly designed Redwood pages are not only responsive and more powerful than their ancestors, but they bring great capability to the table.
How to Move Forward with the Redwood Experience
Adopting to Redwood is not a straightforward task. Every quarterly release, Oracle will add more and more pages with the Redwood design, but how do you adopt and take on to the Redwood experience and explore AI opportunities?
User acceptance and adoption comes with time, so the sooner the transition begins, the more successful the implementations will go. Perficient can help you with your transition from traditional Fusion or legacy on-prem applications to the SCM Redwood experience. When you are ready to take the first step and you’re looking for some advice, contact us. Our strategy is to craft a path for our clients that will make the transition as seamless as possible to the user community and their support staff.
New modern looking newly designed Manage Manufacturers Redwood Experience with built-in AI Assist
Below are the Supply Chain features Oracle has released from release 24D to 25B. (2024 Q3- 2025 Q2) only for Inventory Management and yet it is an overwhelming list. Please stay tuned for our Redwood series that will be talking about select features.
Inventory Management |
24D |
Create Guided Journeys for Redwood Pages in the Setup and Maintenance Work Area |
Integrate Manufacturing and Maintenance Direct Work Order Transactions with Your Warehouse Management System |
Redwood: Audit Receipt Accrual Clearing Balances Using a New User Experience |
Redwood: Correct Receipts Using a Redwood Page |
Redwood: Create an Interorganization Transfer Using a Mobile Device |
Redwood: Create and Edit Accrual Cutoff Rules Using a New User Experience |
Redwood: Create Cycle Counts Using a Redwood Page |
Redwood: Create Receipt Returns Using a Redwood Page |
Redwood: Create Unordered Receipts Using a Redwood Page |
Redwood: Inspect Receipts Using a Redwood Page |
Redwood: Inspect Received Goods Using a Mobile Device |
Redwood: Manage Inbound Shipments and Create ASN or ASBN Using a Redwood Page |
Redwood: Review and Clear Open Receipt Accrual Balance Using a New User Experience |
Redwood: Review Receipt Accounting Distributions Using a New User Experience |
Redwood: Review Receipt Accounting Exceptions using a New User Experience |
Redwood: View Item Quantities Using a Redwood Page |
Redwood: View Lot Attributes in Mobile Inventory Transactions |
Redwood: View Receipts and Receipt Returns in Supplier Portal Using a Redwood Page |
Redwood: View the Inventory Management (New) Tile as Inventory Management (Mobile) |
Replenish Locations Using Radio Frequency Identification |
25A |
Capture Recall Notices from the U.S. Food and Drug Administration Curated and Communicated by Oracle |
Collaborate with Notes When Reviewing Open Accrual Balances |
Complete Recall Containment Tasks Bypassing the Recall Count And Disposition |
Create a Flow Manufacturing Work Definition Associated with a Production Line |
Manage Shipping Profile Options |
Redwood: Approve Physical Inventory Adjustments Using a Redwood Page |
Redwood: Compare Standard Costs Using a New User Experience |
Redwood: Create and Update Cost Scenarios Using a New User Experience |
Redwood: Create and Update Standard Costs Using a New User Experience |
Redwood: Create Manual Count Schedules Using a Redwood Page |
Redwood: Create Nudges to Notify Users of Item Shortage and Item Stockout |
Redwood: Define Pull Sequences and Generate Supplier and Intraorganization Kanban Cards |
Redwood: Enhanced Costed BOM Report with Indented View of Lower-Level Subassembly Details |
Redwood: Enter Receipt Quantity by Distribution in the Responsive Self-Service Receiving Application |
Redwood: Manage ABC Classes, Classification Sets, and Assignment Groups Using a Redwood Page |
Redwood: Manage Account Aliases Using a Redwood Page |
Redwood: Manage and Create Physical Inventories Using a Redwood Page |
Redwood: Manage Consigned Inventory Using a Redwood Page |
Redwood: Manage Consumption Rules Using a Redwood Page |
Redwood: Manage Interorganization Parameters Using a Redwood Page |
Redwood: Manage Intersubinventory Parameters Using a Redwood Page |
Redwood: Manage Inventory Transaction Reasons Using a Redwood Page |
Redwood: Manage Lot and Serial Attribute Mappings Using a Redwood Page |
Redwood: Manage Lot Expiration Actions Using a Redwood Page |
Redwood: Manage Lot Grades Using a Redwood Page |
Redwood: Manage Movement Requests Using a Redwood Page |
Redwood: Manage Pick Slip Grouping Rules Using a Redwood Page |
Redwood: Manage Picking Rules and Picking Rule Assignments Using a Redwood Page |
Redwood: Manage Receiving Parameters Using a Redwood Page |
Redwood: Manage Shipment Lines Using a Redwood Page |
Redwood: Manage Shipments Using a Redwood Page |
Redwood: Manage Transfer Orders Using a Redwood Page |
Redwood: Perform Inventory Transactions Directly from Item Quantities |
Redwood: Put Away Receipts Using a Redwood Page |
Redwood: Receive Expected Shipments Using a Redwood Page |
Redwood: Receive Multiple Lines Together in Responsive Self-Service Receiving as a Casual Receiver |
Redwood: Receive Work Order Destination Purchases Using the Responsive Self-Service Receiving Application |
Redwood: Record Physical Inventory Tags Using a Mobile Device |
Redwood: Record Physical Inventory Tags Using a Spreadsheet |
Redwood: Review Completed Transactions Using a Redwood Page |
Redwood: Review Consumption Advices Using a Redwood Page |
Redwood: Review Standard Costs Import Exceptions Using a New User Experience |
Redwood: SCM AI Agents |
Redwood: Search and View Supplier ASN in Receiving |
Redwood: Signal and Track Supplier and Intraorganization Kanban Replenishment |
Redwood: Use Descriptive Flexfields and Attachments in Mobile Inventory |
Redwood: Use Redwood Style in Movement Request Approvals Notification |
Redwood: View Item Supply and Demand Using a Redwood Page |
Redwood: View Rollup Costs Using a New User Experience |
Redwood: View Scenario Exceptions Using a New User Experience |
Summarize and Categorize the Manual Accrual Clearing Transactions for a Period Using Generative AI |
25B |
Analyze Kanban Activity Using Oracle Transactional Business Intelligence and Business Intelligence Cloud Connector |
Define Pull Sequences and Generate Production and Interorganization Kanban Cards |
Define Time Fence to Locate Recalled Parts and Withdraw Irrelevant Recalls |
Implement a Temporary Kanban Card for Short-Term Demand Surge |
Manage and Track Supplier Kanban Cards Through the Supplier Portal |
Receive FYI Notifications when a Recall Notice is Ingested |
Redwood: Accounting Overhead Rules |
Redwood: Analyze Gross Margin |
Redwood: Capture Lot and Serial Numbers with a Streamlined Flow for Mobile Cycle Counting |
Redwood: Confirm Picks Using a Mobile Device with an Improved User Experience |
Redwood: Confirm Picks Using a Redwood Page |
Redwood: Cost Accounting Landing Page |
Redwood: Cost Accounting Periods |
Redwood: Create and Edit Cost Adjustments |
Redwood: Create and Edit Cost Analysis Groups Using a New User Experience |
Redwood: Create and Edit Cost Books Using a New User Experience |
Redwood: Create and Edit Cost Component Mappings Using a New User Experience |
Redwood: Create and Edit Cost Elements Using a New User Experience |
Redwood: Create and Edit Cost Organization Relationships Using a New User Experience |
Redwood: Create and Edit Cost Organizations Using a New User Experience |
Redwood: Create and Edit Cost Profiles Using a New User Experience |
Redwood: Create and Edit Default Cost Profiles Using a New User Experience |
Redwood: Create and Edit Item Cost Profiles Using a New User Experience |
Redwood: Create and Edit Overhead Cost Element Groups Using a New User Experience |
Redwood: Create and Edit Overhead Expense Pools Using a New User Experience |
Redwood: Create and Edit Valuation Structures Using a New User Experience |
Redwood: Create and Edit Valuation Units Using a New User Experience |
Redwood: Create Cost Accounting Distributions |
Redwood: Enter Miscellaneous Transactions on a Mobile Device Using a Streamlined Flow |
Redwood: Implement Cost Accounting Using Quick Setup |
Redwood: Manage Cycle Count Sequences Using a Redwood Page |
Redwood: Manage Default Packing Configurations Using a Redwood Page |
Redwood: Manage Inventory Business Event Configurations Using a Redwood Page |
Redwood: Manage Material Statuses Using a Redwood Page |
Redwood: Manage Pending Transactions Using a Redwood Page |
Redwood: Manage Pick Wave Release Rules Using a Redwood Page |
Redwood: Manage Release Sequence Rules Using a Redwood Page |
Redwood: Manage Reservation Interface Records Using a Spreadsheet |
Redwood: Manage Reservations Using a Redwood Page |
Redwood: Manage Ship Confirm Rules Using a Redwood Page |
Redwood: Manage Shipment Interface Records Using a Spreadsheet |
Redwood: Manage Shipping Cost Types Using a Redwood Page |
Redwood: Manage Shipping Document Job Set Rules Using a Redwood Page |
Redwood: Manage Shipping Document Output Preferences Using a Redwood Page |
Redwood: Manage Shipping Exceptions Using a Redwood Page |
Redwood: Manage Shipping Parameters Using a Redwood Page |
Redwood: Manage Shipping Transaction Correction Records Using a Spreadsheet |
Redwood: Manage Transaction Sources and Types Using a Redwood Page |
Redwood: Manage Transportation Schedules Using a Redwood Page |
Redwood: Manage Units of Measure Usages Using a Redwood Page |
Redwood: Receive Multiple Distribution Purchase Orders on the Expected Shipment Lines and Received Lines Pages |
Redwood: Record PAR Counts on a Mobile Device Using a Streamlined Flow |
Redwood: Review and Approve Item Cost Profiles |
Redwood: Review Consigned Inventory in Supplier Portal Using a Redwood Page |
Redwood: Review Consumption Advice in Supplier Portal Using a Redwood Page |
Redwood: Review Cost Accounting Distributions |
Redwood: Review Cost Accounting Processes |
Redwood: Review Inventory Valuation |
Redwood: Review Item Costs |
Redwood: Review Maintenance Work Order Costs |
Redwood: Review Standard Purchase Cost Variances |
Redwood: Review Work Order Costs |
Redwood: Standard Cost Overhead Absorption Rules |
Redwood: Use a Redwood Template for Automatic Debit Memo Failure Notifications |
Redwood: Use a Redwood Template for Confirm Receipt Notifications |
Redwood: Use a Redwood Template for Create ASN Notifications |
Redwood: Use Additional Pick Slip Grouping Rules Criteria |
Redwood: Use an Improved Experience for Mobile Inventory Transactions |
Redwood: Use Improved Capabilities in the Responsive Self-Service Receiving Application |
Redwood: Use Improved Search Capabilities on Expected Shipment Lines Page |
Redwood: Use Improved Sorting of Source Picking Locations During Pick Confirm |
Redwood: Use Locators on Transfer Orders |
Redwood: Use Saved Searches on Redwood Pages |
Redwood: Use the Improved Inventory Management Landing Page |
Redwood: View Additional Information When Creating a Receipt Using a Mobile Device |
Redwood: View Additional Information When Performing a Subinventory Transfer Using a Mobile Device |
Redwood: View Electronic Records Using a Redwood Page |
]]>
Data Summit 2025 is just around the corner, and we’re excited to connect, learn, and share ideas with fellow leaders in the data and AI space. As the pace of innovation accelerates, events like this offer a unique opportunity to engage with peers, discover groundbreaking solutions, and discuss the future of data-driven transformation.
We caught up with Jerry Locke, a data solutions expert at Perficient, who’s not only attending the event but also taking the stage as a speaker. Here’s what he had to say about this year’s conference and why it matters:
Why is this event important for the data industry?
“Anytime you can meet outside of the screen is always a good thing. For me, it’s all about learning, networking, and inspiration. The world of data is expanding at an unprecedented pace. Global data volume is projected to reach over 180 zettabytes (or 180 trillion gigabytes) by 2025—tripling from just 64 zettabytes in 2020. That’s a massive jump. The question we need to ask is: What are modern organizations doing to not only secure all this data but also use it to unlock new business opportunities? That’s what I’m looking to explore at this summit.”
What topics do you think will be top-of-mind for attendees this year?
“I’m especially interested in the intersection of data engineering and AI. I’ve been lucky to work on modern data teams where we’ve adopted CI/CD pipelines and scalable architectures. AI has completely transformed how we manage data pipelines—mostly for the better. The conversation this year will likely revolve around how to continue that momentum while solving real-world challenges.”
Are there any sessions you’re particularly excited to attend?
“My plan is to soak in as many sessions on data and AI as possible. I’m especially curious about the use cases being shared, how organizations are applying these technologies today, and more importantly, how they plan to evolve them over the next few years.”
What makes this event special for you, personally?
“I’ve never been to this event before, but several of my peers have, and they spoke highly of the experience. Beyond the networking, I’m really looking forward to being inspired by the incredible work others are doing. As a speaker, I’m honored to be presenting on serverless engineering in today’s cloud-first world. I’m hoping to not only share insights but also get thoughtful feedback from the audience and my peers. Ultimately, I want to learn just as much from the people in the room as they might learn from me.”
What’s one thing you hope listeners take away from your presentation?
“My main takeaway is simple: start. If your data isn’t on the cloud yet, start that journey. If your engineering isn’t modernized, begin that process. Serverless is a key part of modern data engineering, but the real goal is enabling fast, informed decision-making through your data. It won’t always be easy—but it will be worth it.
I also hope that listeners understand the importance of composable data systems. If you’re building or working with data systems, composability gives you agility, scalability, and future-proofing. So instead of a big, all-in-one data platform (monolith), you get a flexible architecture where you can plug in best-in-class tools for each part of your data stack. Composable data systems let you choose the best tool for each job, swap out or upgrade parts without rewriting everything, and scale or customize workflows as your needs evolve.”
Don’t miss Perficient at Data Summit 2025. A global digital consultancy, Perficient is committed to partnering with clients to tackle complex business challenges and accelerate transformative growth.
]]>Over the past three years working with Marketing Cloud Personalization (formerly Interaction Studio), I’ve always been intrigued by the Mobile icon and its capabilities. A few months ago, I decided to take a hands-on approach by developing my own application to explore this functionality firsthand, testing its implementation and understanding its real-world impact. And that is what this blog is about.
The overall steps of the Marketing Cloud Personalization Mobile integration goes as follows:
That’s all… easy right?. Within this blog we will review how to do the connection between MCP and the mobile app and how to create a first interaction (steps 1 and part of step 6).
For this demo, I developed an iOS application using the Swift programming language. While I’m not yet an expert, I’ve been steadily learning how to navigate Xcode and implement functionality using Swift. This project has been a great opportunity to expand my skills in iOS development and better understand the tools and frameworks available within Apple’s ecosystem.
The iOS app I create is very simple (for now), it just a label, a button and an input field. The user types something in the input field, then clicks the button and the data is sent to the label to be shown.
So, we need to add the Evergage SDK inside the app project. Download the Evergage iOS SDK (v1.4.1), unzip it and open the static folder. There, the Evergage.xcframework is the one we are about to use. When you have the folder ready, you need to copy the folder into your app. You should have something like this:
After you added your folder, you need to Build your app again with Command + B.
Now we need to validate the framework is there, so go to Target -> General -> Frameworks, Libraries and Embedded Content. You should see something like this, and since I’m using the static folder, the Do Not Embed is ok.
Validate the Framework Search Path contains a path where the framework was copied/installed. This step would probably be done manually since sometimes the path doesn’t appear. Build the app again to validate if no errors appears.
To validate this works, go to the AppDelegate.swift and type Import Evergage, if no errors appear, you are good to go
Next, we have to create the Native App inside the Personalization dataset of your choice.
Hoover over Mobile and click Add Native App
Fill the information of the App Name and Bundle ID. For the Bundle ID, go to Target > General > Identity
You will with something like this:
In the AppDelegate.swift , we will do the equivalent to add the JavaScript beacon on the page.
Evergage
class reference. This allow the start of the Marketing Cloud Personalization iOS SDK. Our tracking interactions now should be done inside a UIViewController
inherited classes.didFinishLaunchingWithOptions
to willFinishLaounchingWithOptions
application
function we do the following:
evergage.userId
using the evergage.anonymousId
, but if we already have the email or an id for the user, we should passed right away.usePushNotifications
and the useDesignMode
. The last one help us to connect the Personalization web console for action mapping screen.
//Other imports Import Evergage @main class AppDelegate: UIResponder, UIApplicationDelegate { func application(_ application: UIApplication, willFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool{ //Create an singleton instance of Evergage let evergage = Evergage.sharedInstance() //Set User ID as anonymous evergage.userId = evergage.anonymousId //Start the Evergage Configuration with our Dataset information evergage.start { (clientConfigurationBuilder) in clientConfigurationBuilder.account = "ACCOUNT_ID" clientConfigurationBuilder.dataset = "DATASET_ID" // if we want to user push notification campaings clientConfigurationBuilder.usePushNotifications = true //Allow user-initiated gesture to connect to the Personalization web console for action mapping screens. clientConfigurationBuilder.useDesignMode = true } // Override point for customization after application launch. return true } }
If we launch the app at this very moment, we will get the following inside Marketing Cloud personalization
This is very good and with that we are certain its working and sending the information to Marketing Cloud Personalization.
So, in order to track a screen we can use the evergageScreen
. We use this property as part of the EVGScreen
and EVGContext
classes for tracking and personalization. This is possible when the app is using UIViewController
for each of the screens or pages we have.
class ViewController: UIViewController { override func viewDidLoad() { super.viewDidLoad() // Do any additional setup after loading the view. trackScreen() } func trackScreen(){ evergageScreen?.trackAction("Main Screen") } }
If we would want to track the action of click a button, we can do something similar, for example this:
@IBAction func handleClick(_ sender: UIButton) { labelText.text = inputField.text evergageScreen?.trackAction("Button clicked") }
In this code, each time the user clicks a button, the handleClick function will trigger the action. the inputField.text will be assign to the labelText.text and the trackAction function will be triggered and the action will sent to our dataset.
That wraps up the first part of this tutorial! We’ve covered the basic about how to add the Personalization SDK inside a mobile iOS application, how to create a Mobile App within Personalization and do a very basic action tracking in a view. In Part 2, we’ll dive into tracking more complex actions like view item and view item detail which are part of the catalog object action’s for tracking items.
]]>Isn’t SFO an airport? The airport one would travel if the destination is Oracle’s Redwood Shores campus. Widely known as the initialism for the San Francisco International Airport, the answer would be correct if this question were posed in that context. However, in Oracle Fusion, SFO stands for the Supply Chain Financial Orchestration. Based on what it does, we cannot call it an airport, but it sure is a control tower for financial transactions.
As companies are expanding their presence across countries and continents through mergers and acquisitions or natural growth, it becomes inevitable for the companies to transact across the borders and produce intercompany financial transactions.
Supply Chain Financial Orchestration (SFO), is the place where Oracle Fusion handles those transactions. The material may move one way, but for legal or financial reasons the financial flow could be following a different path.
A Typical Scenario
A Germany-based company sells to its EU customers from its Berlin office, but ships from its warehouses in New Delhi and Beijing.
Oracle Fusion SFO takes care of all those transactions and as transactions are processed in Cost Management, financial trade transactions are created, and corporations can see their internal margins, intercompany accounting, and intercompany invoices.
Oh wait, the financial orchestration doesn’t have to be across countries only. What if a corporation wants to measure its manufacturing and sales operations profitability? Supply Chain Financial Orchestration is there for you.
In short, SFO is a tool that is part of the Supply Chain management offering that helps create intercompany trade transactions for various business cases.
Contact Mehmet Erisen at Perficient for more introspection of this functionality, and how Perficient and Oracle Fusion Cloud can digitalize and modernize your ERP platform.
www.oracle.com
www.perficient.com
]]>Replaced disparate and outdated legacy systems with Oracle Fusion Cloud Manufacturing at a well-established manufacturing company. We implemented a scalable Fusion solution, including Project Driven Supply Chain (PDSC), and full Financial and Supply Chain Management Suites to enable Roeslein to execute and extend their business processes globally.
The challenge in manufacturing was to set standard manufacturing processes to fulfill highly customized demand originating from their customers. In addition, Perficient designed a Supply Chain Data Architecture to support the functionality of the solution.
Contact Mehmet Erisen at Perficient for more introspection of this phenomenal achievement. Congratulations to Roeslein & Associates and their entire staff!
]]>TLS certificate lifetimes are being significantly reduced over the next few years as part of an industry-wide push toward greater security and automation. Here’s the phased timeline currently in place:
Now through March 15, 2026: Maximum lifetime is 398 days
Starting March 15, 2026: Reduced to 200 days
Starting March 15, 2027: Further reduced to 100 days
Starting March 15, 2029: Reduced again to just 47 days
For teams managing Sitecore implementations, this is more than a policy shift—it introduces operational urgency. As certificates begin expiring more frequently, any reliance on manual tracking or last-minute renewals could result in costly downtime or broken integrations.
If your Sitecore environment includes secure endpoints, custom domains, or external integrations, now is the time to assess your certificate strategy and move toward automation.
Sitecore projects often involve:
Multiple environments (development, staging, production) with different certificates
Custom domains or subdomains used for CDNs, APIs, headless apps, or marketing campaigns
Third-party integrations that require secure connections
Marketing and personalization features that rely on seamless uptime
A single expired certificate can lead to downtime, loss of customer trust, or failed integrations—any of which could severely impact your digital experience delivery.
Increased risk of missed renewals if teams rely on manual tracking
Broken environments due to expired certs in Azure, IIS, or Kubernetes configurations
Delayed deployments when certificates must be re-issued last minute
SEO and trust damage if browsers start flagging your site as insecure
To stay ahead of the TLS certificate lifecycle changes, here are concrete steps you should take:
Audit all environments and domains using certificates
Include internal services, custom endpoints, and non-production domains
Use a centralized tracking tool (e.g., Azure Key Vault, HashiCorp Vault, or a certificate management platform)
Wherever possible, switch to automated certificate issuance and renewal
Use services like:
Azure App Service Managed Certificates
Let’s Encrypt with automation scripts
ACME protocol integrations for Kubernetes
For Azure-hosted Sitecore instances, leverage Key Vault and App Gateway integrations
Assign clear ownership of certificate management per environment or domain
Document who is responsible for renewals and updates
Add certificate health checks to your DevOps dashboards
Validate certificate validity before deployments
Fail builds if certificates are nearing expiration
Include certificate management tasks as part of environment provisioning
Hold knowledge-sharing sessions with developers, infrastructure engineers, and marketers
Make sure everyone understands the impact of expired certificates on the Sitecore experience
Simulate certificate expiry in non-production environments
Monitor behavior in Sitecore XP and XM environments, including CD and CM roles
Validate external systems (e.g., CDNs, integrations, identity providers) against cert failures
TLS certificate management is no longer a “set it and forget it” task. With shorter lifetimes becoming the norm, proactive planning is essential to avoid downtime and ensure secure, uninterrupted experiences for your users.
Start by auditing your current certificates and work toward automating renewals. Make certificate monitoring part of your DevOps practice, and ensure your Sitecore teams are aware of the upcoming changes.
Action Items for This Week:
Identify all TLS certificates in your Sitecore environments
Document renewal dates and responsible owners
Begin automating renewals for at least one domain
Review Azure and Sitecore documentation for certificate integration options
Securing your Sitecore XM Cloud environment is critical to protecting your content, your users, and your brand. This post walks through key areas of XM Cloud security, including user management, authentication, secure coding, and best practices you can implement today to reduce your security risks.
We’ll also take a step back to look at the Sitecore Cloud Portal—the central control panel for managing user access across your Sitecore organization. Understanding both the Cloud Portal and XM Cloud’s internal security tools is essential for building a strong foundation of security.
The Sitecore Cloud Portal is the gateway to managing user access across all Sitecore DXP tools, including XM Cloud. Proper setup here ensures that only the right people can view or change your environments and content.
Each user you invite to your Sitecore organization is assigned an Organization Role, which defines their overall access level:
Organization Owner – Full control over the organization, including user and app management.
Organization Admin – Can manage users and assign app access, but cannot assign/remove Owners.
Organization User – Limited access; can only use specific apps they’ve been assigned to.
Tip: Assign the “Owner” role sparingly—only to those who absolutely need full administrative control.
Beyond organization roles, users are granted App Roles for specific products like XM Cloud. These roles determine what actions they can take inside each product:
Admin – Full access to all features of the application.
User – More limited, often focused on content authoring or reviewing.
From the Admin section of the Cloud Portal, Organization Owners or Admins can:
Invite new team members and assign roles.
Grant access to apps like XM Cloud and assign appropriate app-level roles.
Review and update roles as team responsibilities shift.
Remove access when team members leave or change roles.
Security Tips:
Review user access regularly.
Use the least privilege principle—only grant what’s necessary.
Enable Multi-Factor Authentication (MFA) and integrate Single Sign-On (SSO) for extra protection.
Within XM Cloud itself, there’s another layer of user and role management that governs access to content and features.
Users: Individual accounts representing people who work in the XM Cloud instance.
Roles: Collections of users with shared permissions.
Domains: Logical groupings of users and roles, useful for managing access in larger organizations.
Recommendation: Don’t assign permissions directly to users—assign them to roles instead for easier management.
Permissions can be set at the item level for things like reading, writing, deleting, or publishing. Access rights include:
Read
Write
Create
Delete
Administer
Each right can be set to:
Allow
Deny
Inherit
Follow the Role-Based Access Control (RBAC) model.
Create custom roles to reflect your team’s structure and responsibilities.
Audit roles and access regularly to prevent privilege creep.
Avoid modifying default system users—create new accounts instead.
XM Cloud supports robust authentication mechanisms to control access between services, deployments, and repositories.
When integrating external services or deploying via CI/CD, you’ll often need to authenticate through client credentials.
Use the Sitecore Cloud Portal to create and manage client credentials.
Grant only the necessary scopes (permissions) to each credential.
Rotate credentials periodically and revoke unused ones.
Use secure secrets management tools to store client IDs and secrets outside of source code.
For Git and deployment pipelines, connect XM Cloud environments to your repository using secure tokens and limit access to specific environments or branches when possible.
Security isn’t just about who has access—it’s also about how your code and data behave in production.
Sanitize all inputs to prevent injection attacks.
Avoid exposing sensitive information in logs or error messages.
Use HTTPS for all external communications.
Validate data both on the client and server sides.
Keep dependencies up to date and monitor for vulnerabilities.
When using visitor data for personalization, be transparent and follow data privacy best practices:
Explicitly define what data is collected and how it’s used.
Give visitors control over their data preferences.
Avoid storing personally identifiable information (PII) unless absolutely necessary.
Securing your XM Cloud environment is an ongoing process that involves team coordination, regular reviews, and constant vigilance. Here’s how to get started:
Audit your Cloud Portal roles and remove unnecessary access.
Establish a role-based structure in XM Cloud and limit direct user permissions.
Implement secure credential management for deployments and integrations.
Train your developers on secure coding and privacy best practices.
]]>The stronger your security practices, the more confidence you—and your clients—can have in your digital experience platform.
Our trusted Unified Commerce Platform partner, Kibo, is gearing up to host the Kibo Connect Client Summit from May 7th to 9th at the Loews Downtown Chicago Hotel. Since the start of our partnership in 2021, Kibo has consistently delivered success through innovative commerce and delivery models, a dynamic omnichannel pricing and promotions engine, and robust delivery options seamlessly integrated into its user-friendly interface. This upcoming summit promises to bring together industry leaders, innovators, and experts to exchange valuable insights, strategies, and success stories from the world of commerce.
The event offers plenty of networking opportunities, with more than 200 executives and industry experts in attendance. Key figures like CTOs and SVPs from renowned businesses such as Total Wine & More, Forrester, and Ace Hardware will be among those contributing thought leadership on stage. Adding to the lineup, our very own Zach Zalowitz, Principal of Order Management and Product Information Management, and Kim Glasscock, Director of Order Management, will represent us at the summit.
Expect a wealth of strategic discussions on the latest practices in commerce, order management, and customer experience. One must-attend session is the panel ‘The Future of Commerce: Navigating Disruption and Driving Innovation,’ featuring Zach Zalowitz alongside prominent leaders from ODP and Proactiv. The panel discussion takes place on Thursday, May 8th, at 2:00 PM.
Additionally, attendees will have the chance to gain actionable insights by participating in various workshops and sessions led by global brands and technology providers.
We’re thrilled to be part of the Kibo Connect Client Summit and look forward to seeing you there. Attendees can expect some exciting surprises from us at the event, whether it’s inspiration from the main stage or insightful conversations at our partner table. As we countdown to May, stay tuned for more updates and information.
Explore our commerce expertise in and in your industry as we prepare to connect, and contact us if you’re ready to schedule time for a discussion at the event.
]]>
This guide will walk you through building a small application step-by-step, focusing on integrating several powerful tools and concepts essential for modern Android development.
The Goal: Build a “Task Reporter” app. Users can add simple task descriptions. These tasks are saved to Firestore. A background worker will periodically “report” (log a message or update a counter in Firestore) that the app is active. We’ll have dev
and prod
flavors pointing to different Firestore collections/data and distribute the dev
build for testing.
Let’s get started!
AdvancedConceptsApp
(or your choice).com.yourcompany.advancedconceptsapp
).build.gradle.kts
).build.gradle.kts
(or build.gradle
) files. This adds the necessary dependencies.google-services.json
:
com.yourcompany.advancedconceptsapp
) is registered. If not, add it.google-services.json
file.app/
directory.Let’s create a simple UI to add and display tasks.
app/build.gradle.kts
.
dependencies {
// Core & Lifecycle & Activity
implementation("androidx.core:core-ktx:1.13.1") // Use latest versions
implementation("androidx.lifecycle:lifecycle-runtime-ktx:2.8.1")
implementation("androidx.activity:activity-compose:1.9.0")
// Compose
implementation(platform("androidx.compose:compose-bom:2024.04.01")) // Check latest BOM
implementation("androidx.compose.ui:ui")
implementation("androidx.compose.ui:ui-graphics")
implementation("androidx.compose.ui:ui-tooling-preview")
implementation("androidx.compose.material3:material3")
implementation("androidx.lifecycle:lifecycle-viewmodel-compose:2.8.1")
// Firebase
implementation(platform("com.google.firebase:firebase-bom:33.0.0")) // Check latest BOM
implementation("com.google.firebase:firebase-firestore-ktx")
// WorkManager
implementation("androidx.work:work-runtime-ktx:2.9.0") // Check latest version
}
Sync Gradle files.
data/Task.kt
.
package com.yourcompany.advancedconceptsapp.data
import com.google.firebase.firestore.DocumentId
data class Task(
@DocumentId
val id: String = "",
val description: String = "",
val timestamp: Long = System.currentTimeMillis()
) {
constructor() : this("", "", 0L) // Firestore requires a no-arg constructor
}
ui/TaskViewModel.kt
. (We’ll update the collection name later).
package com.yourcompany.advancedconceptsapp.ui
import androidx.lifecycle.ViewModel
import androidx.lifecycle.viewModelScope
import com.google.firebase.firestore.ktx.firestore
import com.google.firebase.firestore.ktx.toObjects
import com.google.firebase.ktx.Firebase
import com.yourcompany.advancedconceptsapp.data.Task
// Import BuildConfig later when needed
import kotlinx.coroutines.flow.MutableStateFlow
import kotlinx.coroutines.flow.StateFlow
import kotlinx.coroutines.launch
import kotlinx.coroutines.tasks.await
// Temporary placeholder - will be replaced by BuildConfig field
const val TEMPORARY_TASKS_COLLECTION = "tasks"
class TaskViewModel : ViewModel() {
private val db = Firebase.firestore
// Use temporary constant for now
private val tasksCollection = db.collection(TEMPORARY_TASKS_COLLECTION)
private val _tasks = MutableStateFlow<List<Task>>(emptyList())
val tasks: StateFlow<List<Task>> = _tasks
private val _error = MutableStateFlow<String?>(null)
val error: StateFlow<String?> = _error
init {
loadTasks()
}
fun loadTasks() {
viewModelScope.launch {
try {
tasksCollection.orderBy("timestamp", com.google.firebase.firestore.Query.Direction.DESCENDING)
.addSnapshotListener { snapshots, e ->
if (e != null) {
_error.value = "Error listening: ${e.localizedMessage}"
return@addSnapshotListener
}
_tasks.value = snapshots?.toObjects<Task>() ?: emptyList()
_error.value = null
}
} catch (e: Exception) {
_error.value = "Error loading: ${e.localizedMessage}"
}
}
}
fun addTask(description: String) {
if (description.isBlank()) {
_error.value = "Task description cannot be empty."
return
}
viewModelScope.launch {
try {
val task = Task(description = description, timestamp = System.currentTimeMillis())
tasksCollection.add(task).await()
_error.value = null
} catch (e: Exception) {
_error.value = "Error adding: ${e.localizedMessage}"
}
}
}
}
ui/TaskScreen.kt
.
package com.yourcompany.advancedconceptsapp.ui
// Imports: androidx.compose.*, androidx.lifecycle.viewmodel.compose.viewModel, java.text.SimpleDateFormat, etc.
import androidx.compose.foundation.layout.*
import androidx.compose.foundation.lazy.LazyColumn
import androidx.compose.foundation.lazy.items
import androidx.compose.material3.*
import androidx.compose.runtime.*
import androidx.compose.ui.Alignment
import androidx.compose.ui.Modifier
import androidx.compose.ui.unit.dp
import androidx.lifecycle.viewmodel.compose.viewModel
import com.yourcompany.advancedconceptsapp.data.Task
import java.text.SimpleDateFormat
import java.util.Date
import java.util.Locale
import androidx.compose.ui.res.stringResource
import com.yourcompany.advancedconceptsapp.R // Import R class
@OptIn(ExperimentalMaterial3Api::class) // For TopAppBar
@Composable
fun TaskScreen(taskViewModel: TaskViewModel = viewModel()) {
val tasks by taskViewModel.tasks.collectAsState()
val errorMessage by taskViewModel.error.collectAsState()
var taskDescription by remember { mutableStateOf("") }
Scaffold(
topBar = {
TopAppBar(title = { Text(stringResource(id = R.string.app_name)) }) // Use resource for flavor changes
}
) { paddingValues ->
Column(modifier = Modifier.padding(paddingValues).padding(16.dp).fillMaxSize()) {
// Input Row
Row(verticalAlignment = Alignment.CenterVertically, modifier = Modifier.fillMaxWidth()) {
OutlinedTextField(
value = taskDescription,
onValueChange = { taskDescription = it },
label = { Text("New Task Description") },
modifier = Modifier.weight(1f),
singleLine = true
)
Spacer(modifier = Modifier.width(8.dp))
Button(onClick = {
taskViewModel.addTask(taskDescription)
taskDescription = ""
}) { Text("Add") }
}
Spacer(modifier = Modifier.height(16.dp))
// Error Message
errorMessage?.let { Text(it, color = MaterialTheme.colorScheme.error, modifier = Modifier.padding(bottom = 8.dp)) }
// Task List
if (tasks.isEmpty() && errorMessage == null) {
Text("No tasks yet. Add one!")
} else {
LazyColumn(modifier = Modifier.weight(1f)) {
items(tasks, key = { it.id }) { task ->
TaskItem(task)
Divider()
}
}
}
}
}
}
@Composable
fun TaskItem(task: Task) {
val dateFormat = remember { SimpleDateFormat("yyyy-MM-dd HH:mm", Locale.getDefault()) }
Row(modifier = Modifier.fillMaxWidth().padding(vertical = 8.dp), verticalAlignment = Alignment.CenterVertically) {
Column(modifier = Modifier.weight(1f)) {
Text(task.description, style = MaterialTheme.typography.bodyLarge)
Text("Added: ${dateFormat.format(Date(task.timestamp))}", style = MaterialTheme.typography.bodySmall)
}
}
}
MainActivity.kt
: Set the content to TaskScreen
.
package com.yourcompany.advancedconceptsapp
import android.os.Bundle
import androidx.activity.ComponentActivity
import androidx.activity.compose.setContent
import androidx.compose.foundation.layout.fillMaxSize
import androidx.compose.material3.MaterialTheme
import androidx.compose.material3.Surface
import androidx.compose.ui.Modifier
import com.yourcompany.advancedconceptsapp.ui.TaskScreen
import com.yourcompany.advancedconceptsapp.ui.theme.AdvancedConceptsAppTheme
// Imports for WorkManager scheduling will be added in Step 3
class MainActivity : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContent {
AdvancedConceptsAppTheme {
Surface(modifier = Modifier.fillMaxSize(), color = MaterialTheme.colorScheme.background) {
TaskScreen()
}
}
}
// TODO: Schedule WorkManager job in Step 3
}
}
Create a background worker for periodic reporting.
worker/ReportingWorker.kt
. (Collection name will be updated later).
package com.yourcompany.advancedconceptsapp.worker
import android.content.Context
import android.util.Log
import androidx.work.CoroutineWorker
import androidx.work.WorkerParameters
import com.google.firebase.firestore.ktx.firestore
import com.google.firebase.ktx.Firebase
// Import BuildConfig later when needed
import kotlinx.coroutines.tasks.await
// Temporary placeholder - will be replaced by BuildConfig field
const val TEMPORARY_USAGE_LOG_COLLECTION = "usage_logs"
class ReportingWorker(appContext: Context, workerParams: WorkerParameters) :
CoroutineWorker(appContext, workerParams) {
companion object { const val TAG = "ReportingWorker" }
private val db = Firebase.firestore
override suspend fun doWork(): Result {
Log.d(TAG, "Worker started: Reporting usage.")
return try {
val logEntry = hashMapOf(
"timestamp" to System.currentTimeMillis(),
"message" to "App usage report.",
"worker_run_id" to id.toString()
)
// Use temporary constant for now
db.collection(TEMPORARY_USAGE_LOG_COLLECTION).add(logEntry).await()
Log.d(TAG, "Worker finished successfully.")
Result.success()
} catch (e: Exception) {
Log.e(TAG, "Worker failed", e)
Result.failure()
}
}
}
MainActivity.kt
‘s onCreate
method.
// Add these imports to MainActivity.kt
import android.content.Context
import android.util.Log
import androidx.work.*
import com.yourcompany.advancedconceptsapp.worker.ReportingWorker
import java.util.concurrent.TimeUnit
// Inside MainActivity class, after setContent { ... } block in onCreate
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContent {
// ... existing code ...
}
// Schedule the worker
schedulePeriodicUsageReport(this)
}
// Add this function to MainActivity class
private fun schedulePeriodicUsageReport(context: Context) {
val constraints = Constraints.Builder()
.setRequiredNetworkType(NetworkType.CONNECTED)
.build()
val reportingWorkRequest = PeriodicWorkRequestBuilder<ReportingWorker>(
1, TimeUnit.HOURS // ~ every hour
)
.setConstraints(constraints)
.addTag(ReportingWorker.TAG)
.build()
WorkManager.getInstance(context).enqueueUniquePeriodicWork(
ReportingWorker.TAG,
ExistingPeriodicWorkPolicy.KEEP,
reportingWorkRequest
)
Log.d("MainActivity", "Periodic reporting work scheduled.")
}
ReportingWorker
and MainActivity
about scheduling.com.yourcompany.advancedconceptsapp
adb shell cmd jobscheduler run -f com.yourcompany.advancedconceptsapp 999
(The 999 is usually sufficient, it’s a job ID).usage_logs
collection.Create dev
and prod
flavors for different environments.
app/build.gradle.kts
:
android {
// ... namespace, compileSdk, defaultConfig ...
// ****** Enable BuildConfig generation ******
buildFeatures {
buildConfig = true
}
// *******************************************
flavorDimensions += "environment"
productFlavors {
create("dev") {
dimension = "environment"
applicationIdSuffix = ".dev" // CRITICAL: Changes package name for dev builds
versionNameSuffix = "-dev"
resValue("string", "app_name", "Task Reporter (Dev)")
buildConfigField("String", "TASKS_COLLECTION", "\"tasks_dev\"")
buildConfigField("String", "USAGE_LOG_COLLECTION", "\"usage_logs_dev\"")
}
create("prod") {
dimension = "environment"
resValue("string", "app_name", "Task Reporter")
buildConfigField("String", "TASKS_COLLECTION", "\"tasks\"")
buildConfigField("String", "USAGE_LOG_COLLECTION", "\"usage_logs\"")
}
}
// ... buildTypes, compileOptions, etc ...
}
Sync Gradle files.
applicationIdSuffix = ".dev"
. This means the actual package name for your development builds will become something like com.yourcompany.advancedconceptsapp.dev
. This requires an update to your Firebase project setup, explained next. Also note the buildFeatures { buildConfig = true }
block which is required to use buildConfigField
.Because the `dev` flavor now has a different application ID (`…advancedconceptsapp.dev`), the original `google-services.json` file (downloaded in Step 1) will not work for `dev` builds, causing a “No matching client found” error during build.
You must add this new Application ID to your Firebase project:
com.yourcompany.advancedconceptsapp.dev
(replace `com.yourcompany.advancedconceptsapp` with your actual base package name).google-services.json
file offered. This file now contains configurations for BOTH your base ID and the `.dev` suffixed ID.google-services.json
from the app/
directory and replace it with the **newly downloaded** one.app/src
-> New -> Directory. Name it dev
.dev
, create res/values/
directories.app/src
-> New -> Directory. Name it prod
.prod
, create res/values/
directories.app_name
string definition from app/src/main/res/values/strings.xml
into both app/src/dev/res/values/strings.xml
and app/src/prod/res/values/strings.xml
. Or, you can rely solely on the resValue
definitions in Gradle (as done above). Using resValue
is often simpler for single strings like app_name
. If you had many different resources (layouts, drawables), you’d put them in the respective dev/res
or prod/res
folders.TaskViewModel.kt
and ReportingWorker.kt
to use BuildConfig
instead of temporary constants.TaskViewModel.kt change
// Add this import
import com.yourcompany.advancedconceptsapp.BuildConfig
// Replace the temporary constant usage
// const val TEMPORARY_TASKS_COLLECTION = "tasks" // Remove this line
private val tasksCollection = db.collection(BuildConfig.TASKS_COLLECTION) // Use build config field
ReportingWorker.kt change
// Add this import
import com.yourcompany.advancedconceptsapp.BuildConfig
// Replace the temporary constant usage
// const val TEMPORARY_USAGE_LOG_COLLECTION = "usage_logs" // Remove this line
// ... inside doWork() ...
db.collection(BuildConfig.USAGE_LOG_COLLECTION).add(logEntry).await() // Use build config field
Modify TaskScreen.kt
to potentially use the flavor-specific app name (though resValue
handles this automatically if you referenced @string/app_name
correctly, which TopAppBar
usually does). If you set the title directly, you would load it from resources:
// In TaskScreen.kt (if needed)
import androidx.compose.ui.res.stringResource
import com.yourcompany.advancedconceptsapp.R // Import R class
// Inside Scaffold -> topBar
TopAppBar(title = { Text(stringResource(id = R.string.app_name)) }) // Use string resource
devDebug
, devRelease
, prodDebug
, and prodRelease
.devDebug
. Run the app. The title should say “Task Reporter (Dev)”. Data should go to tasks_dev
and usage_logs_dev
in Firestore.prodDebug
. Run the app. The title should be “Task Reporter”. Data should go to tasks
and usage_logs
.R8 is the default code shrinker and obfuscator in Android Studio (successor to Proguard). It’s enabled by default for release
build types. We need to ensure it doesn’t break our app, especially Firestore data mapping.
app/build.gradle.kts
Release Build Type:
android {
// ...
buildTypes {
release {
isMinifyEnabled = true // Should be true by default for release
isShrinkResources = true // R8 handles both
proguardFiles(
getDefaultProguardFile("proguard-android-optimize.txt"),
"proguard-rules.pro" // Our custom rules file
)
}
debug {
isMinifyEnabled = false // Usually false for debug
proguardFiles(
getDefaultProguardFile("proguard-android-optimize.txt"),
"proguard-rules.pro"
)
}
// ... debug build type ...
}
// ...
}
isMinifyEnabled = true
enables R8 for the release
build type.
app/proguard-rules.pro
:
app/proguard-rules.pro
file. Add the following:
# Keep Task data class and its members for Firestore serialization
-keep class com.yourcompany.advancedconceptsapp.data.Task { (...); *; }
# Keep any other data classes used with Firestore similarly
# -keep class com.yourcompany.advancedconceptsapp.data.AnotherFirestoreModel { (...); *; }
# Keep Coroutine builders and intrinsics (often needed, though AGP/R8 handle some automatically)
-keepnames class kotlinx.coroutines.intrinsics.** { *; }
# Keep companion objects for Workers if needed (sometimes R8 removes them)
-keepclassmembers class * extends androidx.work.Worker {
public static ** Companion;
}
# Keep specific fields/methods if using reflection elsewhere
# -keepclassmembers class com.example.SomeClass {
# private java.lang.String someField;
# public void someMethod();
# }
# Add rules for any other libraries that require them (e.g., Retrofit, Gson, etc.)
# Consult library documentation for necessary Proguard/R8 rules.
-keep class ... { <init>(...); *; }
: Keeps the Task
class, its constructors (<init>
), and all its fields/methods (*
) from being removed or renamed. This is crucial for Firestore.-keepnames
: Prevents renaming but allows removal if unused.-keepclassmembers
: Keeps specific members within a class.3. Test the Release Build:
prodRelease
build variant.prodRelease
as the variant. Click Finish.app/prod/release/
).adb install app-prod-release.apk
.usage_logs
)? If it crashes or data doesn’t save/load correctly, R8 likely removed something important. Check Logcat for errors (often ClassNotFoundException
or NoSuchMethodError
) and adjust your proguard-rules.pro
file accordingly.
Configure Gradle to upload development builds to testers via Firebase App Distribution.
api-project-xxx-yyy.json
move this file to root project at the same level of app folder *Ensure that this file be in your local app, do not push it to the remote repository because it contains sensible data and will be rejected later
app/build.gradle.kts
:
// Apply the plugin at the top
plugins {
// ... other plugins id("com.android.application"), id("kotlin-android"), etc.
alias(libs.plugins.google.firebase.appdistribution)
}
android {
// ... buildFeatures, flavorDimensions, productFlavors ...
buildTypes {
getByName("release") {
isMinifyEnabled = true // Should be true by default for release
isShrinkResources = true // R8 handles both
proguardFiles(
getDefaultProguardFile("proguard-android-optimize.txt"),
"proguard-rules.pro" // Our custom rules file
)
}
getByName("debug") {
isMinifyEnabled = false // Usually false for debug
proguardFiles(
getDefaultProguardFile("proguard-android-optimize.txt"),
"proguard-rules.pro"
)
}
firebaseAppDistribution {
artifactType = "APK"
releaseNotes = "Latest build with fixes/features"
testers = "briew@example.com, bri@example.com, cal@example.com"
serviceCredentialsFile="$rootDir/api-project-xxx-yyy.json
"//do not push this line to the remote repository or stablish as local variable } } }
Add library version to libs.version.toml
[versions]
googleFirebaseAppdistribution = "5.1.1"
[plugins]
google-firebase-appdistribution = { id = "com.google.firebase.appdistribution", version.ref = "googleFirebaseAppdistribution" }
Ensure the plugin classpath is in the
project-level
build.gradle.kts
:
project build.gradle.kts
plugins {
// ...
alias(libs.plugins.google.firebase.appdistribution) apply false
}
Sync Gradle files.
devDebug
, devRelease
, prodDebug
, prodRelease
)../gradlew assembleRelease appDistributionUploadProdRelease
./gradlew assembleRelease appDistributionUploadDevRelease
./gradlew assembleDebug appDistributionUploadProdDebug
./gradlew assembleDebug appDistributionUploadDevDebug
Automate building and distributing the `dev` build on push to a specific branch.
api-project-xxx-yyy.json
located at root project and copy the content.github/workflows/
..github/workflows/
, create a new file named android_build_distribute.yml
.
name: Android CI
on:
push:
branches: [ "main" ]
pull_request:
branches: [ "main" ]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: set up JDK 17
uses: actions/setup-java@v3
with:
java-version: '17'
distribution: 'temurin'
cache: gradle
- name: Grant execute permission for gradlew
run: chmod +x ./gradlew
- name: Build devRelease APK
run: ./gradlew assembleRelease
- name: upload artifact to Firebase App Distribution
uses: wzieba/Firebase-Distribution-Github-Action@v1
with:
appId: ${{ secrets.FIREBASE_APP_ID }}
serviceCredentialsFileContent: ${{ secrets.FIREBASE_SERVICE_ACCOUNT_KEY_JSON }}
groups: testers
file: app/build/outputs/apk/dev/release/app-dev-release-unsigned.apk
.github/workflows/android_build_distribute.yml
file and push it to your main
branch on GitHub.
devDebug
and prodDebug
in Android Studio. Verify the app name changes and data goes to the correct Firestore collections (tasks_dev
/tasks
, usage_logs_dev
/usage_logs
).ReportingWorker
runs periodically and logs data to the correct Firestore collection based on the selected flavor.prodRelease
APK manually. Ensure all features work, especially adding/viewing tasks (Firestore interaction). Check Logcat for crashes related to missing classes/methods.devDebug
(or devRelease
) builds uploaded manually or via CI/CD. Ensure they can install and run the app.develop
branch. Verify the build appears in Firebase App Distribution.
Congratulations! You’ve navigated complex Android topics including Firestore, WorkManager, Compose, Flavors (with correct Firebase setup), R8, App Distribution, and CI/CD.
This project provides a solid foundation. From here, you can explore:
If you want to have access to the full code in my GitHub repository, contact me in the comments.
AdvancedConceptsApp/
├── .git/
├── .github/workflows/android_build_distribute.yml
├── .gradle/
├── app/
│ ├── build/
│ ├── libs/
│ ├── src/
│ │ ├── main/ # Common code, res, AndroidManifest.xml
│ │ │ └── java/com/yourcompany/advancedconceptsapp/
│ │ │ ├── data/Task.kt
│ │ │ ├── ui/TaskScreen.kt, TaskViewModel.kt, theme/
│ │ │ ├── worker/ReportingWorker.kt
│ │ │ └── MainActivity.kt
│ │ ├── dev/ # Dev flavor source set (optional overrides)
│ │ ├── prod/ # Prod flavor source set (optional overrides)
│ │ ├── test/ # Unit tests
│ │ └── androidTest/ # Instrumentation tests
│ ├── google-services.json # *** IMPORTANT: Contains configs for BOTH package names ***
│ ├── build.gradle.kts # App-level build script
│ └── proguard-rules.pro # R8/Proguard rules
├── api-project-xxx-yyy.json # Firebase service account key json
├── gradle/wrapper/
├── build.gradle.kts # Project-level build script
├── gradle.properties
├── gradlew
├── gradlew.bat
└── settings.gradle.kts
]]>