--- title: Building a real-time PWA on Atlassian’s own stack description: Atlassian built a React/TypeScript PWA for their Unleash 2026 tech summit that served 500+ concurrent users entirely on the Atlassian stack. Jira acted as the... canonical: https://daily.dev/posts/building-a-real-time-pwa-on-atlassian-s-own-stack-8iip2lxb7 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Building a real-time PWA on Atlassian’s own stack | daily.dev og:description: Atlassian built a React/TypeScript PWA for their Unleash 2026 tech summit that served 500+ concurrent users entirely on the Atlassian stack. Jira acted as the... og:url: https://daily.dev/posts/building-a-real-time-pwa-on-atlassian-s-own-stack-8iip2lxb7 og:image: https://api.daily.dev/og/posts/8iip2lxB7.png og:image:alt: Building a real-time PWA on Atlassian’s own stack og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Building a real-time PWA on Atlassian’s own stack **[Atlassian](https://daily.dev/sources/atlassian)** · 13 min read · 1 upvotes · 0 comments ## Summary Atlassian built a React/TypeScript PWA for their Unleash 2026 tech summit that served 500+ concurrent users entirely on the Atlassian stack. Jira acted as the system of record for sessions, leaderboards, and push notifications; Rovo powered an AI event guide; Loom served session recordings; and Bitbucket Pipelines let attendees ship real code to production live during the event. Key engineering challenges included modeling event data in Jira, handling eventual consistency with a durable local outbox and state machine, and aggressive performance optimization that cut initial load time from ~12 seconds to under 1 second by deduplicating API calls, fixing a missing minification build config (7.7 MB → 1.53 MB bundle), and breaking a sequential auth waterfall. The app achieved 80% attendee adoption with 8 features shipped live during the event. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I reduce duplicate API calls when multiple React components request the same data on mount? Share the in-flight promise across components instead of caching completed responses, since a response cache does not help when the first request has not returned yet. When a second component requests the same endpoint while a request is already pending, it reuses that same promise so both callers receive the identical result once it resolves. Applying this to identity, project metadata, and leaderboard fetches cut page-load API calls from 24 to 16 and eliminated 8 duplicate calls entirely. _daily.dev surfaces practical patterns like in-flight request deduplication for developers optimizing React data fetching._ ### How do you handle eventual consistency in a frontend app right after a user logs in and permissions haven't propagated yet? Model readiness as a state machine with a converging and a ready state rather than treating it as a boolean. In the converging state the app renders safe cached or bundled data, captures user intent in a durable local outbox before trusting the write path, and overlays that intent until a live read confirms it, avoiding empty screens or misleading errors during permission propagation delays. _developers designing resilient post-login flows can find architecture patterns like this via daily.dev._ ### What caused a JavaScript bundle to be 7.7MB unminified and how was it fixed? A production build configuration bug caused the bundle to ship unminified and readable directly in DevTools, despite being a logic-free build issue. Fixing the build configuration reduced the bundle from roughly 7.7 MB to about 1.53 MB, an 80% reduction, and was one of several fixes that brought time to first useful content from about 12 seconds down to under 1 second. _daily.dev helps engineers track down performance regressions like build misconfigurations before they ship._ ## Similar posts on daily.dev - [Engineering at AI scale: Unlocking velocity and visibility](https://daily.dev/posts/engineering-at-ai-scale-unlocking-velocity-and-visibility-hajymprch) · Atlassian · 0 upvotes · 0 comments - [Beyond the Jira board: how autonomous workflows unlock engineering velocity](https://daily.dev/posts/beyond-the-jira-board-how-autonomous-workflows-unlock-engineering-velocity-g3s2s4agr) · Atlassian · 0 upvotes · 0 comments - [Atlassian Underpins Code Creation With New Agentic Insight Channels](https://daily.dev/posts/atlassian-underpins-code-creation-with-new-agentic-insight-channels-jubmprpyk) · DevOps.com · 0 upvotes · 0 comments - [Atlassian unveils Teamwork Graph, Rovo Max at its Team event](https://daily.dev/posts/atlassian-unveils-teamwork-graph-rovo-max-at-its-team-event-tkllqrr1v) · SD Times · 0 upvotes · 0 comments --- Tags: [#webdev](https://daily.dev/tags/webdev), [#react](https://daily.dev/tags/react), [#atlassian](https://daily.dev/tags/atlassian), [#jira](https://daily.dev/tags/jira) [View this post on daily.dev](https://daily.dev/posts/building-a-real-time-pwa-on-atlassian-s-own-stack-8iip2lxb7) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Building a real-time PWA on Atlassian’s own stack","url":"https://daily.dev/posts/building-a-real-time-pwa-on-atlassian-s-own-stack-8iip2lxb7","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/building-a-real-time-pwa-on-atlassian-s-own-stack-8iip2lxb7"},"datePublished":"2026-08-07T01:38:10.760Z","dateModified":"2026-09-14T06:40:30.060Z","description":"Atlassian built a React/TypeScript PWA for their Unleash 2026 tech summit that served 500+ concurrent users entirely on the Atlassian stack. Jira acted as the...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/69f18f19aedf4d7b8e36911b10ea5743?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/69f18f19aedf4d7b8e36911b10ea5743?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Atlassian","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Atlassian","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/44750d8e66de4411bb477159b321bb43","url":"https://daily.dev/sources/atlassian"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/building-a-real-time-pwa-on-atlassian-s-own-stack-8iip2lxb7","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"webdev,react,atlassian,jira","timeRequired":"PT13M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Atlassian","item":"https://daily.dev/sources/atlassian"},{"@type":"ListItem","position":3,"name":"Building a real-time PWA on Atlassian’s own stack"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/building-a-real-time-pwa-on-atlassian-s-own-stack-8iip2lxb7#faq","mainEntity":[{"@type":"Question","name":"How can I reduce duplicate API calls when multiple React components request the same data on mount?","acceptedAnswer":{"@type":"Answer","text":"Share the in-flight promise across components instead of caching completed responses, since a response cache does not help when the first request has not returned yet. When a second component requests the same endpoint while a request is already pending, it reuses that same promise so both callers receive the identical result once it resolves. Applying this to identity, project metadata, and leaderboard fetches cut page-load API calls from 24 to 16 and eliminated 8 duplicate calls entirely. daily.dev surfaces practical patterns like in-flight request deduplication for developers optimizing React data fetching."}},{"@type":"Question","name":"How do you handle eventual consistency in a frontend app right after a user logs in and permissions haven't propagated yet?","acceptedAnswer":{"@type":"Answer","text":"Model readiness as a state machine with a converging and a ready state rather than treating it as a boolean. In the converging state the app renders safe cached or bundled data, captures user intent in a durable local outbox before trusting the write path, and overlays that intent until a live read confirms it, avoiding empty screens or misleading errors during permission propagation delays. developers designing resilient post-login flows can find architecture patterns like this via daily.dev."}},{"@type":"Question","name":"What caused a JavaScript bundle to be 7.7MB unminified and how was it fixed?","acceptedAnswer":{"@type":"Answer","text":"A production build configuration bug caused the bundle to ship unminified and readable directly in DevTools, despite being a logic-free build issue. Fixing the build configuration reduced the bundle from roughly 7.7 MB to about 1.53 MB, an 80% reduction, and was one of several fixes that brought time to first useful content from about 12 seconds down to under 1 second. daily.dev helps engineers track down performance regressions like build misconfigurations before they ship."}}]} ```