<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>UX on Sunil Kumar Pashikanti</title><link>https://sunilpashikanti.com/tags/ux/</link><description>Recent content in UX on Sunil Kumar Pashikanti</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 09 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sunilpashikanti.com/tags/ux/index.xml" rel="self" type="application/rss+xml"/><item><title>Beyond the 91MB Payload: Architectural Image Optimization in Power Apps</title><link>https://sunilpashikanti.com/posts/beyond-the-91mb-payload-architectural-image-optimization-in-power-apps/</link><pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate><guid>https://sunilpashikanti.com/posts/beyond-the-91mb-payload-architectural-image-optimization-in-power-apps/</guid><description>As a Solutions Architect, I often see Canvas Apps struggle under the weight of high-resolution media. In a recent project, we encountered a significant performance bottleneck: a &amp;#39;91MB Payload&amp;#39; issue where standard image controls were forcing browsers to download massive JPEG/PNG files, leading to memory crashes and sluggish gallery scrolling.</description></item></channel></rss>