<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Zero-to-Hero on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/zero-to-hero/</link>
    <description>Recent content in Zero-to-Hero on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 23 Oct 2022 18:41:15 -0400</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/zero-to-hero/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Zero to Hero: Android App - Part 2 - Database</title>
      <link>https://www.bradcypert.com/zero-to-hero-android-app-part-2-database/</link>
      <pubDate>Mon, 26 Sep 2016 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/zero-to-hero-android-app-part-2-database/</guid>
      <description>&lt;p&gt;Oh, hey, didn’t see you there. Glad that you’ve came back for the next part of my &lt;strong&gt;Zero to Hero&lt;/strong&gt; series! Let’s get right into it!&lt;/p&gt;&#xA;&lt;p&gt;Last time, we created an Android app from Android Studio and manually created the View (or the visual representation of one of our screens) for our application. If you’ve missed out on that piece, you probably want to go back and start there, as all of the other posts in this series build off of that one. &lt;a href=&#34;http://www.bradcypert.com/zero-to-hero-android-app-part-1/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;You can find it here&lt;/a&gt;&#xA;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Zero to Hero: Android App - Part 1 - Views</title>
      <link>https://www.bradcypert.com/zero-to-hero-android-app-part-1/</link>
      <pubDate>Thu, 15 Sep 2016 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/zero-to-hero-android-app-part-1/</guid>
      <description>&lt;p&gt;App development is never a straight-forward task. In fact, apps are built from many components that handle specific needs. It’s up to you, the app developer, to determine which components you need, how they should be implemented, and how they should interface with the rest of the app. The most common component is called a View.&lt;/p&gt;&#xA;&lt;h4 id=&#34;android-views&#34;&gt;Android Views&lt;/h4&gt;&#xA;&lt;p&gt;Look around. What do you see? Sure, the specifics of what you and I see are different, but they both represent the same concept. We both see things that have some visual representation and are usually something we can interact with. In Android, views represent the same thing – They’re essentially just the part of the app a user can see and interact with.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Zero to Hero: Android App - Part 0 - Overview</title>
      <link>https://www.bradcypert.com/zero-to-hero-android-app-iteration-0/</link>
      <pubDate>Tue, 13 Sep 2016 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/zero-to-hero-android-app-iteration-0/</guid>
      <description>&lt;p&gt;I’ve decided to try something new with this post and start a new series called &lt;strong&gt;Zero to Hero&lt;/strong&gt;. The concept behind this is simple – From no knowledge about the proposed domain, we’ll create something cool and get you started with the fundamentals of that domain. Zero knowledge isn’t to say I’ll teach you how to build something as if you have never touched a computer, but it’s, for example, an interactive and fun way to learn Android given: You know what an Android phone is, you’re somewhat comfortable with Java, and XML doesn’t give you the heebeegeebees!&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
