<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Android Makers on Ash Davies</title>
    <link>https://ashdavies.dev/tags/android-makers/</link>
    <description>Recent content in Android Makers on Ash Davies</description>
    <generator>Hugo -- 0.150.1</generator>
    <language>en</language>
    <lastBuildDate>Fri, 28 Apr 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ashdavies.dev/tags/android-makers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What a Long Strange Trip it&#39;s Been: This Year In Android</title>
      <link>https://ashdavies.dev/talks/this-year-in-android-paris/</link>
      <pubDate>Fri, 28 Apr 2023 00:00:00 +0000</pubDate>
      <guid>https://ashdavies.dev/talks/this-year-in-android-paris/</guid>
      <description>&lt;p&gt;The Android community is a fast evolving society of excellent people who passionately involve themselves in their ecosystem. This means the progress of developments can be fast, blazingly fast!&lt;/p&gt;
&lt;p&gt;Inspired by other content creators and newsletters that keep us informed about the most recent events, I decided to document news, events, and releases every week for a year. Starting from the end of Droidcon Berlin, the world’s best Android developer conference.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Everything is an API</title>
      <link>https://ashdavies.dev/talks/everything-is-an-api-makers/</link>
      <pubDate>Mon, 20 Apr 2020 00:00:00 +0000</pubDate>
      <guid>https://ashdavies.dev/talks/everything-is-an-api-makers/</guid>
      <description>&lt;p&gt;When creating a new app module, or modularising an existing one, it becomes easy to forget who might be consuming it. It becomes easy to forget that every decision you make will affect how it is used, or in the worst case, abused. We’re told that code should document itself, but how do these design decisions reflect in the understanding of intended use?&lt;/p&gt;
&lt;p&gt;Just because we might not be exposing a module as a public or open-sourced library, doesn’t mean we can’t benefit from making good decisions towards an effective and sensible API. By taking the stance that every piece of code we write is an API we can build more versatile and scalable applications.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
