918: Extreme Native Perf on the Web With Superhuman  ## Metadata - Author: [[Syntax - Tasty Web Development Treats]] - Full Title: 918: Extreme Native Perf on the Web With Superhuman - Category: #podcasts - URL: https://share.snipd.com/episode/8c68b8c9-0022-4246-9f9d-229b483ec8f5 ## Document Notes ## Highlights - **Loïc's Personal Superhuman Journey** - Loïc initially doubted paying $30-$40 monthly for an email app when using Gmail already felt productive. - After three weeks, the fast, delightful experience rewired his perception, making him a Superhuman user and later joining their team. Transcript: Wes Bos Yeah. Loïc Houssier I mean, I was like you. Like I was not using the product before getting in touch with the team. And I was like, how come I would pay for something that is free? I'm using Gmail. I'm a Gmail power user. I like all my setup is done there, like all my filters and all. So I felt productive. I felt productive. And then I tried the product during like when I was chatting with like their teams. And before joining, I was like, yeah, it's nice. It's beautiful. It's fast. Now the question is like, okay, it's better, but would I pay 30, 40 bucks a month to get, I would say, that amount of better? So I was like, no, not sure, not sure. And we keep talking, and I love the people. I love their perspective. I love the vision they had about how the craft should be done and how Delight can basically create a business. And after three weeks, they have this wonderful PLG motion, like product-led growth motion. And they kind of like trick you into using the keyboard shortcuts. So like the education in product was really good. After three weeks i was like holy cow this is fast there's no freaking way i can go back to gmail and i was like okay i need to understand how they do this i need to understand how they basically Make me happy to pay 40 bucks a month uh like for something where the competition is basically free And it's super interesting. ([Time 0:03:17](https://share.snipd.com/snip/f9b0b1db-588a-4982-8a9d-8bd3f0e50753)) - **Hire Product-Focused Engineers** - Hire engineers who are product and design-oriented with a keen eye for user experience details. - Focus heavily on CSS and design principles rather than just technical skills for top-quality UI crafting. Transcript: Loïc Houssier Need a bunch of senior people, you need to hire engineers that are product slash design engineers. So you need people that just have an eye for something that feels off and that can make it right. So we are very intentional in the people that we hire. We don't hire software engineers. Product engineers. Everyone is saying they hire product engineers. But a good portion of our interview process is focused on, especially for the front-end people, is focused on your ability to craft a great user experience. So we just don't want people that are great at whatever the frameworks or all of that, but very CSS-oriented, very detail-oriented. So yeah, you have to be intentional when you hire. And we have a lot of internal trainings, I would say, coming back and recurring about all the engineering principles that we need to apply in the way we work. ([Time 0:09:01](https://share.snipd.com/snip/f4858262-ab62-41b3-8977-7409cfd8e68d)) - **Network Latency is Main Slowness Cause** - The main cause of app slowness is network latency, especially on mobile devices with poor connections. - Performing data operations locally, such as syncing recent emails, yields a much faster and smoother user experience. Transcript: Loïc Houssier And that's why we moved to like offline first. It's not because we wanted to support offline. It's because the number one culprit when it comes to slowness is the network, especially when you're talking emails and you're on your mobile phone, you have a shitty network. You don't want this to be felt on the end users side of things. So we do a lot locally. We do a lot locally. So it might surprise you, but for example, there's a database on your iPhone mobile app. We are not getting the data live. We basically like sync the last 30 days and moving onwards. So we have a huge footprint on your phone so that everything like search can work offline and be like crazy fast. We don't rely on the provider search like Gmail or Outlook, for example, only for stuff that are back in history. ([Time 0:11:16](https://share.snipd.com/snip/c6741e77-96cf-436f-be3f-9b741efe1cc9)) - **Local Database Powers Offline Use** - Superhuman currently uses Realm-like SQLite databases on mobile and local browser APIs for web and desktop. - They sync local data like emails and calendar events to ensure offline functionality and fast access. Transcript: Wes Bos Yeah. I've been getting into a lot of local data stuff myself and sync engines and CRDTs and those types of things. Can you maybe talk a little bit about the tech behind what local database you are using and how the sync process works? Yeah. So take everything with a grain of salt. I'm the VP. I'm not the engineer, neither. I'm the chief architect. Loïc Houssier But so right now we are on mobile. We're using real. But like we are moving away. And we are like at the decision process to understand which tech we will use globally. It's kind of like a SQLite approach. I remember Ram. Yeah. On the browser side, same. So we use an extension. So we have an extension that is used both by the Electron app and the web experience. And we use the browser APIs and everything to basically store locally. And we use some version of SQLite as well to store stuff. We store basically emails, we store your events, agenda, calendaring, everything like this is locally stored. ([Time 0:12:10](https://share.snipd.com/snip/ba2783ea-f007-4f56-a9ef-2ff2c20e4b63)) - **AI Runs Server-Side For Quality** - On-device AI generation is currently too slow and not high quality enough for Superhuman's standards. - They run AI processes on backend servers to ensure fast, accurate draft creation and email classification. Transcript: Loïc Houssier It's like the vector search is only one piece of the feature that you want to provide. So I will give you some example, but we do some draft creation for you. So funny enough, Superhuman moved from being the fastest email app to the most productive email app. And part of the productivity is creating for you drafts that are ready to be sent. Like you don't even have to think about it. Someone asks you a question, we look at your capacity and we provide some answers that hopefully are 90% of the time right. You just have to hit send. Boom, you're done. Typical use case as well. You ask a question to someone and you have some sort of reminder that is ready so that you can nudge people pretty fast without thinking about it. And to do this, we need some tones. We need some information about like the past emails that you sent to those people, and you need to process the email and everything that is generative on device is still relatively slow Right now. So the experience wouldn't be great. So the question is like, are we okay with somewhat like a slow, like generative feature that would make you wait or we just don't allow it at all and coming back to our principles okay is Not good enough so this is like typically the case where devices and models like running on device are not good enough just yet for our quality bar. ([Time 0:14:14](https://share.snipd.com/snip/d22957b1-0491-49ab-8025-ff67ab7f5154)) - **Optimize AI Before App Use** - Precompute AI features like draft creation before opening the app for instantaneous availability. - Use streaming APIs for AI writing features to make responses feel faster than the user can read. Transcript: Loïc Houssier So, so that's one point, like we do it, I think so that it's ready when I would say you open the, uh, I would say you, your superhuman app. So I was mentioning those, uh, drafts or like the classification of your email. Everything is happening on our backend. And when you open the app, all your emails are filtered automatically and the drafts are created. So we try to optimize for those processing that can happen basically before you open the app. Most of the features are like this. We still have some features like augmented writing, like you want to kind of like rewrite like an email because you don't feel right about it. Like you don't want to go to chat GPT and everything. So like, come on J and improve writing, boom, and you have like this being processed. And then it's kind of like using some UX tweaks to make it feel that it's instantaneous. So you cannot just wait with like a spinner saying like, hey, reviewing your comments. So for example, like if you compare to Notion AI, if you're using Notion AI to rewrite some content, it will feel relatively slow, they will basically strike through stuff. So they add some complexity to the user experience, showing they do something. And eventually you accept the modification. We don't do that. Like we basically like write and basically like the streaming APIs are good enough to make things like feel fast. Basically, it's writing faster that you can read. So you don't need those extra stuff and those extra things that Notion is doing, for example. So we try to get rid of the clutter so that the experience feels like really fast. ([Time 0:16:31](https://share.snipd.com/snip/3e7a1051-5377-476c-9507-9c560d96a047)) - **Structure Teams for Fast Shipping** - Organize teams by user domains to enable deep focus and faster shipping of relevant features. - Prepare work thoroughly to keep team flow and velocity high. Transcript: Loïc Houssier And we work hard uh so that's i mean honestly that's that's a part of it like we work hard. And I mean, I have freaking good engineers, to be fair. Most of the team, like the average tenure is probably around like three years on average, with people up to like six to seven years. So we have a bunch of seniority and knowledge that is already in the team, which helps. We are pretty intentional and we try to prepare things so that when we work on things, on features, they are baked already to some extent so that we can keep the flow going. We put in place an organization that is pretty domain centric. So we have three big domains in superhuman, the calendar experience, which is a new one, the triage experience. So we have a team dedicated on the, like the focus that you need to get when you join. Like, for example, you go to Gmail, you have a long list of emails and it's kind of a mess. You have the cognitive load, you need to go through it. So we have a bunch of features like splits, or like automatic archiving of like the clutter so that you can just focus on the right thing. We have a team dedicated to it. And we have a team dedicated with engaging with your emails, where this forwarding, commenting, responding, basically. So those are the three teams. And when you have teams that are like laser focused on their persona, the way they use it, the complaint that they have, it's easier to get velocity because you know your stack, you know Your code base, you know the complaints, you know, like the how people are using it. It makes things, I would say faster. And to be fair, AI is helping a lot. Anecdotal feedback, like it's based on like self, like we did a survey and people were like providing like their own appreciation of like the productivity gain they get from AI. The answers were roughly between 20 and 30% productivity gain. So it's not doubling our capacity just yet, but like significant. ([Time 0:18:39](https://share.snipd.com/snip/7e85f17e-a37c-4860-bc0c-45a4fc714fb6)) - **AI Tackles Email Overload** - Superhuman uses AI to auto-classify and archive marketing or pitch emails, drastically reducing inbox clutter. - Users can customize classification with prompts, combating email overload smartly. Transcript: Scott Tolinski Because this is something I think a lot about right now is that tools like Superhuman allow you to just send a whole lot more email than you normally would. Because it, you said it will generate drafts, right? So there's there's like this new area of it's not necessarily spam but it's just like this like generated cold outreach that i get i probably got 15 already this morning and i'm i'm kind Of at my wits end with my email right now i'm just i'm sick of it because it's it's so hard to find what is important so i'm curious like like do you have any thoughts about how email in the Future is going to look both from sending lots more because it's good for business but then on the inbound having to be offensive and try filter for filter all this crap out no no, no. Loïc Houssier I mean, this is a good point. One thing that was interesting, before talking about the future of emails, if you look back, what was the past of email? Our customer base, 90% of our users are using Gmail, and the enterprise customers are on Outlook, roughly. So that's kind of like the 90-10 is like the way we think about it. Think about Gmail. Gmail has no interest in getting rid of the spam or the marketing spam. Because, of course, Gmail is a marketing engine. Google is a marketing engine. And that's why we say they are kind of like bread and butter. So they cannot just help you only receive what makes sense for you. Like they need that volume of data. We don't care because that's not our pricing strategy. That's not the way we make money. And that's coming like today. Like this is what you have right now. We, and especially using AI, it's so much easier to detect whether an email is a pitch. Like your company reaching out to you to sell you like the new CI, CD tool that they've been working, they're out of YC, whatever, and they want to pitch you. Or like those marketing emails, because you use GitHub or GitLab on a daily basis, they send you like some marketing content associated with like the new features and all of that. Yeah, pardon my French. That close, that close. But we all get like all those emails and honestly to be efficient. And especially when you're a C-level, there are some stuff that are really crazy important and that clutter that you would love to get rid of. And now we get rid of it. Like our users, like everything that is marked as a pitch or marked as marketing email, you can select auto archive it. So you don't even see it. It's not even showing up in your email. And then you can do some pretty like nice thing. Now you can prompt the classification. You can say like, oh, you know what? Everything that is like podcast related or everything that is coming from my board, as wide as this. And my board are people like this and this and this. So you can write prompts now in Superhuman to classify your email so that you can say, this is important. This is important. And it's working great. It's working great. ([Time 0:20:53](https://share.snipd.com/snip/acc767ff-40ca-47ef-b16a-888993c59229)) - **AI Search Helps Citizenship Application** - Loïc used AI search to find his travel email details to complete a US citizenship application. - This practical example shows how AI search can significantly improve email utility in everyday life. Transcript: Loïc Houssier Use this AI search like almost on a daily basis because like a lot of my knowledge and content is in my email. The last example, over the weekend, I was working on my citizenship application. And for the people that are going through this, like in the U.S., you need to go through the last five years of travels outside of the U.S. And I was like, oh, damn. I remember like I went to Japan. I don't remember the dates. Hey, can you find the tickets for my trip in Japan that I believe happened in around that timeline boom boom boom and I get those emails and I have the dates and done like I was done with it So this is like silly examples but like AI search is definitely something that is I would say crazy good the the next piece that will be like very interesting and probably will ship that Early Q3 is like someone asking like a friend of you already in your like I would say, indoor list of contact and all of that, asking for like a slot. And like, hey, can we meet somewhere next week, please? We have access to your calendar. We have access to your availability. ([Time 0:25:33](https://share.snipd.com/snip/deac4f68-1475-447a-b3c5-404353b95a3e)) - **Create Hidden Delightful Features** - Implement UX features that feel seamless and contextual, like auto-opening calendars when a date is detected in emails. - Keep the interface sleek by hiding new features initially and letting users discover them with use. Transcript: Loïc Houssier This is the type of features that might feel overkill for like a typical B2B SaaS company. They would be like, nah, let's not do like a feature like this. Like people can click on the calendar and go to that. Like they can do it. There's a way. And this is where like we have a CEO founder that is kind of like an art director to some extent, and has like a product test and understand what are the features that will create delight In the end user. And this is typically one, you open this calendar, and boom, we can, we see there's a date. And it's not that complex to find a date like in a text and boom, you open like the sidebar, and it's probably working 95% of the time, but it's just delightful because you feel you're in The context. And this is something that is really important. You were mentioning the fact that we have a lot of features, but we are not cluttering the experience. The experience still looks sleek. There's not a lot of buttons. Like we are not adding like a new button. Like every time there's a new feature, we want this to be discoverable, but hidden, I would say, first. So you need to kind of like learn to use them so that the experience always feel sleek and like you are always like in the focus mode. ([Time 0:27:46](https://share.snipd.com/snip/e782c5ff-bf8f-4e91-b70c-b6679ca019a8)) - **Product Taste Grows With Mentorship** - Product taste is a critical but hard-to-teach skill cultivated by mentorship and exposure. - Superhuman's founder Rahul models this taste, shaping product quality and design reviews that raise standards. Transcript: Loïc Houssier Is something that you need someone to teach you to some extent. And Rahul is probably the person that has the most impressive product taste. So he's doing every single product reviews and design reviews in the company. Kind of like the Brian Chipsky of the world at Airbnb. Like it's kind of like a version of that. I don't want to enter like the founder mode like discussion. Like it's a really great founder that we have and we love him. But he has that. He always has those questions. He always try to understand like how far are you from getting to that wow moment? Like how many steps to hit? And I've been here like only six months. And now I'm asking those questions. Now I'm looking at the demo that my team now are doing. I'm like, feels clunky, doesn't feel superhuman, feels too complex. We need to do something um like this so it's it's kind of like trained to some extent by being exposed to rahul that has that uh as a i don't know if he learned it the gift but it's different It's a gift i think it is i think it is uh but like the same way i would say when you work with someone that is just great uh and you get mentored and you see how they operate you start to build A muscle and you start to build, I would say, that taste. It's kind of like drinking wine. You drink shitty wine at first, you start to have a better taste about it and you meet someone that is just great at explaining why it feels better. ([Time 0:30:10](https://share.snipd.com/snip/c7c0e8f4-c2e3-4768-b2ac-745f657e9a3e)) - **Dark Mode Costs Complex Changes** - Superhuman's dark mode ('carbon') is not a full true dark mode and was developed to meet user requests. - Implementing a proper dark mode is complex due to bespoke UI and requires rethinking every interaction locally. Transcript: Loïc Houssier Very true. It was mostly made for white and clear mode for a long time. And then we basically implemented the dark mode because of the request, but we didn't do it everywhere. And as we are not heavy on design systems, making those changes takes time. And we want to optimize locally. So every single interaction needs to be thought through with dark mode now, like in mind. But no, I'm with you. I'm with you. And you know what? Even worse, I'm an Android user. And Android is lagging behind iOS. So like for my team, I complain about like the two things that are lagging. ([Time 0:32:20](https://share.snipd.com/snip/54642c20-38a6-480e-97c1-3cc39fc7e91e)) - **Teach Keyboard Shortcuts Gradually** - Educate users gradually to master keyboard shortcuts for faster email management. - Keyboard shortcuts outperform voice commands for quick actions like archiving or forwarding emails. Transcript: Loïc Houssier Are able to utilize these features effectively? This is a great question, and this is a question we have internally because our initial ICP, so the ideal customer profile, was the Bay Area, or by extension, tech industry funder. So usually young, usually tech-savvy, and highly productive and wanted to gain some time. So those people were the right target to get like keyboard shortcuts and everything. They were like looking for it and even like expecting it. It's more clicky now as we were like more and more present on the market. So basically all startups were and still are using like superhuman those startups got acquired by bigger groups and you see those like c level of startups being acquired complaining I would say to the bigger group saying like no no no we want to keep it so now we have like big companies basically saying to us hey guys we need to standardize and superhuman but like not All the population is tech-savvy like this. What do you propose? And that's something that is tricky to some extent. And this is where I was mentioning in the beginning, the PLG motion and the education motion is something that is very important for us and our success because even the people that are Not that tech-savvy, if you go through basically those in-product education moments, you get used to it. And you're like, oh, damn, it's easy. Like, enter. Anyone can do enter. And then you start with enter. And then maybe you start with like the E, which is archiving things. Like, oh, archiving works well and maybe you use that one and then you learn about the second one maybe like weeks later so the curve of the addition is might be might be like a bit slower For the non-tech savvy people but eventually like the the speed at which you operate with those keyboard shortcuts is crazy and it's interesting because there's a lot of discussion About like the change of user interaction with devices and voice becoming more and more important. I still believe that keyboard shortcuts would be so much easier than voice for doing the archive forward and things like this. So yes, we are talking about it. Not yet to the point where we want to add a lot of ribbon. I can't imagine having a ribbon with different actions for people that are very out-looking to some extent can feel that, oh, yeah, that's the same or close enough. ([Time 0:33:40](https://share.snipd.com/snip/fb082bb8-8557-4015-971f-83fcd87a0025)) - **Shortcut Helps Achieve Inbox Zero** - Loïc uses "H" shortcut to hide emails and reschedule them easily, enhancing Inbox Zero achievement. - This workflow clears cognitive burden by deferring non-urgent emails precisely when needed. Transcript: Loïc Houssier I use the most. So H to basically like make your email disappear and only come back when you believe it will make sense. Good example is like, oh, I don't want to treat that today. I want to focus on this tomorrow. So HT, enter, boom, your email is gone. And T for tomorrow. That's probably the one that I use the most, like next week, next month, or like, I would say today or tomorrow at 2pm. So that's, I would say the type of things that I use a lot because I want to reach inbox zero. Whereas like one thing like that is really key for our users is reaching inbox zero, because you just get rid of the cognitive load. And when you reach that point where you have nothing, like, oh, everything has been treated, and you don't have to mark stuff and read because you want to get to it at some point and everything, Which is like the typical flow for like Gmail or Outlook, it feels so great. And to do this, basically, you postpone for to when it makes sense so usually like oh yeah i know that i want three to treat like those type of emails on friday hf and friday bim it's done And um one second and it's ready so you can go through like a hundred of emails a day which is roughly said what i receive uh this into like 15 minutes at the end of the day. ([Time 0:37:10](https://share.snipd.com/snip/1e29da90-84c1-4757-b1b5-efb60fc68372)) - **Superhuman Boosts Productivity** - Superhuman users save an average of four hours per week and reply 48 hours faster via the app. - The app is more beneficial for leadership and freelancers managing many emails than typical engineers. Transcript: Loïc Houssier I tend to hate email so yeah everyone hates email everyone hates email um so so that's a good way and interestingly and maybe like the last plug i would say for superhuman but uh what we See is in the uh i would say our customer base is like they save like four hours a week. So it doesn't apply to, I would say if you're a typical engineer with like in a big team, so you don't manage third parties, you don't manage a board, you don't manage like a lot of people, You will be probably living your life in Slack. Way more and hopefully in Slack and not in Teams or like any other one. So that might not apply. But when you start to be in leadership roles or your role, maybe you're a freelancer and you spend, I would say, a lot of time in emails night and day. So four hours a week, this is typically what people save. And they reply usually 48 hours faster than before. So that's the type of metric that we have. ([Time 0:39:30](https://share.snipd.com/snip/1e49a188-584c-47c4-874c-3a62f7eb4468)) - **Delight Requires Costly Local Architecture** - Investing in speed and delight requires costly local-first architectures with complex sync engines. - Superhuman accepts this because the superior user experience retains users despite higher development challenges. Transcript: Wes Bos Right. And you made your check technical choices to align with that, to use local data. And through that, you've created a product that delights people. It is fast as hell and overall like really feels good to use. And I, I, I've been talking a lot about local data on this show, and I think that's like an important thing is that oftentimes we think about, well, I'll use local data, but like you all Started with the experience, what experience needs to be there, and then that probably determined to use the local data and then the keyboard shortcuts and all these things. And it really really uh i think worked out in a great way for you all so but it has a cost like one thing that is really important for people to understand like if you're starting your company Loïc Houssier And this has like a freaking cost like you need to basically understand that delight and like that speed is something that is an investment we are native uh most like for iOS and Android For that purpose. Being native has a cost. We could have used Flutter or whatever, like all the framework to basically build once and use everywhere. We decided to be like very intentional. We, I would say, are local first. So you were talking about like sync engines. Like syncing is probably like the number one, not pain, but like challenge that we have that is tricky because you have network, no network. So you have some sort of like a pub sub like mechanism on every single device in every single platform that we are using. But that's typically business logic that you would typically provide and only once in your back end or your back end for front end, like whatever the architecture that you following. But typically in a B2B SaaS company that doesn't care about speed, you would manage that there and manage like the pub sub like on the back-end. But we want to be offline first. So you need to have that approach on the local device. It has a cost. Every time we want to do some modification about syncing, so you were talking about Kanondar. Number one, I would say feature of all our users, like they are, bring us calendar the same way you save email, and we are working on it. But it means that on every single device, we need to kind of like adapt our like thinking engine for managing like the different events to work with the API of Outlook and Gmail. So it has a cost. It has a cost. But we do believe that this cost is worth it because, I mean, we have like our users, they love the product and they don't go elsewhere because the experience is so great. ([Time 0:40:47](https://share.snipd.com/snip/9a4a18a9-9d06-4126-bf2b-0beaaa500b0a)) - **Modifier Stack Powers Sync Engine** - Sync engine uses a modifier stack logging all user actions locally for offline support and undo capability. - Actions sync with backend and then propagate to email providers when network is available. Transcript: Loïc Houssier Of modifiers. So it's roughly said a pub sub mechanism. So when we want to archive an email, so we have a modifier that we basically log like every single stuff that you're doing on that email, archive, unarchived, archived, unarchived, If you want to play with it. On top of it, we have like the undo capacity. Like we give you like 10 seconds because, oh shoot, I made a typo, a typo, and I didn't use AI to rewrite my email. No, no, no, no, no, Z, so that you don't send the email. So, like, you need to have, like, basically like a stack of actions that you can go through, and we want to implement that offline, so it needs to be present on every single device. So, we call that modifier, and it's roughly said like a stack of actions that will be synced. I would say as soon as you have the network, it will be synced with the backend that implements also those modifiers and will then implement the changes in Gmail or in Outlook. ([Time 0:43:40](https://share.snipd.com/snip/ea8973be-4ce5-43cb-ae3d-4457296dd361)) - **Frontend Engineers Handle Backend Logic** - Frontend JavaScript engineers split into UX specialists and background sync/platform engineers. - Device-side backend logic handles race conditions and eventual consistency usually seen in server backends. Transcript: Loïc Houssier Like one interesting thing is like our front-end engineers and like JavaScript engineers. We have two kinds of engineers, like people working on the UX and the people working on what we call the background, which is kind of like the backend of the local stacks. And we have like a platform team that is usually treating those like nitty gritty, almost like back-end problems on the device because it's, I mean, you face like the same race conditions, The same like eventual consistency of shit that you, sorry, this time I said it, like that you have typically on the back end uh which is not typically common for like javascript users Unless you're using node on the back end but we are go shop sec west do you have anything else you want to get to here no i think that's good i was i was specifically going to ask about that Scott Tolinski Of like like the logic layer and the u layer, but you pretty much just answered it. So that's really interesting when it's, when most of the code runs on the device, there's not really a backend, right? ([Time 0:44:50](https://share.snipd.com/snip/699f8bf9-1d68-4ab6-b5d9-442c0e949968)) - **Offline Resilience During Outage** - During the Google and Cloudflare outage, Superhuman users could still send emails offline that synced later. - Only new email reception failed; users experienced seamless sending despite backend bugs. Transcript: Loïc Houssier Correct. Scott Tolinski Did you have downtime and what did that look like for your app? Loïc Houssier So this is a great question so we are offline first yeah so which means that during that outage the only problem that you had was that we couldn't receive new emails because like google Was basically down uh so like gmail was downish so receiving new emails was not possible but we stack everything. So we had to replay, transparent for our user. They send emails, like everything that is email answering, email sending and all of that, totally transparent because it's managed locally. And then it's like going to our backend when they have the network and the backend is kind of like replaying everything. So we had like a long stack of emails that were waiting for the outage to be done and we basically managed that. We had some issues because of the attachment and there were some issues with attachment because like we had one bug. So it was like an incident, not an incident, like it was an incident internally, but like not seen by our end users. So we're used to it like Outlook, like their Graph API tends to break every new version because they are, I don't know what they're doing, but like they break stuff relatively often. But it's mostly not seen on our side. So the only impact is like you will have like a small notification, hey, Gmail is facing some issues. ([Time 0:46:59](https://share.snipd.com/snip/99f56ebe-f9bb-4ce4-805b-9a433c95fefe))