<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Andrii Kolodiichyk on Medium]]></title>
        <description><![CDATA[Stories by Andrii Kolodiichyk on Medium]]></description>
        <link>https://medium.com/@kolodiichyk?source=rss-14068ac16a50------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*US8-AZ2p0KOP6rowFFCkmw.jpeg</url>
            <title>Stories by Andrii Kolodiichyk on Medium</title>
            <link>https://medium.com/@kolodiichyk?source=rss-14068ac16a50------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:21:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kolodiichyk/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Pysar: A Cross-Platform Report Engine for .NET]]></title>
            <link>https://medium.com/@kolodiichyk/pysar-a-cross-platform-report-engine-for-net-3b23226495b1?source=rss-14068ac16a50------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b23226495b1</guid>
            <category><![CDATA[dotnet-core]]></category>
            <category><![CDATA[report]]></category>
            <category><![CDATA[ide]]></category>
            <dc:creator><![CDATA[Andrii Kolodiichyk]]></dc:creator>
            <pubDate>Sun, 06 Sep 2026 14:15:28 GMT</pubDate>
            <atom:updated>2026-09-26T10:43:40.211Z</atom:updated>
            <content:encoded><![CDATA[<p>Describe a paginated document once, in XAML or C#. Get a vector PDF, bitmap pages, or a zoomable viewer — on Windows, macOS, Linux, Android, iOS and in the browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wQ9fUikZwghBYdNYV2KKJQ.jpeg" /></figure><h3>The problem worth restating</h3><p>Generating a paginated business document from .NET — an invoice, a statement, a certificate — is a solved problem, but the existing solutions each solve it with a condition attached.</p><p>Some are Windows-only, which is a dead end the moment a service moves to a Linux container or the same report has to render inside a MAUI app. Some are inseparable from a visual designer, which is fine until the report’s structure depends on runtime data and you need to compose it in code. And some are priced per developer, which turns a routine feature into a procurement conversation.</p><p>None of these are unreasonable business models. They are just constraints, and I had a use case where all three were binding at once: the same report definition had to run server-side into a PDF, and render inside a desktop and a mobile client, on machines that were not all Windows.</p><p>So I wrote the engine. It’s called <strong>Pysar</strong>, it’s MIT licensed, and it’s on NuGet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qIp2-Y8cpPA_6F_cCyNsKw.png" /></figure><h3>The shape of the thing</h3><p>Pysar has one object model and two ways to author against it.</p><p>The layout, pagination and rendering engine is plain .NET on top of <strong>SkiaSharp</strong>. That choice is the whole reason the cross-platform claim holds: Skia is the same rasteriser and the same text shaper everywhere, so a report measured on a Linux build agent paginates identically to the same report measured on an iPhone. There is no ‘<em>System.Drawing’</em>, no GDI, no platform text stack in the layout path.</p><p>What the host application supplies is deliberately small — a single ‘<em>IReportPlatformHandler’</em> covering the two things that are genuinely platform-specific: where files come from, and which fonts are available. Everything above that is shared code.</p><pre>var report = ReportBuilder.Create(&quot;Hello report&quot;)<br>    .WithPageFormat(new PageFormat { Margin = new Thickness(30) })<br>    .WithDetail(detail =&gt; detail.AddElement(new Text { Content = &quot;Hello from Pysar&quot; }))<br>    .Build();<br><br>await new SkiaReportRenderer().SavePdfAsync(report, &quot;hello.pdf&quot;);</pre><p>Everything is measured in points (1/72&quot;). A4 portrait is 595.5 × 842 pt.</p><h3>Bands, not a canvas</h3><p>A report is a vertical stack of bands — report header, page header, detail, page footer, report footer — and the detail band is the one that repeats over your data. Inside a band you compose the familiar layout primitives: ‘<em>Grid’</em>, ‘<em>StackPanel’</em>, ‘<em>Frame’</em>, ‘<em>Text’</em>, ‘<em>Image’</em>, plus ‘<em>Repeater’</em> for nested master-detail grouping.</p><p>This is an old idea and it is the right one for paginated documents, because it makes pagination a property of the model rather than something the author has to think about.</p><p>Detail rows are sliced across pages, detail headers can repeat on every page, page bands are re-resolved per page, and ‘<em>PageNumber’</em> / ‘<em>PageCount’</em> are available both to bindings and to an ‘<em>OnPageChangedAsync’</em> hook.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aemxGl-ODq8Nla3w8G3ZuA.png" /></figure><h3>Two authoring styles, one tree</h3><p>For a report with a fixed shape — the invoice, the statement, the certificate — markup reads better than a chain of method calls, and it stays editable by someone who isn’t writing C#: a template stored in a database, or edited through a design-time preview.</p><p>That’s what ‘.<em>rxaml</em>’ is for.</p><pre>&lt;Report xmlns=&quot;https://mriyalab.com/pysar&quot; x:DataType=&quot;local:Invoice&quot;&gt;<br>  &lt;PageFormat Size=&quot;A4&quot; Margin=&quot;30&quot; /&gt;<br><br>  &lt;ReportHeaderBand&gt;<br>    &lt;Text Content=&quot;{Binding Company.Name}&quot; FontSize=&quot;18&quot; FontStyle=&quot;Bold&quot; /&gt;<br>  &lt;/ReportHeaderBand&gt;<br><br>  &lt;DetailBand DataSource=&quot;{Binding Items}&quot;&gt;<br>    &lt;DetailBand.DetailHeader&gt;<br>      &lt;Text Content=&quot;Product&quot; FontStyle=&quot;Bold&quot; /&gt;<br>    &lt;/DetailBand.DetailHeader&gt;<br><br>    &lt;Grid ColumnDefinitions=&quot;*, 80, 80&quot;&gt;<br>      &lt;Text Grid.Column=&quot;0&quot; Content=&quot;{Binding Product}&quot; /&gt;<br>      &lt;Text Grid.Column=&quot;1&quot; Content=&quot;{Binding Quantity}&quot; /&gt;<br>      &lt;Text Grid.Column=&quot;2&quot; Content=&quot;{Binding Total, StringFormat=&#39;{0:C}&#39;}&quot;&gt;<br>        &lt;Text.Triggers&gt;<br>          &lt;DataTrigger Binding=&quot;{Binding Total}&quot; CompareType=&quot;GreaterThan&quot; Value=&quot;1000&quot;&gt;<br>            &lt;Setter Member=&quot;FontColor&quot; Value=&quot;Chocolate&quot; /&gt;<br>          &lt;/DataTrigger&gt;<br>        &lt;/Text.Triggers&gt;<br>      &lt;/Text&gt;<br>    &lt;/Grid&gt;<br>  &lt;/DetailBand&gt;<br>&lt;/Report&gt;</pre><p>For a report whose structure is computed at runtime, the fluent builder is the better fit. Both produce the same tree, and they can be mixed.</p><p>Reports can also be loaded from a string at runtime, which is what a user-editable template actually needs:</p><pre>using Pysar.Xaml;<br><br>var report = ReportXaml.Load(&quot;&quot;&quot;<br>    &lt;Report xmlns=&quot;https://mriyalab.com/pysar&quot;&gt;<br>      &lt;PageFormat Size=&quot;A4&quot; Margin=&quot;30&quot; /&gt;<br>      &lt;DetailBand&gt;<br>        &lt;Text Content=&quot;Hello from XAML&quot; /&gt;<br>      &lt;/DetailBand&gt;<br>    &lt;/Report&gt;<br>    &quot;&quot;&quot;);<br><br>report.Build();</pre><h3>Bindings resolve once — a report is a document, not a UI</h3><p>This is the design decision that most distinguishes Pysar from a UI framework it superficially resembles.</p><p>In WPF or MAUI, a binding is a live subscription: the source changes, the visual updates. In Pysar, ‘<em>{Binding}</em>’ resolves <strong>once, at build time</strong>. ‘<em>Report.Build()’</em> walks the tree, resolves bindings, expands repeaters and applies triggers, and what comes out is a finished document.</p><p>There is a rule that follows directly from this, and it’s worth knowing before your first ‘<em>NullReferenceException’ </em>— adjacent surprise: ‘<strong><em>Build()</em>’ mutates the tree, so a ‘<em>Report</em>’ instance can be built exactly once.</strong> Create or load a new instance per document.</p><p>Building the same one twice throws, on purpose — a silent second build would produce a subtly wrong document, and a loud exception is the better failure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d-cKPAK8WF-nlKX26kxmOw.png" /></figure><h3>Binding validation at compile time</h3><p>A typo in a binding path is the classic reporting bug: it surfaces as a blank cell in production, in one document out of a thousand, months later.</p><p>The ‘<em>Pysar.Xaml’</em> source generator validates ‘<em>{Binding …}’</em> paths — and ‘<em>DataTrigger.Binding’ </em>— against a declared data-context type at build time. The hint is the MAUI-style directive you already know:</p><pre>&lt;Report xmlns=&quot;https://mriyalab.com/pysar&quot; x:DataType=&quot;local:Invoice&quot;&gt;</pre><p>An unknown member is a ‘<em>PQX010’</em> error. A type the generator cannot resolve is a ‘<em>PQX011&#39;</em> warning. ‘<em>x:DataType’</em> is inherited down the tree until another element declares its own, and ‘<em>x:DataType=’</em> clears it for a subtree. An element with a `DataSource` puts its content children in a per-item scope over the collection’s element type, while its property elements — ‘<em>DetailBand.DetailHeader</em>’ and the like — stay in the outer scope, so the generator follows the scope you actually meant.</p><p>The validation runs even for reports loaded at runtime, as long as the markup is in the project. And where the scope genuinely cannot be known, nothing is reported rather than guessed: styles and resource dictionaries are reused across scopes, so their bindings are never validated. A false error in a report engine is worse than a missing one — it teaches people to ignore the diagnostic.</p><p>For application projects, the generator also provides ‘<em>InitializeComponent()’</em>, strongly typed ‘<em>x:Name’</em> fields, and compiled object construction via the standard ‘<em>x:Class’</em> directive. Resources, styles and triggers currently fall back to the runtime loader.</p><h3>Output: vector PDF, or pixels</h3><p>‘<em>SkiaReportRenderer</em>’ writes a built report as a <strong>vector</strong> PDF. Text stays selectable and stays sharp at any zoom, because nothing is rasterised on the way out.</p><pre>report.Build();<br><br>// straight to a file<br>await new SkiaReportRenderer().SavePdfAsync(report, &quot;invoice.pdf&quot;);<br><br>// onto any stream — an HTTP response body, for instance<br>await new SkiaReportRenderer().RenderToPdfAsync(report, httpContext.Response.Body);<br><br>// or as bytes, to attach to an email<br>byte[] pdfBytes = await new SkiaReportRenderer().RenderToPdfBytesAsync(report);</pre><p>On a platform package, the same output is reachable through `IReportExportService`, which makes it injectable and lets `ExportFormat` stand in for a future non-PDF format without changing call sites:</p><pre>byte[] pdfBytes = await exportService.ExportAsync(report, ExportFormat.Pdf);</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HVibu5TynXEl9fqMol_mng.png" /></figure><h3>One viewer, four UI frameworks</h3><p>Displaying a report is where a cross-platform engine usually fragments into four independently buggy controls. Pysar avoids that by putting the hard part — page geometry, zoom, tile planning and the tile cache — in a framework-neutral</p><p><em>‘Pysar.Viewer’</em> core, and giving each platform a thin ‘<em>ReportView’</em> over it with the same properties everywhere.</p><p>The core idea is <strong>tiling</strong>: only the visible region is rasterised, so memory follows the size of the viewport rather than the zoom level. A reader who zooms to 500% on page 40 of a 200-page statement is asking for a screenful of pixels, not for the document at 500%.</p><p>The per-platform layer is then mostly input and asset plumbing:</p><ul><li>.<strong>NET MAUI</strong> — fonts and images as ‘<em>MauiAsset’</em> items, read straight from the app package with nothing extracted to disk. Pinch zooms around the fingers; a double tap toggles between fit-width and close-up, both anchored where the gesture happened. ‘<em>IReportSharer’</em> and ‘<em>IReportPrinter’</em> reach the platform share sheet and print dialog.</li><li><strong>Avalonia</strong> — assets via `avares: ‘Ctrl/Cmd’ + wheel zooms around the pointer.</li><li><strong>WPF</strong> — Windows only, assets from pack URIs and assembly manifest resources.</li><li><strong>Blazor</strong> — the browser has no file system, so assets are fetched up front and held in memory. That is not a preference: fonts are loaded synchronously, and a blocking read on the browser’s single thread is a deadlock, not a stall.</li></ul><pre>var files = await PreloadedFileSystem.FetchAsync(http, [<br>    &quot;Fonts/Ubuntu-Regular.ttf&quot;,<br>    &quot;Images/logo.svg&quot;<br>]);<br><br>WasmPlatformHandler.Install(files);</pre><p>One detail I’ll flag because it’s the kind of thing that costs an afternoon: on macOS, Avalonia delivers no pinch gesture. Measured across two branches, 11.3.12 and 12.1.1, a trackpad pinch produced only wheel events and not a single `PinchEvent`. So the zoom comes from an AppKit local event monitor for `NSEventTypeMagnify`, reached through the Objective-C runtime, and it’s a no-op on every other platform. It is also the one part of the viewer no test can reach — an exception crossing the native boundary ends the process rather than raising — so it carries a comment telling you to verify any change by hand, on an actual trackpad.</p><h3>Packages</h3><p>A consumer names at most three: `Pysar` always, `Pysar.Xaml` for markup, and one platform package.</p><pre>| Package | Responsibility |<br>| --- | --- |<br>| `Pysar` | Reports, bands, layouts, repeaters, styles, triggers, binding, and the SkiaSharp measurement / pagination / rendering / PDF engine |<br>| `Pysar.Xaml` | `.rxaml` runtime loader and the code-behind source generator |<br>| `Pysar.Viewer` | Framework-neutral viewer logic (arrives transitively) |<br>| `Pysar.Maui` | MAUI: app-package assets, fonts, PDF export, sharing |<br>| `Pysar.Avalonia` | Avalonia: `avares://` assets, fonts, report view |<br>| `Pysar.Blazor` | Blazor: viewer component, printing through the browser |<br>| `Pysar.Wpf` | WPF (Windows only): pack/manifest assets, fonts, report view |</pre><h3>What isn’t done yet</h3><p>Being straight about the edges, because a launch post that only lists strengths isn’t useful to anyone deciding whether to adopt this:</p><ul><li><strong>.NET 10 is required.</strong> There is no downlevel target.</li><li><strong>PDF is the only export format.</strong> ‘<em>ExportFormat</em>’ exists so that adding another one doesn’t break call sites, but today it has one meaningful value.</li><li><strong>The IDE plugins are not on their marketplaces.</strong> Rider and VS Code plugins — which give binding navigation and a design-time preview — install manually from direct download links in the README. A Visual Studio plugin doesn’t exist yet.</li><li><strong>MAUI on Windows is untested.</strong> The package targets Android, iOS and Mac Catalyst; a Windows target only appears when packing on a Windows host and ships unverified.</li><li>‘<strong>.rxaml’</strong> resources, styles and triggers use the runtime-loader fallback rather than compiled construction.</li></ul><h3>Try it</h3><pre>dotnet add package Pysar</pre><p>Source, samples (Console, MAUI, Avalonia, WPF, Blazor WASM) and docs:</p><p><a href="https://github.com/MriyaLab/Pysar"><strong><em>https://github.com/MriyaLab/Pysar</em></strong></a></p><p>MIT licensed. Issues and PRs welcome — especially from anyone rendering documents on a platform I don’t have on my desk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b23226495b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leveling Up Pull-to-Refresh in .NET MAUI: LoadingView, Bug Fixes & New Examples]]></title>
            <link>https://medium.com/@kolodiichyk/leveling-up-pull-to-refresh-in-net-maui-loadingview-bug-fixes-new-examples-c38b294041f2?source=rss-14068ac16a50------2</link>
            <guid isPermaLink="false">https://medium.com/p/c38b294041f2</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[net-maui]]></category>
            <category><![CDATA[xamarin]]></category>
            <category><![CDATA[dotnet-maui]]></category>
            <dc:creator><![CDATA[Andrii Kolodiichyk]]></dc:creator>
            <pubDate>Wed, 18 Mar 2026 05:47:01 GMT</pubDate>
            <atom:updated>2026-03-18T05:47:01.981Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XkgEhElANUExhctd8W4uwA.png" /></figure><blockquote>An update to my previous post <a href="https://medium.com/@kolodiichyk/building-beautiful-pull-to-refresh-experiences-in-net-maui-53809cad724f">Building Beautiful Pull-to-Refresh Experiences in .NET MAUI</a></blockquote><p>Since publishing the original article on Palmy.Maui.PullToRefresh, the library has received a meaningful round of improvements — a new LoadingView feature, several bug fixes, and a new example that shows the Overlay strategy at its best. This post walks through every change, explains the design decisions behind them, and shows you how to put it all to use.</p><p><strong>1. The New LoadingView Property</strong><br> <br>The biggest addition is a new bindable property: LoadingView. Previously, when a user triggered a refresh, the RefreshView (your custom pull indicator) would snap back into place and wait for IsRefreshing to turn false. There was no built-in way to say “while the data is loading, cover the whole screen with something else.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*3WdOpDveGeRaw9-UZ7gcHg.gif" /></figure><p>LoadingView fills that gap. Set it to any View and the control will: <br> <br> <em>1. Fade it in (over ~300 ms) immediately when the user releases and triggers a refresh. <br> 2. Fade it out automatically when IsRefreshing goes back to false.</em></p><pre>&lt;pullToRefresh:PullToRefreshView IsRefreshing=&quot;{Binding IsRefreshing}&quot;        <br>                                    RefreshCommand=&quot;{Binding RefreshCommand}&quot;&gt;  <br>                                                                                <br>      &lt;pullToRefresh:PullToRefreshView.LoadingView&gt;                             <br>          &lt;Grid BackgroundColor=&quot;#CC000000&quot;&gt;                                    <br>              &lt;lottie:LottieView Source=&quot;loading.json&quot;                          <br>                                 RepeatMode=&quot;Infinite&quot;                          <br>                                 HorizontalOptions=&quot;Fill&quot;                       <br>                                 VerticalOptions=&quot;Fill&quot; /&gt;                      <br>          &lt;/Grid&gt;                                                               <br>      &lt;/pullToRefresh:PullToRefreshView.LoadingView&gt;<br>                                                                                <br>      &lt;!-- your content here --&gt;<br>      &lt;CollectionView ItemsSource=&quot;{Binding Items}&quot; /&gt;                          <br>                                                                                <br>  &lt;/pullToRefresh:PullToRefreshView&gt;</pre><p>It works with both strategies (<em>Normal</em> and <em>Overlay</em>) and the property is fully bindable, so you can swap the view at runtime.</p><p><strong>2. New example Weather</strong></p><p>The sample app now includes a Weather page that shows a clean, minimal use of the Pull-to-Refresh control with the ScrollView.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*4dhaLGrV1dC5EUhVDMM9ZA.gif" /></figure><p><em>— Clean white UI with a large current temperature display, weather icon <br> (FontAwesome), and a 5-day forecast list<br> — A RefreshView with a branded header bar containing a Lottie spinner <br> animation <br> — Each refresh regenerates random weather data (temperature, wind, weather type), simulating a real API call with a 3-second delay</em></p><pre>&lt;pullToRefresh:PullToRefreshView IsRefreshing=&quot;{Binding IsRefreshing}&quot;        <br>                                    RefreshCommand=&quot;{Binding RefreshCommand}&quot;<br>                                    RefreshHeight=&quot;80&quot;                          <br>                                    MaxPullDistance=&quot;160&quot;                       <br>                                    Type=&quot;Normal&quot;&gt;                              <br>                                                                                <br>      &lt;pullToRefresh:PullToRefreshView.RefreshView&gt;                             <br>          &lt;Border BackgroundColor=&quot;{StaticResource Tertiary}&quot;<br>                  HeightRequest=&quot;80&quot;                                            <br>                  StrokeThickness=&quot;0&quot;&gt;                                          <br>              &lt;lottie:LottieView Source=&quot;spinner.json&quot;                          <br>                                 HeightRequest=&quot;40&quot; WidthRequest=&quot;40&quot;           <br>                                 AutoPlay=&quot;True&quot;                                <br>                                 RepeatMode=&quot;Infinite&quot;                          <br>                                 HorizontalOptions=&quot;Center&quot;                     <br>                                 VerticalOptions=&quot;Center&quot; /&gt;                    <br>          &lt;/Border&gt;                                                             <br>      &lt;/pullToRefresh:PullToRefreshView.RefreshView&gt;                            <br>                                                                                <br>      &lt;ScrollView&gt;<br>          &lt;!-- City, current temperature, weather icon, 5-day forecast --&gt;<br>      &lt;/ScrollView&gt;                                                             <br>   <br>  &lt;/pullToRefresh:PullToRefreshView&gt;</pre><p><strong>3. Bug Fixes &amp; Improvements (v0.1.0-alpha → v1.1.0)</strong></p><p>Here’s everything that was fixed and improved since the first alpha:</p><p>— iOS scroll conflict — Gesture recognition on iOS conflicted with native<br> scroll, causing the pull gesture to interfere with list scrolling. Reworked<br> with a custom TouchInterceptorGestureRecognizer (moved to its own file) and improved null-guard handling in InitializeCollectionView.<br> — Android hidden cells in CollectionView — Items at the top of a<br> CollectionView would become invisible after a pull gesture on Android. Fixed in the Normal strategy by correcting how the refresh row layout was measured and applied.<br> — Android touch/Down gesture — The DOWN touch event wasn’t being captured correctly, causing missed or delayed pull starts. Replaced inline listener code with dedicated GenericTouchListener and OnItemTouchListener classes wired to RecyclerView via SetOnTouchListener + AddOnItemTouchListener.<br> — Normal strategy layout rewrite — The Normal strategy previously translated the entire container. It was rewritten to animate HeightRequest on a dedicated grid row, resulting in cleaner pull behaviour and correct layout during the animation.<br> — Memory leaks — Strategies now use WeakReference&lt;PullToRefreshView&gt; and properly clear all view references on Dispose. Platform handlers unsubscribe from all event listeners on detach. AbortAnimation is called during disposal to prevent dangling animation callbacks.<br> — RefreshView freeze on cancel with LoadingView — When a LoadingView was set and the user released before reaching the ReleaseToRefresh threshold, the RefreshView would freeze. <br> — Overlay strategy percentage starting at −100 — The Pulling event’s Progress value was reporting −100 → 0 instead of 0 → 100. <br> — Weather page example — Added a third example page with a weather-themed refresh flow, including a custom WeatherTypeConverter helper.<br> — AutoResize property removed — The AutoResize bindable property was removedas it was superseded by the new strategy architecture.</p><p>— -<br> All the code is available in the <a href="https://github.com/kolodiichyk/Palmy.Maui.PullToRefresh">https://github.com/kolodiichyk/Palmy.Maui.PullToRefresh</a>. If you hit any issues or have feature ideas, open an issue or start a discussion there. Happy refreshing! <br> <br> — -<br><em>Follow me for more .NET MAUI content.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c38b294041f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Beautiful Pull-to-Refresh Experiences in .NET MAUI]]></title>
            <link>https://medium.com/@kolodiichyk/building-beautiful-pull-to-refresh-experiences-in-net-maui-53809cad724f?source=rss-14068ac16a50------2</link>
            <guid isPermaLink="false">https://medium.com/p/53809cad724f</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[mobile-apps]]></category>
            <category><![CDATA[net-maui]]></category>
            <dc:creator><![CDATA[Andrii Kolodiichyk]]></dc:creator>
            <pubDate>Sun, 11 Jan 2026 17:57:17 GMT</pubDate>
            <atom:updated>2026-01-12T12:36:34.071Z</atom:updated>
            <content:encoded><![CDATA[<h3>Building Beautiful Pull-to-Refresh Experiences in .NET MAUI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o1JyHDejwdETdwBmBEYdHA.png" /></figure><p>Pull-to-refresh is one of those UI patterns we’ve come to expect in modern mobile applications. Whether you’re checking your social feed, refreshing your email, or updating a shopping list, that satisfying pull gesture has become second nature. But if you’ve tried implementing custom refresh indicators in .NET MAUI, you’ve likely encountered the limitations of the built-in `RefreshView` control.</p><p>Today, I’m excited to introduce Palmy.Maui.PullToRefresh — a highly customizable pull-to-refresh control that gives you complete freedom over your refresh indicator design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*5K2lUbMWJTYPIrz0OBPqCw.gif" /></figure><h3>The Problem with Default RefreshView</h3><p>.NET MAUI’s built-in `RefreshView` is functional, but it comes with significant limitations: <br>— Limited customization of the refresh indicator <br>— Platform-specific appearance that’s difficult to override <br>— No support for custom animations or interactive elements <br>— Restricted control over the refresh area’s size and behaviour</p><p>If you want to create a branded, polished user experience with custom animations— like a Lottie animation, animated icons, or even complex multi-element indicators — you’re out of luck with the default control.</p><h3>Introducing Palmy.Maui.PullToRefresh</h3><p>Palmy.Maui.PullToRefresh solves these problems by providing a completely customizable pull-to-refresh implementation that works seamlessly across iOS and Android. You get full control over:</p><p>- <em>Custom Refresh Views</em>: Use any MAUI view as your refresh indicator — Lottie animations, custom graphics, font icons, or complex layouts</p><p>- <em>Two Display Modes</em>: Choose between Normal (pushes content down) or Overlay (floats above content) types</p><p>- <em>State-Driven Events</em>: React to pull states (Pulling, ReleaseToRefresh, Refreshing, Finished, Cancelled) to create interactive animations</p><p>- <em>Configurable Behaviour</em>: Control pull distance, refresh height, and other parameters</p><p>- <em>MVVM-Friendly</em>: Full data binding support with `IsRefreshing` and `RefreshCommand` properties</p><h3>Getting Started</h3><p>Installation is straightforward. Add the NuGet package to your .NET MAUI project (check Prerelease as it’s only an alpha version):</p><pre>dotnet add package Palmy.Maui.PullToRefresh</pre><p>Let’s start with a simple example. Here’s how to wrap a `CollectionView` with custom pull-to-refresh functionality:</p><pre>&lt;pullToRefresh:PullToRefreshView<br>    IsRefreshing=&quot;{Binding IsRefreshing}&quot;<br>    RefreshCommand=&quot;{Binding RefreshCommand}&quot;<br>    RefreshHeight=&quot;120&quot;<br>    MaxPullDistance=&quot;420&quot;<br>    Type=&quot;Normal&quot;&gt;<br><br>    &lt;pullToRefresh:PullToRefreshView.RefreshView&gt;<br>        &lt;Border HeightRequest=&quot;120&quot; BackgroundColor=&quot;White&quot;&gt;<br>            &lt;!-- Your custom refresh indicator goes here --&gt;<br>            &lt;ActivityIndicator IsRunning=&quot;True&quot; /&gt;<br>        &lt;/Border&gt;<br>    &lt;/pullToRefresh:PullToRefreshView.RefreshView&gt;<br><br>    &lt;CollectionView ItemsSource=&quot;{Binding Items}&quot;&gt;<br>        &lt;!-- Your item template --&gt;<br>    &lt;/CollectionView&gt;<br>&lt;/pullToRefresh:PullToRefreshView&gt;</pre><p>And the corresponding ViewModel:</p><pre>public class MyViewModel : BaseViewModel<br>{<br>    public bool IsRefreshing { get; set; }<br>    public ObservableCollection&lt;MyItem&gt; Items { get; set; } = new();<br>    public Command RefreshCommand { get; }<br><br>    public MyViewModel()<br>    {<br>        RefreshCommand = new Command(OnRefresh);<br>    }<br><br>    private async void OnRefresh()<br>    {<br>        IsRefreshing = true;<br><br>        // Fetch new data<br>        await LoadDataAsync();<br><br>        IsRefreshing = false;<br>    }<br>}</pre><h3>Advanced Example: Lottie Animation with State Changes</h3><p>Now let’s create something more impressive. We’ll use a Lottie animation that changes based on the pull state:</p><pre>&lt;pullToRefresh:PullToRefreshView<br>    IsRefreshing=&quot;{Binding IsRefreshing}&quot;<br>    RefreshCommand=&quot;{Binding RefreshCommand}&quot;<br>    RefreshHeight=&quot;120&quot;<br>    MaxPullDistance=&quot;420&quot;<br>    Type=&quot;Overlay&quot;<br>    Pulling=&quot;PullToRefreshView_OnPulling&quot;&gt;<br><br>    &lt;pullToRefresh:PullToRefreshView.RefreshView&gt;<br>        &lt;Grid HeightRequest=&quot;120&quot; IsClippedToBounds=&quot;True&quot;&gt;<br>            &lt;Border Margin=&quot;15&quot;<br>                    BackgroundColor=&quot;White&quot;<br>                    HeightRequest=&quot;60&quot;<br>                    WidthRequest=&quot;60&quot;<br>                    HorizontalOptions=&quot;Center&quot;<br>                    VerticalOptions=&quot;Center&quot;<br>                    StrokeShape=&quot;RoundRectangle 30&quot;&gt;<br>                &lt;Border.Shadow&gt;<br>                    &lt;Shadow Brush=&quot;Gray&quot; Radius=&quot;10&quot; Offset=&quot;0,0&quot; /&gt;<br>                &lt;/Border.Shadow&gt;<br><br>                &lt;lottie:LottieView x:Name=&quot;AnimationView&quot;<br>                                   AutoPlay=&quot;False&quot;<br>                                   RepeatMode=&quot;Infinite&quot;<br>                                   Source=&quot;spinner.json&quot;<br>                                   HeightRequest=&quot;40&quot;<br>                                   WidthRequest=&quot;40&quot; /&gt;<br>            &lt;/Border&gt;<br><br>            &lt;Image HeightRequest=&quot;40&quot; WidthRequest=&quot;40&quot;&gt;<br>                &lt;Image.Source&gt;<br>                    &lt;FontImageSource x:Name=&quot;RefreshViewFontImageSource&quot;<br>                                     FontFamily=&quot;FontAwesomeSolid&quot;<br>                                     Glyph=&quot;circle-down&quot;<br>                                     Color=&quot;LightGray&quot; /&gt;<br>                &lt;/Image.Source&gt;<br>            &lt;/Image&gt;<br>        &lt;/Grid&gt;<br>    &lt;/pullToRefresh:PullToRefreshView.RefreshView&gt;<br><br>    &lt;CollectionView ItemsSource=&quot;{Binding Products}&quot;&gt;<br>        &lt;!-- Your collection items --&gt;<br>    &lt;/CollectionView&gt;<br>&lt;/pullToRefresh:PullToRefreshView&gt;</pre><p>In the code-behind, we handle the `Pulling` event to update the UI based on the current state:</p><pre>private void PullToRefreshView_OnPulling(object sender, PullToRefreshEventArgs e)<br>{<br>    switch (e.State)<br>    {<br>        case PullToRefreshState.Pulling:<br>            RefreshViewFontImageSource.Glyph = &quot;circle-down&quot;;<br>            break;<br><br>        case PullToRefreshState.ReleaseToRefresh:<br>            RefreshViewFontImageSource.Glyph = &quot;circle-up&quot;;<br>            break;<br><br>        case PullToRefreshState.Refreshing:<br>            RefreshViewFontImageSource.Glyph = null;<br>            AnimationView.Play();<br>            break;<br><br>        case PullToRefreshState.Finished:<br>        case PullToRefreshState.Cancelled:<br>            AnimationView.Stop();<br>            RefreshViewFontImageSource.Glyph = &quot;circle-down&quot;;<br>            break;<br>    }<br>}</pre><p>This creates a beautiful, interactive experience:</p><p>1. <em>Pulling</em>: Shows a down arrow icon</p><p>2. <em>ReleaseToRefresh</em>: Flips to an up arrow (user pulled far enough)</p><p>3. <em>Refreshing</em>: Hides the icon and plays the Lottie spinner animation</p><p>4. <em>Finished/Cancelled</em>: Stops the animation and resets to the down arrow</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*FXv9YsgCLPOhxVDzyBUf_w.gif" /></figure><h3>Understanding Pull Types</h3><p>Palmy.Maui.PullToRefresh offers two display types:</p><p><strong><em>Normal Type</em></strong><br>The refresh view pushes your content down as you pull. This is the traditional pull-to-refresh behavior you see in most apps.</p><pre>&lt;pullToRefresh:PullToRefreshView Type=&quot;Normal&quot;&gt;</pre><p>Perfect for:</p><ul><li>List views where content should visibly move</li><li>Designs where the refresh indicator needs to be part of the content flow</li></ul><p><strong><em>Overlay Type<br></em></strong>The refresh view floats above your content, which stays in place. This creates a more modern, app-like feel.</p><pre>&lt;pullToRefresh:PullToRefreshView Type=&quot;Overlay&quot;&gt;</pre><p>Perfect for:</p><ul><li>Card-based layouts</li><li>Designs where content should remain stationary</li><li>Creating floating, badge-style refresh indicators</li></ul><h3>Creating a Creative Refresh Experience</h3><p>Let’s look at a more creative example from the sample app — a car dealership list with an animated car driving across the screen during refresh:</p><pre>&lt;pullToRefresh:PullToRefreshView<br>    IsRefreshing=&quot;{Binding IsRefreshing}&quot;<br>    RefreshCommand=&quot;{Binding RefreshCommand}&quot;<br>    RefreshHeight=&quot;120&quot;<br>    MaxPullDistance=&quot;420&quot;<br>    Type=&quot;Normal&quot;<br>    Pulling=&quot;PullToRefreshView_OnPulling&quot;&gt;<br><br>    &lt;pullToRefresh:PullToRefreshView.RefreshView&gt;<br>        &lt;Border BackgroundColor=&quot;White&quot; HeightRequest=&quot;120&quot;&gt;<br>            &lt;lottie:LottieView x:Name=&quot;AnimationView&quot;<br>                               Margin=&quot;0,58,0,0&quot;<br>                               AutoPlay=&quot;False&quot;<br>                               RepeatMode=&quot;Infinite&quot;<br>                               Source=&quot;car.json&quot;<br>                               HeightRequest=&quot;240&quot;<br>                               HorizontalOptions=&quot;Fill&quot; /&gt;<br>        &lt;/Border&gt;<br>    &lt;/pullToRefresh:PullToRefreshView.RefreshView&gt;<br><br>    &lt;CollectionView ItemsSource=&quot;{Binding Cars}&quot;&gt;<br>        &lt;!-- Car items --&gt;<br>    &lt;/CollectionView&gt;<br>&lt;/pullToRefresh:PullToRefreshView&gt;</pre><p>When users refresh the car list, a delightful Lottie animation of a car driving across the screen plays — perfectly matching the content being refreshed!</p><h3>Key Properties and Events</h3><p><strong><em>Bindable Properties</em></strong></p><ul><li><em>IsRefreshing</em> (bool): Bind to your ViewModel to control/monitor refresh state</li><li><em>RefreshCommand</em> (ICommand): Command executed when refresh is triggered</li><li><em>RefreshHeight</em> (double): Height of the refresh indicator area (default: 100)</li><li><em>MaxPullDistance</em> (double): Maximum distance users can pull (default: 200)</li><li><em>Type</em> (PullToRefreshType): Normal or Overlay display mode</li><li><em>RefreshView</em>(View): Your custom refresh indicator view</li></ul><p><strong><em>Events</em></strong></p><ul><li><em>Pulling</em>: Fires continuously during pull gesture with state and percentage information</li></ul><p><strong><em>Pull States<br></em></strong>The <em>PullToRefreshEventArgs</em> provides:</p><ul><li>State: Current pull state (Pulling, ReleaseToRefresh, Released, Refreshing, Cancelled, Finished)</li><li>Percentage: Pull progress from 0 to 1, useful for creating progress-based animations</li></ul><h3>Performance Considerations</h3><p><em>Palmy.Maui.PullToRefresh</em> is built with performance in mind:</p><ul><li>Uses native gesture recognizers for smooth, responsive pull interactions</li><li>Supports hardware acceleration for Lottie animations</li><li>Efficiently handles state changes without unnecessary re-renders</li><li>- Works seamlessly with virtualized lists like `CollectionView`</li></ul><h3>Platform Support</h3><p>The control works identically on:</p><ul><li>iOS / iPadOS</li><li>Android</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VVLZbhB-j69FThNwFR0liw.png" /></figure><h3>Conclusion</h3><p>At the current moment (11th of January 20205), it’s only an alpha version and not ready for production. There are some minor bugs, and control support only CollectionView</p><p>So<em>, Palmy.Maui.PullToRefresh</em> transforms pull-to-refresh from a mundane utility into an opportunity for creative, branded user experiences. Whether you want simple customization or complex, state-driven animations, this control gives you the flexibility you need.</p><p>The examples shown here are just the beginning. With full control over the refresh view and access to all pull states, you’re limited only by your imagination.</p><p>Ready to enhance your .NET MAUI apps with beautiful pull-to-refresh experiences? Check out the GitHub repository for source code, more examples, and contribution opportunities.</p><ul><li>Repository: <a href="https://github.com/kolodiichyk/Palmy.Maui.PullToRefresh">https://github.com/kolodiichyk/Palmy.Maui.PullToRefresh</a></li><li>Nuget: <a href="https://www.nuget.org/packages/Palmy.Maui.PullToRefresh/">https://www.nuget.org/packages/Palmy.Maui.PullToRefresh/</a></li></ul><p>— -</p><p>What creative refresh animations have you built? Share your ideas in the comments below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53809cad724f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ParallaxView in .net MAUI — easy way to apply parallax effect in your app]]></title>
            <link>https://medium.com/@kolodiichyk/parallaxview-in-net-maui-easy-way-to-apply-parallax-effect-in-your-app-86fc090fbd81?source=rss-14068ac16a50------2</link>
            <guid isPermaLink="false">https://medium.com/p/86fc090fbd81</guid>
            <dc:creator><![CDATA[Andrii Kolodiichyk]]></dc:creator>
            <pubDate>Thu, 27 Mar 2025 19:09:33 GMT</pubDate>
            <atom:updated>2025-03-27T19:09:33.385Z</atom:updated>
            <content:encoded><![CDATA[<h3>ParallaxView in .net MAUI — easy way to apply parallax effect in your app</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4A2fyTcQHBWrJ9csaog4bQ.jpeg" /></figure><p>Parallax scrolling effects can transform ordinary mobile interfaces into immersive experiences. In this article, I’ll show you how to use the ParallaxView library to easily implement stunning parallax effects in your .NET MAUI applications.</p><p><strong>Introduction</strong></p><p>The library allows you to create layered visual elements that move at different speeds in response to user scrolling, creating a sense of depth and immersion. Each image inside the ParallaxView can be customized with parameters like Speed and ZoomScale, allowing for precise control over the parallax effect and enabling a wide range of creative possibilities.</p><p><strong>Installation</strong></p><p>First, install the ParallaxView package using the NuGet Package Manager or the following command:</p><pre>dotnet add package ParallaxView</pre><p><strong>Usage cases</strong></p><p>Create a page and add the namespace to your XAML:</p><pre><br>&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br>&lt;ContentPage x:Class=&quot;ParallaxView.Example.FireWatchPage&quot;<br>             xmlns=&quot;http://schemas.microsoft.com/dotnet/2021/maui&quot;<br>             xmlns:x=&quot;http://schemas.microsoft.com/winfx/2009/xaml&quot;<br>             xmlns:parallaxView=&quot;clr-namespace:ParallaxView;assembly=ParallaxView&quot;&gt;<br>    &lt;ScrollView&gt;<br>        &lt;VerticalStackLayout Padding=&quot;20,0&quot;<br>                             Spacing=&quot;10&quot;<br>                             VerticalOptions=&quot;Start&quot;&gt;<br><br>            &lt;!-- Content elements follow --&gt;<br>            <br>        &lt;/VerticalStackLayout&gt;<br>    &lt;/ScrollView&gt;<br>&lt;/ContentPage&gt;</pre><p>Now you can use the control in your XAML:</p><pre>&lt;parallaxView:ParallaxView HeightRequest=&quot;300&quot;&gt;<br>    &lt;Image parallaxView:ParallaxView.Speed=&quot;0.8&quot;<br>           Aspect=&quot;AspectFill&quot;<br>           HeightRequest=&quot;300&quot;<br>           HorizontalOptions=&quot;Fill&quot;<br>           Source=&quot;layer_1.png&quot;<br>           VerticalOptions=&quot;End&quot; /&gt;<br><br>    &lt;Image parallaxView:ParallaxView.Speed=&quot;0.7&quot;<br>           Aspect=&quot;AspectFill&quot;<br>           HeightRequest=&quot;300&quot;<br>           HorizontalOptions=&quot;Fill&quot;<br>           Source=&quot;layer_2.png&quot;<br>           VerticalOptions=&quot;End&quot; /&gt;<br><br>          &lt;!--... Other images ...--&gt;<br><br>    &lt;Image parallaxView:ParallaxView.Speed=&quot;0.3&quot;<br>           Aspect=&quot;AspectFill&quot;<br>           HeightRequest=&quot;250&quot;<br>           HorizontalOptions=&quot;Center&quot;<br>           Source=&quot;firewatch.png&quot;<br>           VerticalOptions=&quot;Center&quot; /&gt;<br><br>    &lt;Image parallaxView:ParallaxView.Speed=&quot;0&quot;<br>           Aspect=&quot;AspectFill&quot;<br>           HeightRequest=&quot;300&quot;<br>           HorizontalOptions=&quot;Fill&quot;<br>           Source=&quot;layer_6.png&quot;<br>           VerticalOptions=&quot;End&quot; /&gt;<br>&lt;/parallaxView:ParallaxView&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*38utdvG-NFB9lZbPUppnOw.gif" /></figure><p><strong>Zoom effect</strong></p><p>Another case of using a control for the zooming effect</p><pre>&lt;parallaxView:ParallaxView HeightRequest=&quot;250&quot;&gt;<br>    &lt;Image parallaxView:ParallaxView.IsZoomed=&quot;True&quot;<br>           parallaxView:ParallaxView.Speed=&quot;0.9&quot;<br>           parallaxView:ParallaxView.ZoomScale=&quot;0.0075&quot;<br>           Aspect=&quot;AspectFill&quot;<br>           HeightRequest=&quot;250&quot;<br>           HorizontalOptions=&quot;Fill&quot;<br>           Source=&quot;photo.jpg&quot;<br>           VerticalOptions=&quot;End&quot; /&gt;<br>&lt;/parallaxView:ParallaxView&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*TAP48I85oxkzSoupXu5Xkw.gif" /></figure><p><strong>Using ParallaxView outside of ScrollView</strong></p><p>This implementation creates a visually appealing effect where the background image scrolls at a different rate than the foreground content, adding depth to the UI.<br>To attach a scrolling event of some control to the ParallaxView set this control to the Source:</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;<br>&lt;ContentPage x:Class=&quot;ParallaxView.Example.BackgroundParallaxPage&quot;<br>             xmlns=&quot;http://schemas.microsoft.com/dotnet/2021/maui&quot;<br>             xmlns:x=&quot;http://schemas.microsoft.com/winfx/2009/xaml&quot;<br>             xmlns:parallaxView=&quot;clr-namespace:ParallaxView;assembly=ParallaxView&quot;<br>             BackgroundColor=&quot;{DynamicResource Primary}&quot;&gt;<br>    &lt;Grid&gt;<br>        &lt;parallaxView:ParallaxView HorizontalOptions=&quot;Fill&quot;<br>                                   Source=&quot;{x:Reference CollectionViewExample}&quot;<br>                                   VerticalOptions=&quot;Fill&quot;&gt;<br>            &lt;Image parallaxView:ParallaxView.Speed=&quot;0.1&quot;<br>                   Aspect=&quot;AspectFill&quot;<br>                   HeightRequest=&quot;1500&quot;<br>                   HorizontalOptions=&quot;Fill&quot;<br>                   Source=&quot;example4.jpg&quot;<br>                   VerticalOptions=&quot;Fill&quot; /&gt;<br>        &lt;/parallaxView:ParallaxView&gt;<br>        &lt;CollectionView x:Name=&quot;CollectionViewExample&quot;&gt;<br>            &lt;CollectionView.ItemTemplate&gt;<br>                &lt;DataTemplate&gt;<br>                    &lt;!-- Replace with your content --&gt;<br>                &lt;/DataTemplate&gt;<br>            &lt;/CollectionView.ItemTemplate&gt;<br>        &lt;/CollectionView&gt;<br>    &lt;/Grid&gt;<br>&lt;/ContentPage&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*uy6QueSLI2bB8zBp9t75ew.gif" /></figure><p><strong>Conclusion</strong></p><p>ParallaxView makes it easy to implement sophisticated visual effects in your .NET MAUI applications. By following the examples of implementation, you can create immersive, visually appealing interfaces that engage your users and elevate your app’s design.</p><blockquote>🔗 GitHub: <a href="https://github.com/kolodiichyk/ParallaxView">https://github.com/kolodiichyk/ParallaxView</a><br>📦 NuGet: <a href="https://www.nuget.org/packages/ParallaxView/">https://www.nuget.org/packages/ParallaxView</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86fc090fbd81" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>