NYLAS MAIL APP UPDATE
You’ll need to use a poll-based sync architecture as that is a limitation of Google’s contacts APIs.Ĥ.Build code to diff & update complex, interrelated objects like email addresses, IM addresses, web pages, and phone numbersĥ.
Ongoing maintenance that you pay down over time.Edge case handling: extremely large messages, weird attachment formats, messages that have broken MIME-types or are otherwise spec-noncompliant (this is a big, ongoing project) A normal case is easy, but when a MIME type isn’t specified properly it’s much more complicatedĩ.Make sure your database is truncating long headers in a way that doesn’t lose valuable informationĨ.Adding HTML tags in the right places to make it format / display properly The basics are easy, but extracting the character set from the right place in MIME and converting it is time consuming.You’ll have to investigate rate limiting by bandwidth, per-user, for this project, by account, or something else. The Google APIs have multiple rate limits and don’t tell you what rate-limits you hit.Properly handle rate-limiting / 429 errors Attachment storage and handling, including encryptionĤ. Handle performance and integration with the sync componentsģ.Handle scaling (you can easily DDoS yourself if you don’t know what you’re doing).Add support for Google push notifications (this is a big project) Build email sync functionality, starting w/polling the Gmail API for the data that you needĢ. Properly handling the case where a user only grants a subset of the requested permissions, which is now an option that Google supportsġ. You have to handle them to make sure you’re not stopping syncing accounts when they should still sync.ħ.These issues often translate to 500 or 403 errors coming from Google.Roughly once a year, Google makes a bad code push that breaks their auth APIs.Implement logic to handle reliability issues and outages from Google Implement logic to properly handle revoked refresh tokensĦ. Implement logic to refresh access tokens when needed & notifying usersĥ. Build the system so it’s prepared to handle a security leakĤ.Build logic to handle edge cases and secret re-encryption.Gain or develop knowledge about cryptography, symmetric encryption algorithms and which ones to use.Implement secure storage for Google refresh tokens Implement Google auth flow & create screens for callback workflowģ. Create and configure a Google Project to allow access to the Gmail APIĢ.
Here are the simplified steps required to build a complete authentication flow:ġ. It’s also the very first experience users see when asked to authenticate sensitive data – so you want to make sure it’s handled smoothly and securely. See integration steps broken down into detail below, or view the high-level infographic overview here.Īuthentication is a critical step required to integrate Gmail data into your app. In addition, Nylas comes with pre-built security features that provide a more secure, reliable connection than you’d get integrating with the service providers directly – out of the box, we’re SOC 2 certified, GDPR compliant, Privacy Shield certified and HIPAA and FINRA ready.
NYLAS MAIL APP FULL
With Nylas, it takes just 18 days to build full email, calendar, and contacts integrations with 100% of providers. That’s over 1.5 years for a talented team of 7 senior engineers to scope the project, test it, build a POC, pursue the security certifications, push the POC live, and maintain the integration(s). On average, it costs $2,035,044 and 30,834 developer hours to build a Nylas equivalent that connects your application to 100% of email, calendar, and contacts providers.
0 kommentar(er)
