<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>GraphQL - Tag - Sandesh Damkondwar</title><link>https://sandesh.work/tags/graphql/</link><description>GraphQL - Tag - Sandesh Damkondwar</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>sandeshdamkondwar@gmail.com (Sandesh Damkondwar)</managingEditor><webMaster>sandeshdamkondwar@gmail.com (Sandesh Damkondwar)</webMaster><lastBuildDate>Wed, 21 Dec 2022 00:00:00 +0530</lastBuildDate><atom:link href="https://sandesh.work/tags/graphql/" rel="self" type="application/rss+xml"/><item><title>How we redesigned and rearchitected our Merchant Experience</title><link>https://sandesh.work/redesigning-rearchitecting-merchant-experience/</link><pubDate>Wed, 21 Dec 2022 00:00:00 +0530</pubDate><author>sandeshdamkondwar@gmail.com (Sandesh Damkondwar)</author><guid>https://sandesh.work/redesigning-rearchitecting-merchant-experience/</guid><description><![CDATA[<p><em>Originally published on <a href="https://engineering.razorpay.com/redesigning-rearchitecting-the-merchant-experience-d788bb44e526" target="_blank" rel="noopener noreffer ">Razorpay Engineering</a></em></p>
<p>Journey on how we made the merchant experience better — Part 1: Engineering Process</p>
<p></p>
<h2 id="tldr">TL;DR</h2>
<p>At Razorpay, we were experiencing user dropouts for a variety of reasons, particularly during the onboarding process, which resulted in an 89% user dropout.</p>
<p>Because of the architecture limitations, it was hard and challenging for us to give merchants a better experience that was fast, consistent, and had few dropouts.</p>]]></description></item></channel></rss>