<p dir="auto">I found a very, very small error in pubspec.yaml.</p>
<h2 dir="auto">Steps to Reproduce</h2>
<p dir="auto">Create fresh flutter project, and</p>
<ol dir="auto">
<li>Create <code class="notranslate">Image.asset</code> in main.dart</li>
<li>Uncomment the <code class="notranslate">assets</code> section to add a sample image asset</li>
<li>Try to run app</li>
</ol>
<p dir="auto">Then, an error occurs: <code class="notranslate">Error on line 40, column 4 of pubspec.yaml: Expected a key while parsing a block mapping. assets: ^ Unable to reload your application because "flutter packages get" failed to update package dependencies. Exception: pub get failed (65)</code></p>
<h2 dir="auto">Solution</h2>
<p dir="auto">All you have to do to fix it is to add one space before <code class="notranslate">uses-material-design: true</code>. By default intendation is broken.</p>
<p dir="auto">PS When you know how to fix it, it takes 3 seconds, but you still need some time to find a solution on the Internet. But it isn't what we would call "seamless experience". Also, as you could see, error log doesn't give usable hint</p>
<p dir="auto">Background: <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="277671100" data-permission-text="Title is private" data-url="https://github.com/flutter/flutter/issues/13242" data-hovercard-type="issue" data-hovercard-url="/flutter/flutter/issues/13242/hovercard" href="https://github.com/flutter/flutter/issues/13242">#13242</a> covers a specific memory consumption issue (which we'll continue looking into). I'm opening this bug for a more general discussion of the sorts of finer-grained control over image caching and handling that developers would like to see from Flutter.</p>
<p dir="auto">Today, the only real control the framework provides is the ability to set <a href="https://docs.flutter.io/flutter/painting/ImageCache-class.html#maximumSize" rel="nofollow">ImageCache.maximumSize</a> to indicate the maximum number of images to store in Flutter's image cache.</p>
<p dir="auto">In terms of the really basic things, a few thoughts:</p>
<ul dir="auto">
<li>finer-grained control over cache eviction</li>
<li>finer-grained control over cache strategy (e.g. local storage, store scaled/compressed)</li>
<li>de-duplication of identical source images</li>
</ul>
<p dir="auto">It would be useful to understand what features developers would like to see from the framework and what priorities people have around image caching.</p>