<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mobile on Artur Rios Lab</title><link>https://lab.artur-rios.tech/tags/mobile/</link><description>Recent content in Mobile on Artur Rios Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 20 Oct 2026 18:00:00 +0000</lastBuildDate><atom:link href="https://lab.artur-rios.tech/tags/mobile/index.xml" rel="self" type="application/rss+xml"/><item><title>What Is Flutter? History, Architecture and How to Build With It</title><link>https://lab.artur-rios.tech/front-end/flutter/</link><pubDate>Tue, 20 Oct 2026 18:00:00 +0000</pubDate><guid>https://lab.artur-rios.tech/front-end/flutter/</guid><description>&lt;p&gt;Most toolkits for building an app on more than one platform make a choice&#10;early on: either they wrap each platform&amp;rsquo;s own buttons, lists and text fields,&#10;or they run the app inside a web view. Flutter does neither. It ships its own&#10;rendering engine inside every app and draws every pixel of the interface&#10;itself, from the text to the scroll bars, on a canvas the operating system&#10;hands it. The same Dart code then runs on Android, iOS, the web, Windows,&#10;macOS and Linux, and on embedded devices through a custom host.&lt;/p&gt;</description></item></channel></rss>