@arcinternet@diabrowser@joshm@charliedeets Arc said goodbye, so be honest: Dia mobile isโฆ
a. Almost here
b. Soon!
c. Living in a Figma file
d. Josh has it on his phone and won't share.
We've decided to sunset Arc on December 22, 2026.
That's not an easy sentence to write. We spent years building Arc and celebrating each and every release along the way: we have so much pride and love for what we made alongside the Arc community.
Our priority is to deliver best-in-class security for our members. Keeping a browser secure takes constant, dedicated work that is only increasing in the age of AI. Dia was built from the ground up to meet todayโs security standards, so that's where our engineering and security teams will focus moving forward.
We've worked to make switching to @diabrowser as easy as possible for Arc members. Here's how:
ยท Your passwords, bookmarks, extensions and history come over to Dia seamlessly.
ยท Spaces, Folders, and Tab Groups are in Dia and import over with your data intact.
ยท Dia now surpasses Arc benchmarks in stability, speed, and security.
ยท The browser features you use in Arc are free in Dia, and the AI is optional.
Thank you for using Arc, for pushing us to make it better, and for building alongside us. The team that made Arc is the same team behind Dia, and some of our most ambitious work is just ahead. We'd love for you to be there with us when it lands.
๐ฑ๐ฌ๐ฌ+ ๐ฃ๐ฅ๐ ๐บ๐ฒ๐ฟ๐ด๐ฒ๐ฑ ๐ฏ๐ ๐ฑ๐ฒ๐๐ถ๐ด๐ป๐ฒ๐ฟ๐! ~70% of them are core product and feature work, rest bug fixes and maintenance. ๐๐ฒ๐ฟ๐ฒ ๐ฎ๐ฟ๐ฒ ๐บ๐ ๐ป๐ผ๐๐ฒ๐.
Design is now a very different function at @Razorpay. Product designers don't just own mocks, they own the actual experience in production, designing, building and maintaining it.
6 months back, we decided to revamp how we build software. A big part was design handoffs: an unnecessary collaboration tax in today's world. With the right context and skills, AI can now write great code. So, anyone should be able to build.
So, we reworked our engineering systems and design workflows. We experimented a lot, made some mistakes too, and built an org where shipping is part of every product designer's job.
๐ช๐ต๐ฎ๐'๐ ๐ผ๐๐ฟ ๐๐ผ๐ฟ๐ธ๐ณ๐น๐ผ๐? That's a long answer for here. If you're interested, lmk in the replies and if enough folks are keen, we'd love to do a presentation or video on it!
----------------
๐ค๐๐ฒ๐๐๐ถ๐ผ๐ป๐ ๐ ๐ธ๐ฒ๐ฒ๐ฝ ๐ด๐ฒ๐๐๐ถ๐ป๐ด:
๐ช๐ต๐ฎ๐ ๐ฎ๐ฟ๐ฒ ๐ฒ๐ป๐ด๐ถ๐ป๐ฒ๐ฒ๐ฟ๐ ๐ฑ๐ผ๐ถ๐ป๐ด ๐๐ต๐ฒ๐ป?
Building the systems that let everyone in the org build at scale: Our in-house coding harness, PR review automation, CI/CD automation, and a lot more.
๐๐ผ๐ ๐ฑ๐ถ๐ฑ ๐ฑ๐ฒ๐๐ถ๐ด๐ป๐ฒ๐ฟ๐ ๐น๐ฒ๐ฎ๐ฟ๐ป ๐๐ผ ๐ฐ๐ผ๐ฑ๐ฒ?
They didn't have to learn to code. They learnt the foundations of engineering, thinking like an engineer. It happened through learning sessions and on the job.
๐๐ฟ๐ฒ ๐ฑ๐ฒ๐๐ถ๐ด๐ป๐ฒ๐ฟ๐ ๐ณ๐ฟ๐ผ๐บ ๐ฒ๐ป๐ด๐ถ๐ป๐ฒ๐ฒ๐ฟ๐ถ๐ป๐ด ๐ฏ๐ฎ๐ฐ๐ธ๐ด๐ฟ๐ผ๐๐ป๐ฑ๐?
Some are. Many aren't. We've built a team of generalist designers who are keen to learn anything.
๐ช๐ต๐ฎ๐ ๐ฎ๐ฟ๐ฒ ๐๐ต๐ฒ ๐ป๐ฒ๐ ๐ฟ๐ผ๐น๐ฒ๐? There are two:
1. Design Builders: designers who own the production experience.
2. Design AI Engineers: folks who build the systems and workflows that let designers ship.
๐๐ฒ๐๐ถ๐ด๐ป ๐๐๐ถ๐น๐ฑ๐ฒ๐ฟ ๐๐ ๐ฃ๐ฟ๐ผ๐ฑ๐๐ฐ๐ ๐๐ฒ๐๐ถ๐ด๐ป๐ฒ๐ฟ?
A Design Builder is a very different role from a typical design role. They truly own the production UI, UX, interactions, performance, bugs and quality, in code.
Huge shoutout to the entire @Razorpay_Design team! You took this up, pushed yourselves into a completely new world, took insane ownership and made it happen. ๐โโ๏ธ