<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Local-Caching on DRM HSE</title><link>https://www.drmhse.com/tags/local-caching/</link><description>Recent content in Local-Caching on DRM HSE</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 15 Jul 2026 12:43:37 +0300</lastBuildDate><atom:link href="https://www.drmhse.com/tags/local-caching/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Review-Focused Flutter Client for Jules</title><link>https://www.drmhse.com/posts/building-jules-flutter-client/</link><pubDate>Sun, 10 May 2026 09:00:00 +0300</pubDate><guid>https://www.drmhse.com/posts/building-jules-flutter-client/</guid><description>&lt;p>I built a Flutter client for Jules because I wanted the review work to stay beside the conversation that produced it.&lt;/p>
&lt;p>A Jules session is more than a sequence of messages. It can include a plan waiting for approval, progress updates, repository context, and a patch to inspect. In a narrow chat view, those parts compete for the same space. On a desktop, they can remain visible together.&lt;/p>
&lt;p>The first version of my client therefore uses three panes: session history, the activity timeline, and a code diff. It also caches sessions locally so reopening the app does not begin with an empty screen.&lt;/p></description></item></channel></rss>