<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Android on code.kiwi.com</title><link>https://code.kiwi.com/tag/android/</link><description>Recent content in Android on code.kiwi.com</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 17 Mar 2023 21:06:30 +0000</lastBuildDate><atom:link href="https://code.kiwi.com/tag/android/index.xml" rel="self" type="application/rss+xml"/><item><title>Type-safe arguments in Jetpack Navigation Compose</title><link>https://code.kiwi.com/articles/type-safe-arguments-in-jetpack-navigation-compose/</link><pubDate>Sun, 02 Oct 2022 20:07:00 +0000</pubDate><guid>https://code.kiwi.com/articles/type-safe-arguments-in-jetpack-navigation-compose/</guid><description>&lt;p&gt;&lt;img src="https://code.kiwi.com/images/media/5d148e7ef2f4eb230a0ff66b9bf4293331ee6e32df53ef43b93d1a9cb879117d.webp" alt=""&gt;&lt;/p&gt;
&lt;p&gt;NavigationComposeTyped in action&lt;/p&gt;
&lt;p&gt;Jetpack Navigation Compose is the Jetpack Navigation library enhanced for usage in Compose. But the actual “enhancement” is a bit limited and different from the View-based navigation. Most importantly, there are no SafeArgs — a type-safe compile time solution for passing arguments between destinations. Navigation for Compose uses a simple URL pattern — &lt;strong&gt;arguments have to be converted to a string as a query parameter/path segment&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Rewriting Android App’s Back-Handling Logic</title><link>https://code.kiwi.com/articles/rewriting-android-apps-back-handling-logic/</link><pubDate>Tue, 29 Mar 2022 20:04:00 +0000</pubDate><guid>https://code.kiwi.com/articles/rewriting-android-apps-back-handling-logic/</guid><description>&lt;p&gt;Our Kiwi.com app is quite old and vast. It is in development for about 7 years; each year we’re adding more features and code, each year the app is being worked on by more developers.&lt;/p&gt;</description></item><item><title>Page Objects for E2E Android UI testing</title><link>https://code.kiwi.com/articles/page-objects-for-e2e-android-ui-testing/</link><pubDate>Mon, 14 Mar 2022 20:22:00 +0000</pubDate><guid>https://code.kiwi.com/articles/page-objects-for-e2e-android-ui-testing/</guid><description>&lt;p&gt;Android end-to-end UI testing is not that difficult, but we have observed that the official API/tooling doesn’t scale much if you have a big app.&lt;/p&gt;
&lt;p&gt;“Page Object” is a design pattern abstraction over a particular screen: it provides access to read the screen’s data and provides an API to interact with the screen. You may read the &lt;a href="https://martinfowler.com/bliki/PageObject.html"&gt;pattern description on Martin Fowler’s site&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>React Native at Kiwi.com</title><link>https://code.kiwi.com/articles/react-native-at-kiwi-com/</link><pubDate>Tue, 19 Nov 2019 18:25:00 +0000</pubDate><guid>https://code.kiwi.com/articles/react-native-at-kiwi-com/</guid><description>&lt;p&gt;Kiwi.com app is running on three main platforms — web, iOS and Android — and was written with different platform-specific technologies. &lt;strong&gt;We were curious about the possibilities of sharing code across multiple platforms&lt;/strong&gt; and dug into React Native (and React Native Web). Read on to find out what we learnt on the way.&lt;/p&gt;</description></item></channel></rss>