codesanitize

What’s new within the Jetpack Compose August ’25 launch

Android Development

codesanitize

-

13 August 2025

What’s new within the Jetpack Compose August ’25 launch

Posted by Meghan Mehta – Developer Relations Engineer and Nick Butcher – Product Supervisor

At the moment, the Jetpack Compose August ‘25 launch is secure. This launch incorporates model 1.9 of core compose modules (see the complete BOM mapping), introducing new APIs for rendering shadows, 2D scrolling, wealthy styling of textual content transformations, improved checklist efficiency, and extra!

To make use of at present’s launch, improve your Compose BOM model to 2025.08.00:

implementation(platform("androidx.compose:compose-bom:2025.08.00"))

Shadows

We’re completely happy to introduce two extremely requested modifiers: Modifier.dropShadow() and Modifier.innerShadow() permitting you to render box-shadow results (in comparison with the prevailing Modifier.shadow() which renders elevation primarily based shadows primarily based on a lighting mannequin).

Modifier.dropShadow()

The dropShadow() modifier attracts a shadow behind your content material. You possibly can add it to your composable chain and specify the radius, shade, and unfold. Keep in mind, content material that ought to seem on high of the shadow (like a background) ought to be drawn after the dropShadow() modifier.

@Composable
@Preview(showBackground = true)
enjoyable SimpleDropShadowUsage() {
    val pinkColor = Shade(0xFFe91e63)
    val purpleColor = Shade(0xFF9c27b0)
    Field(Modifier.fillMaxSize()) {
        Field(
            Modifier
                .measurement(200.dp)
                .align(Alignment.Middle)
                .dropShadow(
                    RoundedCornerShape(20.dp),
                    dropShadow = DropShadow(
                        15.dp,
                        shade = pinkColor,
                        unfold = 10.dp,
                        alpha = 0.5f
                    )
                )
                .background(
                    purpleColor,
                    form = RoundedCornerShape(20.dp)
                )
        )
    }
}

Determine 1. Drop shadow drawn throughout form

Modifier.innerShadow()

The Modifier.innerShadow() attracts shadows on the inset of the supplied form:

@Composable
@Preview(showBackground = true)
enjoyable SimpleInnerShadowUsage() {
    val pinkColor = Shade(0xFFe91e63)
    val purpleColor = Shade(0xFF9c27b0)
    Field(Modifier.fillMaxSize()) {
        Field(
            Modifier
                .measurement(200.dp)
                .align(Alignment.Middle)
                .background(
                    purpleColor,
                    form = RoundedCornerShape(20.dp)
                )
                .innerShadow(
                    RoundedCornerShape(20.dp),
                    innerShadow = InnerShadow(
                        15.dp,
                        shade = Shade.Black,
                        unfold = 10.dp,
                        alpha = 0.5f
                    )
                )
        )
    }
}

modifier.innerShadow() applied to a shape

Determine 2. Modifier.innerShadow() utilized to a form

The order for inside shadows is essential. The inside shadow attracts on high of the content material, so for the instance above, we wanted to maneuver the inside shadow modifier after the background modifier. We’d have to do one thing related when utilizing it on high of one thing like an Picture. On this instance, we’ve positioned a separate Field to render the shadow within the layer above the picture:

@Composable
@Preview(showBackground = true)
enjoyable PhotoInnerShadowExample() {
    Field(Modifier.fillMaxSize()) {
        val form = RoundedCornerShape(20.dp)
        Field(
            Modifier
                .measurement(200.dp)
                .align(Alignment.Middle)
        ) {
            Picture(
                painter = painterResource(id = R.drawable.cape_town),
                contentDescription = "Picture with Interior Shadow",
                contentScale = ContentScale.Crop,
                modifier = Modifier.fillMaxSize()
                    .clip(form)
            )
            Field(
                modifier = Modifier.fillMaxSize()
                    .innerShadow(
                        form,
                        innerShadow = InnerShadow(15.dp,
                            unfold = 15.dp)
                    )
            )
        }
    }
}

Determine 3.Interior shadow on high of a picture

New Visibility modifiers

Compose UI 1.8 launched onLayoutRectChanged, a brand new performant option to monitor the situation of components on display screen. We’re constructing on high of this API to assist frequent use circumstances by introducing onVisibilityChanged and onFirstVisible. These APIs settle for non-obligatory parameters for the minimal fraction or period of time the merchandise has been seen for earlier than invoking your motion.

Use onVisibilityChanged for UI modifications or unintended effects that ought to occur primarily based on visibility, like robotically enjoying and pausing movies or beginning an animation:

LazyColumn {
  gadgets(feedData) { video ->
    VideoRow(
        video,
        Modifier.onVisibilityChanged(minDurationMs = 500, minFractionVisible = 1f) {
          seen ->
            if (seen) video.play() else video.pause()
          },
    )
  }
}

Use onFirstVisible to be used circumstances if you want to react to a component first changing into seen on display screen for instance to log impressions:

LazyColumn {
    gadgets(100) {
        Field(
            Modifier
                // Log impressions when merchandise has been seen for 500ms
                .onFirstVisible(minDurationMs = 500) { /* log impression */ }
                .clip(RoundedCornerShape(16.dp))
                .drawBehind { drawRect(backgroundColor) }
                .fillMaxWidth()
                .peak(100.dp)
        )
    }
}

Wealthy styling in OutputTransformation

BasicTextField now helps making use of kinds like shade and font weight from inside an OutputTransformation.

The brand new TextFieldBuffer.addStyle() strategies allow you to apply a SpanStyle or ParagraphStyle to vary the looks of textual content, with out altering the underlying TextFieldState. That is helpful for visually formatting enter, like telephone numbers or bank cards. This methodology can solely be referred to as inside an OutputTransformation.

// Format a telephone quantity and shade the punctuation
val phoneTransformation = OutputTransformation {
    // 1234567890 -> (123) 456-7890
    if (size == 10) {
        insert(0, "(")
        insert(4, ") ")
        insert(9, "-")

        // Shade the added punctuation
        val grey = Shade(0xFF666666)
        addStyle(SpanStyle(shade = grey), 0, 1)
        addStyle(SpanStyle(shade = grey), 4, 5)
        addStyle(SpanStyle(shade = grey), 9, 10)
    }
}

BasicTextField(
    state = myTextFieldState,
    outputTransformation = phoneTransformation
)

LazyLayout

The constructing blocks of LazyLayout are all now secure! Try LazyLayoutMeasurePolicy, LazyLayoutItemProvider, and LazyLayoutPrefetchState to construct your personal Lazy parts.

Prefetch Enhancements

There at the moment are important scroll efficiency enhancements in Lazy Record and Lazy Grid with the introduction of recent prefetch conduct. Now you can outline a LazyLayoutCacheWindow to prefetch extra content material. By default, just one merchandise consists forward of time within the course of scrolling, and after one thing scrolls off display screen it’s discarded. Now you can customise the quantity of things forward to prefetch and behind to retain by means of a fraction of the viewport or dp measurement. While you choose into utilizing LazyLayoutCacheWindow, gadgets start prefetching within the forward space immediately.

The configuration entry level for that is on LazyListState, which takes within the cache window measurement:

@OptIn(ExperimentalFoundationApi::class)
@Composable
non-public enjoyable LazyColumnCacheWindowDemo() {
    // Prefetch gadgets 150.dp forward and retain gadgets 100.dp behind the seen viewport
    val dpCacheWindow = LazyLayoutCacheWindow(forward = 150.dp, behind = 100.dp)
    // Alternatively, prefetch/retain gadgets as a fraction of the checklist measurement
    // val fractionCacheWindow = LazyLayoutCacheWindow(aheadFraction = 1f, behindFraction = 0.5f)
    val state = rememberLazyListState(cacheWindow = dpCacheWindow)
    LazyColumn(state = state) {
        gadgets(1000) { Textual content(textual content = "$it", fontSize = 80.sp) }
    }
}

Notice: Prefetch composes extra gadgets than are at the moment seen — the brand new cache window API will seemingly improve prefetching. Which means that merchandise’s LaunchedEffects and DisposableEffects might run earlier – don’t use this as a sign for visibility e.g. for impression monitoring. As a substitute, we advocate utilizing the brand new onFirstVisible and onVisibilityChanged APIs. Even if you happen to’re not manually customizing LazyLayoutCacheWindow now, keep away from utilizing composition results as a sign of content material visibility, as this new prefetch mechanism will likely be enabled by default in a future launch.

Scroll

2D Scroll APIs

Following the discharge of Draggable2D, Scrollable2D is now accessible, bringing two-dimensional scrolling to Compose. Whereas the prevailing Scrollable modifier handles single-orientation scrolling, Scrollable2D allows each scrolling and flinging in 2D. This lets you create extra complicated layouts that transfer in all instructions, corresponding to spreadsheets or picture viewers. Nested scrolling can also be supported, accommodating 2D eventualities.

val offset = bear in mind { mutableStateOf(Offset.Zero) }
Field(
    Modifier.measurement(150.dp)
        .scrollable2D(
            state =
                rememberScrollable2DState { delta ->
                    offset.worth = offset.worth + delta // replace the state
                    delta // point out that we consumed all of the pixels accessible
                }
        )
        .background(Shade.LightGray),
    contentAlignment = Alignment.Middle,
) {
    Textual content(
        "X=${offset.worth.x.roundToInt()} Y=${offset.worth.y.roundToInt()}",
        model = TextStyle(fontSize = 32.sp),
    )
}

Scroll Interop Enhancements

There are bug fixes and new options to enhance scroll and nested scroll interop with Views, together with the next:

Fastened the dispatching of incorrect velocities throughout fling animations between Compose and Views.

Compose now accurately invokes the View’s nested scroll callbacks within the applicable order.

Enhance crash evaluation by including supply information to stack traces

We’ve heard from you that it may be laborious to debug Compose crashes when your personal code doesn’t seem within the stack hint. To deal with this we’re offering a brand new, opt-in API to supply richer crash location particulars, together with composable names and places enabling you to:

Effectively establish and resolve crash sources.

Extra simply isolate crashes for reproducible samples.

Examine crashes that beforehand solely confirmed inside stack frames.

Notice that we don’t advocate utilizing this API in launch builds as a result of efficiency influence of accumulating this additional info, nor does it work in minified apks.

To allow this function, add the road beneath to the appliance entry level. Ideally, this configuration ought to be carried out earlier than any compositions are created to make sure that the stack hint info is collected:

class App : Software() {
   override enjoyable onCreate() {
        // Allow just for debug taste to keep away from perf regressions in launch
        Composer.setDiagnosticStackTraceEnabled(BuildConfig.DEBUG)
   }
}

New annotations and Lint checks

We’re introducing a brand new runtime-annotation library that exposes annotations utilized by the compiler and tooling (corresponding to lint checks). This enables non-Compose modules to make use of these annotations with no dependency on the Compose runtime library. The @Secure, @Immutable, and @StableMarker annotations have moved to runtime-annotation, permitting you to annotate lessons and capabilities that don’t rely upon Compose.

Moreover, we have now added two new annotations and corresponding lint checks:

@RememberInComposition: An annotation that may mark constructors, capabilities, and property getters, to point that they need to not be referred to as instantly inside composition with out being remembered. Errors will likely be raised by a corresponding lint examine.

@FrequentlyChangingValue: An annotation that may mark capabilities, and property getters, to point that they shouldn’t be referred to as instantly inside composition, as this will trigger frequent recompositions (for instance, marking scroll place values and animating values). Warnings are supplied by a corresponding lint examine.

Extra updates

To simplify compatibility and enhance stability for lint examine assist, Compose now requires Android Gradle Plugin (AGP) / Lint model 8.8.2 or increased. Try this new documentation web page to study extra.

Two new APIs have been added for context menus:

Get began

We recognize all bug studies and have requests submitted to our situation tracker. Your suggestions permits us to construct the APIs you want in your apps. Joyful composing!

Cisco strengthens AI networking story

Computer Networking

codesanitize

-

13 August 2025

0

“General, AI demand within the enterprise will develop over time. However enterprise prospects have to see the worth, see the ROI. Additionally, they should have a well-defined use case,” Wollenweber stated, noting that the 12-month innovation cycles of GPU distributors will be problematic if prospects select the unsuitable platform. If prospects “make a big funding and may’t capitalize on that funding and get worth out of the tools, then by the point they get to maturity, the subsequent generations of GPUs are there and so they need to transfer,” he stated.

That’s another excuse prospects are experimenting with AI through cloud suppliers or sovereign AI amenities which can be constructed for experimentation and for increasing AI use instances, Wollenweber stated.

AI group constructing

Whereas Cisco is concentrated on bolstering enterprise infrastructure, it’s additionally doing work with the broader the AI group by making out there expertise it hopes will drive additional utilization.

Most just lately, Cisco donated its AGNTCY initiative to the Linux Basis, which is able to proceed to advance the AI agent administration platform as an open-source mission. Outshift, which is Cisco’s analysis and improvement arm, launched AGNTCY to develop AI agent discovery, identification, messaging, and observability infrastructure.

Underneath the auspices of the Linux Basis, Cisco, Dell, Google Cloud, Oracle, Crimson Hat and greater than 65 different distributors will construct a variety of industry-standard protocols and frameworks to permit AI brokers to find each other, talk, collaborate and be managed throughout platforms, fashions, and organizations, based on the Linux Basis and Cisco.

“However to construct these collaborative techniques, brokers want to have the ability to discover one another, confirm their identities, and share context with out costly customized integration work. Agentic AI is now on the similar inflection level the early web confronted. Good particular person techniques that may’t speak to one another, the place each agent is its personal island – till frequent protocols emerge,” wrote Vijoy Pandey, normal supervisor and senior vp of Outshift by Cisco, in a weblog put up concerning the contribution.

Workforce OKRs in Motion

Software Development

codesanitize

-

13 August 2025

0

OKRs—Goals and Key Outcomes—have turn into a well-liked goal-setting
framework in tech and past. They had been designed to bridge the hole between
technique and execution, promising focus, alignment, and accountability. However
too typically, they’ve changed into one thing else completely: a quarterly ritual
of checklists, dashboards, and efficiency metrics that smother the unique
intent.

I’ve seen it occur in organizations huge and small. Targets are written
down, however nothing actually modifications. Groups comply at greatest—or disengage
fully.

This text is my response. It’s concerning the groups that break that
sample—those that use OKRs not as a administration instrument, however as a technique to personal
outcomes, align with technique, and ship actual leads to the messy,
fantastic actuality of constructing merchandise and serving prospects.

Widespread Pitfalls of OKRs in Follow

OKRs are all over the place. From startups to massive enterprises, they present up in
kickoff conferences, dashboards, and technique paperwork.

However in lots of organizations I’ve labored with, OKRs hardly ever change how groups
really work—or ship.

Too typically, targets are written down however fail to drive motion. Why? As a result of
they’re imposed from above. Management defines targets and key outcomes,
fingers them down, and expects groups to execute.

Generally these OKRs are nothing greater than KPIs with new labels. Different
instances, they’re imprecise slogans—disconnected from actual work. Both manner, the
outcome is similar: groups don’t personal the targets. With out possession, they comply
at greatest—or disengage completely. True dedication is uncommon.

When OKRs are handed down as an alternative of co-created, they lose their energy.
Moderately than driving focus and adaptation, they turn into static artifacts—one other
checkbox in a quarterly ritual.

This isn’t the one manner it will probably go. I’ve labored with groups that broke the
sample. Not by ready for somebody handy them higher targets—however by stepping
up, defining their very own, and proudly owning the outcomes.

These groups didn’t deal with OKRs like checklists or dashboards. They made them
a part of how they assume, plan, and ship daily.

Excessive performing groups personal the result

At ThoughtWorks, I facilitated a whole lot of Lean Inceptions with
cross-functional groups—builders, designers, product managers, and analysts.
Every session pulsed with vitality as individuals collaborated, shared concepts, and
challenged assumptions.

Within the highest-performing groups, nonetheless, one thing stood out. They didn’t
simply speak about options or supply dates; they might clearly reply 4 key
questions:

What’s the group’s strategic objective?
What a part of this technique is related to us?
What can we actually transfer this quarter?
How will we all know we’re making progress?

These solutions weren’t imprecise. They had been particular and grounded. Because of this,
these groups linked their day by day work to broader outcomes—and it confirmed.
Their choices had been sharper, their priorities clearer, and their code
delivered actual outcomes.

This shift—from executing duties to pursuing function—modified every little thing.
That’s the place Workforce OKRs reside: in high-performing groups that join their targets
to actual outcomes. However a Workforce OKR isn’t a standalone train. It’s a
bridge—serving to groups ship on the group’s technique whereas staying
grounded in what they will affect and obtain collectively.

Bridging the Hole: Technique and Workforce OKRs

Workforce autonomy doesn’t must imply isolation, and strategic alignment
doesn’t require command and management. But in lots of organizations, these two
concepts typically conflict.

Management units strategic priorities and expects groups to “align.” Groups,
in the meantime, outline OKRs they consider matter—however these don’t at all times map to the
larger image. The result’s misalignment, frustration, and wasted
vitality.

Nice groups and nice leaders bridge that hole by assembly within the center.
Technique gives route; Workforce OKRs create dedication.

This isn’t a cascade. It’s a dialog.

Determine 1: Prime-down OKR & a standard
pitfall: OKRs outlined on the prime, damaged into elements, and pushed down.

In high-performing environments, management shares intent—the challenges to
resolve, the alternatives to grab, the metrics to maneuver. Groups pay attention, replicate,
and outline what they’ll personal. As one staff would possibly body it:

“Primarily based on what we all know and might affect, right here’s what we consider we will
obtain—and the way we’ll measure progress.”

Right here, possession isn’t assigned; it’s assumed. Workforce OKRs allow not simply
strategic compliance however strategic contribution.

Determine 2: Alignment Over Cascading: The shift from cascading targets to
collaborative alignment round strategic targets.

What Makes Workforce OKRs Totally different

Workforce OKRs aren’t assigned, nor are they dropped into trackers by
management. They’re assumed—created by the staff, for the staff.

This shift issues. It marks the distinction between executing somebody
else’s priorities and committing to an consequence the staff actually believes in.

With Workforce OKRs, the method seems to be completely different:

The staff defines the Goal, rooted within the strategic context. It’s not
only a fancy slogan—it’s a transparent and significant assertion of what the staff desires
to attain and why it issues.
The staff identifies Key Outcomes—clear indicators of progress that present actual,
measurable change. A Key End result typically isn’t a KPI itself, however a motion in a
KPI. It’s about route and affect, not simply numbers.
The staff commits to the result, not simply doing duties. They take actual
possession, keep versatile, and concentrate on what actually brings worth.

Leaders nonetheless lead, however their position modifications. As a substitute of dictating the how,
they make clear the why. They share route, invite dialogue, and help groups
in constructing actual possession.

This isn’t chaos. It’s alignment via belief.

From Technique to Workforce OKR

Workforce OKRs don’t exist in isolation. They emerge from context—formed by
imaginative and prescient, guided by technique, and grounded in actuality.

Determine 3: How every layer nests into the subsequent to kind a transparent chain from
imaginative and prescient to execution.

This layered mannequin reveals how intent flows into motion:

Imaginative and prescient units the long-term route.
Technique defines present priorities.
Workforce OKRs make clear what every staff will personal.
Backlog connects intent to concrete work.

Every layer helps the subsequent. When imaginative and prescient is unclear, technique struggles to
concentrate on what issues most subsequent. With no clear technique, Workforce OKRs lose
alignment and function. And when Workforce OKRs are imprecise, backlogs fill with
scattered duties quite than deliberate steps towards significant outcomes.

However when these layers align, groups can confidently translate high-level
intent into centered, significant motion.

From Path to Definition: Key Conversations

Determine 4: The circulation of structured conversations that
rework technique into work.

Alignment doesn’t occur in a single assembly; it evolves via a rhythm
of structured conversations. This timeline illustrates how technique turns into
significant staff motion:

Strategic Alignment Workshop: Management shares intent, not
deliverables.
Workforce OKR Planning Workshop: Groups replicate and outline what they’ll
pursue.
From Targets to Work: OKRs circulation into backlog objects and initiatives.

This isn’t a inflexible cascade. It’s a rhythm of dialogue and iteration,
constructing alignment with out sacrificing autonomy.

A Actual Instance: From Technique to Dedication

I’ve labored with many massive organizations, and I get it: management wants
construction, a gradual rhythm, and alignment throughout enterprise items. Strategic
OKRs will be extremely highly effective when used the suitable manner.

Right here’s how one massive Brazilian monetary establishment created a easy but
efficient technique to join technique and execution.

Determine 5: From Technique to Workforce OKRs: Yearly Planning
and Quarterly Execution

Management Defines Firm Priorities

At the beginning of the 12 months, management set three daring priorities: simplify
onboarding for brand new prospects, develop into the small-business phase, and
enhance resilience in essential techniques.

This wasn’t a want listing. Leaders intentionally centered on a couple of
high-impact bets, creating house for enterprise items and groups to take
significant possession.

Enterprise Items Construct Their Plans

The Digital Companies Enterprise Unit—liable for the net banking
platform—centered on precedence #1: simplifying onboarding. They outlined their
Strategic OKR:

Goal: Delight new prospects by reworking the first-week
expertise.

Key Outcomes:

Cut back first-week buyer drop-off price by 25%
Enhance total first-week NPS from 20 to 35.
Decrease common help name time for brand new customers by 15%.

This Strategic OKR grew to become a north star for a number of groups, providing
route with out prescribing options.

Strategic OKRs Are Refined in Dialog

Strategic OKRs at each firm and BU ranges had been refined via
dialogue, not decree. Leaders challenged assumptions, clarified metrics, and
aligned on the place every BU may create probably the most affect.

Word that this Strategic OKR was later pushed by a number of groups.
Larger-level management, although they’d entry to all staff OKRs, selected not
to trace them immediately. As a substitute, they reviewed a month-to-month report centered on
the BU’s Strategic OKR—a realistic strategy for big organizations the place
prime leaders can’t realistically observe each staff’s targets.

Groups Outline Their OKRs

When BU-level targets reached groups, they arrived as context, not orders.
BU leaders shared supporting information—consumer analytics, drop-off factors, buyer
complaints—then stepped again.

The Discover Workforce, liable for cellular app onboarding within the Digital
Companies BU, requested themselves: “What a part of this may we personal? What would
success seem like from our perspective?”

Their Workforce OKR:

Goal: Make the primary week seamless and confidence-boosting for
new customers.

Key Outcomes:

Enhance onboarding completion from 65% to 90%.
Increase tutorial engagement from 15% to 50%.
Cut back help tickets about account setup by 30%.

Over the quarter, the Discover Workforce redesigned onboarding flows, examined
tutorials, and improved contextual assist. Weekly check-ins and mid-cycle
retrospectives stored them adaptive and accountable. By the top of the cycle,
they’d delivered measurable enhancements in buyer outcomes, immediately
supporting the BU’s Strategic OKR.

Word on Adaptation: This instance attracts from actual patterns I’ve noticed
in massive organizations. To respect confidentiality, particulars have been
modified, however the essence of how Strategic OKRs and Workforce OKRs join
stays intact.

Align Up. Align Throughout: Constructing Strategic Alignment With out Shedding Workforce Autonomy

After I speak about alignment in massive organizations, I don’t simply imply
aligning as much as management’s technique. That’s solely half the story. The opposite
half—and infrequently the trickier one—is aligning throughout peer groups. Each dimensions
are important for making Workforce OKRs work at scale.

That is what I name vertical and horizontal alignment.

Vertical alignment connects a staff’s OKRs to the group’s strategic
targets (some individuals name this connecting tactical OKRs to strategic OKRs). It
solutions a essential query: “How does our work contribute to the larger
image?”
Horizontal alignment ensures that groups working in the identical enterprise unit—or
throughout items—coordinate and collaborate successfully. It asks: How will we help
one another to achieve shared outcomes?

Assume of a big enterprise unit like a fleet of ships. Every staff (or “ship”)
has its personal captain and crew, charting their course. However they’re not
navigating alone. They’re transferring collectively towards the identical North Star. That’s
the essence of horizontal alignment.

Every staff chases its personal Workforce OKR, tailor-made to its experience and sphere of
affect. However their efforts are interconnected—like gears in a machine. The
magic occurred in how they modify to one another’s progress in actual time,
conserving the bigger goal in sight.

That is alignment with out rigidity. Groups nonetheless owned their OKRs and have
autonomy over how they contribute. However they aren’t working in silos; they’re
navigating collectively.

Determine 6: A number of groups contributing to a shared strategic goal, every with their very own Workforce OKRs complementing each other

So how do groups preserve alignment alive—with out dropping autonomy? That is the place
the Workforce OKR Cycle helps. It’s a easy rhythm that helps focus,
collaboration, and flexibility.

The Workforce OKR Cycle

To assist groups put this into observe, I like to recommend a light-weight, repeatable
cycle. It retains groups centered, aligned, and capable of adapt as circumstances
change.

The Workforce OKR Cycle revolves round three key moments:

Workforce OKR Planning (sometimes quarterly): A second for alignment. The
staff connects with management, understands the strategic context, and defines
its OKRs—clarifying what they wish to obtain and the way they’ll measure
progress.
Workforce OKR Test-in (weekly): A light-weight sync led by the staff. They
evaluate key outcomes, talk about progress, determine blockers, and modify course as
wanted—catching points earlier than they derail momentum.
Workforce OKR Retrospective (mid-cycle and finish): A mirrored image level the place the
staff seems to be again not simply at supply, however at affect. These retrospectives assist
refine each intent and execution for future cycles.

This rhythm transforms OKRs from a one-time planning train right into a residing
system—a steady loop of alignment and adaptation.

Determine 7: A typical Workforce OKR cycle

Workforce OKR Planning Workshop

The Workforce OKR Planning Workshop occurs at first of every cycle. It’s
when the staff comes collectively to outline its Goal and Key Outcomes, aligning
with their BU’s strategic route.

This isn’t a top-down handoff; it’s a co-creation second that units
route and fosters possession.

One facilitation method I typically use is the Time Machine exercise:

“Please enter the Time Machine. Think about it’s the top of the quarter. You’re
happy with what the staff has achieved. What occurred?”

Every staff member writes their imagined success story. These reflections
floor themes and insights, that are then translated into measurable
indicators of progress. These indicators turn into the Key Outcomes.

When groups run this exercise, OKRs shift from static targets to expressions
of actual intent and shared dedication.

Workforce OKR Test-ins

That is the place many groups lose momentum—and the place the perfect groups stand
out.

A Workforce OKR Test-in is a brief, recurring second (for instance, Fridays at 2
p.m.) the place the staff displays collectively. It’s not a standing report; it’s a
dialog about progress and priorities.

Groups ask:

Are we making significant progress?
Are we measuring the suitable issues?
What’s working—and what’s getting in the way in which?
Do we have to modify course?

These questions rework OKRs from static artifacts into dynamic, residing
conversations.

I name check-ins the heartbeat of the OKR cycle. They preserve the staff
aligned—not simply on progress, however on confidence and vitality.

Do Your Test-in with GRIP

To maintain check-ins centered and actionable, I information groups with a easy
framework:

GRIP

Purpose confidence: How assured are we in reaching the Goal?
Outcomes progress: What’s the present standing of every Key End result?
Points: What’s getting in the way in which?
Plan ahead: What’s subsequent?

A fast GRIP check-in turns OKRs into energetic conversations—not only a
evaluate, however a possibility to regulate course earlier than points escalate.

In lots of groups I’ve labored with, the GRIP check-in grew to become a 15-minute weekly
anchor. It created a shared language—“What’s our confidence this week?”—and
helped groups see the place they wanted help or the place to double down. Like a
pilot scanning devices mid-flight, GRIP gave them readability to navigate
ahead.

Workforce OKR Retrospective

On the finish of the cycle, the staff doesn’t simply rating the OKR—they replicate
on the journey:

Did we obtain what we got down to do?
What did we be taught?
What stunned us?
What’s going to we do in a different way subsequent time?

That is the place studying occurs. One of the simplest ways to help it’s with a
retrospective.

You’ll discover dozens of efficient codecs at
FunRetrospectives.com and within the ebook
FunRetrospectives.

However don’t wait till the top to replicate. Mid-cycle retrospectives will be
simply as highly effective—particularly when the staff feels caught, misaligned, or not sure
about progress. They provide an opportunity to regroup whereas there’s nonetheless time to
course-correct.

Mid-cycle retrospectives aren’t obligatory, however they’re extremely useful
when the staff senses misalignment, stalled progress, or shifting priorities.
Some groups schedule them proactively on the midpoint of their OKR cycle;
others use them as a versatile instrument after they really feel momentum is slipping or
context modifications unexpectedly.

One format I typically use mid-cycle is Attractors and Detractors, a easy
but highly effective exercise for unpacking the systemic forces influencing the OKR so
far. It highlights:

Attractors: What pulled us towards the OKR?
Detractors: What pushed us away from it?

This exercise helps groups make sense of their work—clarifying what aligns
with their OKR and what doesn’t. It sharpens focus and prioritization,
particularly for groups severe about reaching their targets.

In a single staff I labored with, a mid-cycle retrospective utilizing this format
uncovered a brand new organizational initiative that was unintentionally diverting
effort away from the staff’s OKR. That perception helped them realign and regain
focus, resulting in significant affect by the top of the cycle.

What Units Nice Groups Aside

The distinction isn’t within the course of or the instrument. It’s within the mindset.

Groups that personal their OKRs don’t simply align with technique—they form it.
They don’t simply ship outputs—they ship outcomes.

That’s what makes them stand out. And that’s what makes Workforce OKRs work.

ios – Learn how to rename an open doc in a SwiftUI DocumentGroup app with customized navigation?

iOS Development

codesanitize

-

13 August 2025

0

I am constructing a document-based SwiftUI app following Apple’s Constructing a Doc-Based mostly App with SwiftUI information. The app makes use of DocumentGroup and shops paperwork in iCloud Drive.

Necessary context: We’re utilizing a customized navigation bar as an alternative of the system’s default navigation bar, which implies we do not have entry to the built-in rename performance that comes with the usual doc title bar.

Present Setup

   @principal
   struct MyApp: App {
       var physique: some Scene {
           DocumentGroup(newDocument: MyDocument()) { file in
               ContentView(doc: file.$doc)
                   .navigationBarHidden(true) // Utilizing customized navigation
           }
       }
   }

The Drawback

I must rename the at present open doc programmatically from inside the app. When making an attempt to make use of FileManager.moveItem(at:to:), I get this error:

Error Area=NSCocoaErrorDomain Code=513 “”Untitled 142” could not be moved as a result of
you do not have permission to entry “CamPlan”.”
UserInfo={NSUnderlyingError=0x140b62310 {Error Area=NSPOSIXErrorDomain Code=1 “Operation not permitted”}}

The file path is in iCloud: /personal/var/cell/Library/Cell Paperwork/com~apple~CloudDocs/CamPlan/Untitled 142.cplan

What I’ve Tried

Direct FileManager strategy – Ends in permission error:

strive FileManager.default.moveItem(at: currentURL, to: newURL)

NSFileCoordinator – Hangs indefinitely, doubtless as a result of doc already being coordinated:

let coordinator = NSFileCoordinator(filePresenter: nil)
coordinator.coordinate(writingItemAt: currentURL, choices: .forMoving, error: &error) { url in
    // This block by no means executes - coordination hangs
}

Surroundings rename motion – Returns nil since we’re not utilizing the system navigation:
```
@Surroundings(.rename) personal var rename  // rename is nil
```
Copy and delete strategy – Additionally fails with permission errors in iCloud listing

Query

How can I programmatically rename the at present open doc in a DocumentGroup-based SwiftUI app when:

The doc is saved in iCloud Drive
We’re utilizing a customized navigation bar (not the system one)
The doc is at present open and being edited

Is there a correct API or methodology to set off a doc rename that works with DocumentGroup’s file coordination and iCloud’s necessities? Or do I want to shut the doc first, rename it, after which reopen it?

Surroundings: iOS 17+, SwiftUI, DocumentGroup structure

DEF CON analysis takes intention at ZTNA, calls it a bust

Computer Networking

codesanitize

-

13 August 2025

0

DEF CON analysis takes intention at ZTNA, calls it a bust

Main vendor vulnerabilities span authentication and design flaws

The analysis uncovered vital vulnerabilities throughout Examine Level, Zscaler and Netskope that fell into three main classes: authentication bypasses, credential storage failures and cross-tenant exploitation.

Authentication bypass vulnerabilities

Zscaler’s SAML implementation contained essentially the most extreme authentication flaw. The researchers found that the signature on the SAML assertion was solely checked for presence, and it wasn’t validated towards the identification supplier’s public key. This allowed full bypass of identification supplier authentication by forging SAML responses with invalid signatures.

Netskope suffered from an analogous however extra elementary bypass. The enrollment API required no authentication, permitting attackers to register units utilizing solely leaked group keys and legitimate e mail addresses.

Examine Level’s vulnerability centered on hard-coded encryption keys embedded in shopper binaries. These keys protected diagnostic log uploads containing JSON Internet Tokens (JWTs) that lived for 30 days creating a possible compromise situation for any buyer who had uploaded logs to assist.

Credential storage and token administration flaws

All three distributors applied weak credential storage mechanisms. Zscaler saved Machine Token Authentication credentials in Home windows registry in clear textual content, permitting native attackers to extract tokens and impersonate any consumer by modifying registry values. Netskope’s “Safe Enrollment” tokens used DPAPI encryption with inadequate safety.

Vendor response and remediation

Vendor responses diverse considerably in pace and effectiveness. In keeping with the researchers, Zscaler responded most quickly, initially patching their SAML vulnerability (CVE-2025-54982) inside 4 hours. Nonetheless, the repair launched compatibility points requiring a rollback earlier than a everlasting answer was applied.