<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: jbjrwww</title>
    <description>The latest articles on DEV Community by jbjrwww (@jbjrwww).</description>
    <link>https://dev.to/jbjrwww</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4179412%2F18070eed-c884-4b58-88df-3f578ba91f54.png</url>
      <title>DEV Community: jbjrwww</title>
      <link>https://dev.to/jbjrwww</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jbjrwww"/>
    <language>en</language>
    <item>
      <title>Why Pikon World chooses mobile 3D quality before the first frame</title>
      <dc:creator>jbjrwww</dc:creator>
      <pubDate>Mon, 12 Oct 2026 13:19:50 +0000</pubDate>
      <link>https://dev.to/jbjrwww/why-pikon-world-chooses-mobile-3d-quality-before-the-first-frame-4i73</link>
      <guid>https://dev.to/jbjrwww/why-pikon-world-chooses-mobile-3d-quality-before-the-first-frame-4i73</guid>
      <description>&lt;p&gt;Pikon is my Flutter strategy game, available on iOS and Android. I'm developing its 3D territory world with flutter_scene and Flutter GPU.&lt;/p&gt;

&lt;p&gt;Demo: &lt;a href="https://www.youtube.com/shorts/E56hZT_j4Ps" rel="noopener noreferrer"&gt;https://www.youtube.com/shorts/E56hZT_j4Ps&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The short development demo shows the boat, a storm, conquest effects and native stone wall construction. One engineering decision behind it is worth explaining: quality is chosen before the first frame.&lt;/p&gt;

&lt;p&gt;Waiting for low frame rates is not enough when allocating render targets can already exceed a device's memory budget. The world starts with one of four presets selected from device RAM. A frame governor then samples pacing and can lower quality, but does not raise it again during the same session.&lt;/p&gt;

&lt;p&gt;The initial selector in the current implementation is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight dart"&gt;&lt;code&gt;&lt;span class="kd"&gt;static&lt;/span&gt; &lt;span class="n"&gt;WorldQuality&lt;/span&gt; &lt;span class="nf"&gt;forDeviceMemory&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;int&lt;/span&gt;&lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="n"&gt;megabytes&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;megabytes&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="kc"&gt;null&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="n"&gt;megabytes&lt;/span&gt; &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;full&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;megabytes&lt;/span&gt; &lt;span class="p"&gt;&amp;lt;&lt;/span&gt; &lt;span class="mi"&gt;2560&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;minimal&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;megabytes&lt;/span&gt; &lt;span class="p"&gt;&amp;lt;&lt;/span&gt; &lt;span class="mi"&gt;3584&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;light&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;megabytes&lt;/span&gt; &lt;span class="p"&gt;&amp;lt;&lt;/span&gt; &lt;span class="mi"&gt;5120&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;balanced&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;full&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;These RAM thresholds are project heuristics. Total RAM is only a rough signal, and unknown memory currently falls back to the full preset. The runtime governor ignores a three-second warm-up, evaluates two-second windows and drops a level below 40 observed fps. That value is a control threshold. It does not guarantee a particular device frame rate.&lt;/p&gt;

&lt;p&gt;Ambient occlusion, bloom, render-target pixel ratio, shadows and anti-aliasing are reduced across the presets. Android also has a separate shadow policy while I investigate a render-pass issue.&lt;/p&gt;

&lt;p&gt;This clip is a development demonstration, not a phone performance benchmark. I'd be interested in how other Flutter developers manage initial memory budgets for scenes embedded in an app.&lt;/p&gt;

&lt;p&gt;Try Pikon:&lt;br&gt;
iOS: &lt;a href="https://apps.apple.com/app/id6804834624" rel="noopener noreferrer"&gt;https://apps.apple.com/app/id6804834624&lt;/a&gt;&lt;br&gt;
Android: &lt;a href="https://play.google.com/store/apps/details?id=com.jbonjour.pikon" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.jbonjour.pikon&lt;/a&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>dart</category>
    </item>
  </channel>
</rss>
