<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Widget on The Coders Blog</title><link>https://thecodersblog.com/tag/widget/</link><description>Recent content in Widget on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 08 May 2026 21:06:17 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/widget/index.xml" rel="self" type="application/rss+xml"/><item><title>Gratitude Boosts Widget User Retention</title><link>https://thecodersblog.com/widget-user-retention-driven-by-gratitude-2026/</link><pubDate>Fri, 08 May 2026 21:06:17 +0000</pubDate><guid>https://thecodersblog.com/widget-user-retention-driven-by-gratitude-2026/</guid><description>&lt;h2 id="beyond-functionality-the-unexpected-power-of-emotional-design-on-the-android-homescreen"&gt;Beyond Functionality: The Unexpected Power of Emotional Design on the Android Homescreen&lt;/h2&gt;
&lt;p&gt;For years, Android widgets have been a peculiar beast in the mobile development landscape. They&amp;rsquo;re a persistent, glanceable presence, offering quick access to information or actions, yet often developers lament their creation. The technical hurdles are well-documented: the &lt;code&gt;RemoteViews&lt;/code&gt; paradigm, the strict limitations on view types, the complexities of inter-process communication, and the notorious update delays. Many view them as a necessary evil, a relic of an earlier mobile era.&lt;/p&gt;</description></item></channel></rss>