<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Android Developer</title>
	<atom:link href="http://www.therealjoshua.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.therealjoshua.com</link>
	<description>Los Angeles Freelance Developer</description>
	<lastBuildDate>Thu, 26 Apr 2012 18:47:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Android: Starting a New Project</title>
		<link>http://www.therealjoshua.com/2012/04/android-starting-a-new-project/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=android-starting-a-new-project</link>
		<comments>http://www.therealjoshua.com/2012/04/android-starting-a-new-project/#comments</comments>
		<pubDate>Thu, 12 Apr 2012 04:08:39 +0000</pubDate>
		<dc:creator>musselwhizzle</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[OOP]]></category>
		<category><![CDATA[Styling]]></category>
		<category><![CDATA[Controller]]></category>
		<category><![CDATA[Deign Patterns]]></category>
		<category><![CDATA[Design Pattern]]></category>
		<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[flexible android]]></category>
		<category><![CDATA[MVC]]></category>
		<category><![CDATA[Styles]]></category>
		<category><![CDATA[View]]></category>

		<guid isPermaLink="false">http://www.therealjoshua.com/?p=425</guid>
		<description><![CDATA[Tomorrow I&#8217;m grateful to start new project and am filled with all the excitement that comes with it; I get to solve new architectural challenges, test new ideas, work with new designs, build new components, and work with new team members. When working with another developer on an app I typically like to divide the [...]]]></description>
		<wfw:commentRss>http://www.therealjoshua.com/2012/04/android-starting-a-new-project/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Event Dispatching: Sending Messages</title>
		<link>http://www.therealjoshua.com/2012/03/event-dispatching-sending-messages/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=event-dispatching-sending-messages</link>
		<comments>http://www.therealjoshua.com/2012/03/event-dispatching-sending-messages/#comments</comments>
		<pubDate>Fri, 23 Mar 2012 05:02:51 +0000</pubDate>
		<dc:creator>musselwhizzle</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[OOP]]></category>
		<category><![CDATA[Controller]]></category>
		<category><![CDATA[Data Binding]]></category>
		<category><![CDATA[Deign Patterns]]></category>
		<category><![CDATA[Design Pattern]]></category>
		<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[Model]]></category>
		<category><![CDATA[MVC]]></category>
		<category><![CDATA[View]]></category>

		<guid isPermaLink="false">http://www.therealjoshua.com/?p=403</guid>
		<description><![CDATA[This post will be discussing how to get objects to communicate with each other. If we look at a standard MVC diagram, we see 2 types of arrows on the diagram: solid arrows and dotted arrows. The solid arrows represent method invocations. For instance, foo.setBar(4) would be a method invocation. The dotted lines represent Events. [...]]]></description>
		<wfw:commentRss>http://www.therealjoshua.com/2012/03/event-dispatching-sending-messages/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Styling Android With Defaults</title>
		<link>http://www.therealjoshua.com/2012/01/styling-android-with-defaults/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=styling-android-with-defaults</link>
		<comments>http://www.therealjoshua.com/2012/01/styling-android-with-defaults/#comments</comments>
		<pubDate>Mon, 09 Jan 2012 02:20:16 +0000</pubDate>
		<dc:creator>musselwhizzle</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[OOP]]></category>
		<category><![CDATA[Styling]]></category>
		<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[flexible android]]></category>
		<category><![CDATA[Styles]]></category>

		<guid isPermaLink="false">http://www.therealjoshua.com/?p=352</guid>
		<description><![CDATA[According to Android&#8217;s own documentation, there is no documentation for styling Android. You&#8217;d think with the power of Google and huge market penetration, the Android team with have the commitment by now to document their code and features, but that&#8217;s another story. So what does Android officially say about styling? &#8220;Go read the source code.&#8221; [...]]]></description>
		<wfw:commentRss>http://www.therealjoshua.com/2012/01/styling-android-with-defaults/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Android Architecture: Part 9, Conclusion</title>
		<link>http://www.therealjoshua.com/2011/12/android-architecture-part-9-conclusion/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=android-architecture-part-9-conclusion</link>
		<comments>http://www.therealjoshua.com/2011/12/android-architecture-part-9-conclusion/#comments</comments>
		<pubDate>Thu, 29 Dec 2011 07:20:11 +0000</pubDate>
		<dc:creator>musselwhizzle</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[OOP]]></category>
		<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[Model]]></category>
		<category><![CDATA[MVC]]></category>
		<category><![CDATA[View]]></category>

		<guid isPermaLink="false">http://www.therealjoshua.com/?p=326</guid>
		<description><![CDATA[In the previous 8 articles we discussed in-depth all parts to setting up a well-architected Android project. This post will mostly be some of my general thoughts about our project Tap Counter,  MVC in Android and what&#8217;s next for this blog. Tap Counter: Sources I&#8217;m pretty happy with the  way the series turned out and [...]]]></description>
		<wfw:commentRss>http://www.therealjoshua.com/2011/12/android-architecture-part-9-conclusion/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>Android Architecture: Part 8, State Pattern</title>
		<link>http://www.therealjoshua.com/2011/11/android-architecture-part-8-state-pattern/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=android-architecture-part-8-state-pattern</link>
		<comments>http://www.therealjoshua.com/2011/11/android-architecture-part-8-state-pattern/#comments</comments>
		<pubDate>Sun, 27 Nov 2011 06:06:14 +0000</pubDate>
		<dc:creator>musselwhizzle</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[OOP]]></category>
		<category><![CDATA[Design Patterns]]></category>

		<guid isPermaLink="false">http://www.therealjoshua.com/?p=245</guid>
		<description><![CDATA[This is the part where I address what&#8217;s happening in TapController that I&#8217;ve been avoiding until now. Unlike MVC and DOAs, I wouldn&#8217;t consider the State Pattern to be an essential part of Android architecture. However, it certainly is rad and it can do some cool things. Between that and because I&#8217;ve used it in [...]]]></description>
		<wfw:commentRss>http://www.therealjoshua.com/2011/11/android-architecture-part-8-state-pattern/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Android Architecture: Part 7, Persistence</title>
		<link>http://www.therealjoshua.com/2011/11/android-architecture-part-7-persistence/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=android-architecture-part-7-persistence</link>
		<comments>http://www.therealjoshua.com/2011/11/android-architecture-part-7-persistence/#comments</comments>
		<pubDate>Sat, 26 Nov 2011 23:04:14 +0000</pubDate>
		<dc:creator>musselwhizzle</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[OOP]]></category>
		<category><![CDATA[Design Patterns]]></category>

		<guid isPermaLink="false">http://www.therealjoshua.com/?p=224</guid>
		<description><![CDATA[We&#8217;ve made it through all the hard stuff. If you can do MVC in Android, the rest of this series is going to easy. Grab a beer and reward yourself and let&#8217;s talk about data persistence. I&#8217;m going to assume you already know about sqlite and other persistence features in Android. If not, now is a [...]]]></description>
		<wfw:commentRss>http://www.therealjoshua.com/2011/11/android-architecture-part-7-persistence/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Android Architecture: Part 6, Putting it Together</title>
		<link>http://www.therealjoshua.com/2011/11/android-architecture-part-6-putting-it-together-2/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=android-architecture-part-6-putting-it-together-2</link>
		<comments>http://www.therealjoshua.com/2011/11/android-architecture-part-6-putting-it-together-2/#comments</comments>
		<pubDate>Sat, 26 Nov 2011 04:30:31 +0000</pubDate>
		<dc:creator>musselwhizzle</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[OOP]]></category>
		<category><![CDATA[Design Pattern]]></category>
		<category><![CDATA[MVC]]></category>

		<guid isPermaLink="false">http://www.therealjoshua.com/?p=195</guid>
		<description><![CDATA[So far we&#8217;ve discussed Models, Views, and Controllers. And now let&#8217;s discuss how we stick them together to make 1 cohesive unit of the MVC paradigm. The Activity is our entry point for each new view of our application and it&#8217;s in the onCreate() method that we will need to instantiate our model and controller. [...]]]></description>
		<wfw:commentRss>http://www.therealjoshua.com/2011/11/android-architecture-part-6-putting-it-together-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Android Architecture: Part 5, The Controller</title>
		<link>http://www.therealjoshua.com/2011/11/android-architecture-part-5-the-controller/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=android-architecture-part-5-the-controller</link>
		<comments>http://www.therealjoshua.com/2011/11/android-architecture-part-5-the-controller/#comments</comments>
		<pubDate>Sat, 26 Nov 2011 04:00:55 +0000</pubDate>
		<dc:creator>musselwhizzle</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[OOP]]></category>
		<category><![CDATA[Controller]]></category>
		<category><![CDATA[Deign Patterns]]></category>

		<guid isPermaLink="false">http://www.therealjoshua.com/?p=165</guid>
		<description><![CDATA[Of the 3 parts of MVC, the controller is the heavy lifter. The model is nothing more than a glorified name-value object and a good view is &#8220;dumb&#8221; and just updates when the model changes and does whatever the controller says. (The word &#8220;dumb&#8221; is common when talking about views and it&#8217;s a good thing [...]]]></description>
		<wfw:commentRss>http://www.therealjoshua.com/2011/11/android-architecture-part-5-the-controller/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Android Architecture: Part 4, The View</title>
		<link>http://www.therealjoshua.com/2011/11/android-architecture-part-4-the-view/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=android-architecture-part-4-the-view</link>
		<comments>http://www.therealjoshua.com/2011/11/android-architecture-part-4-the-view/#comments</comments>
		<pubDate>Fri, 25 Nov 2011 22:08:34 +0000</pubDate>
		<dc:creator>musselwhizzle</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[OOP]]></category>
		<category><![CDATA[Data Binding]]></category>
		<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[View]]></category>

		<guid isPermaLink="false">http://www.therealjoshua.com/?p=129</guid>
		<description><![CDATA[What is a View? In Android, Activities are going to be our architectural views. Having the Activity serve the role of a view isn&#8217;t too intuitive. Because Android creates the Activity for us and manages its lifecycle, it&#8217;s difficult to conceptualize the role an Activity should do. Heck, it even comes with tons of hooks [...]]]></description>
		<wfw:commentRss>http://www.therealjoshua.com/2011/11/android-architecture-part-4-the-view/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Android Architecture: Part 3, The Model</title>
		<link>http://www.therealjoshua.com/2011/11/android-architecture-part-3-the-model-in-mvc/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=android-architecture-part-3-the-model-in-mvc</link>
		<comments>http://www.therealjoshua.com/2011/11/android-architecture-part-3-the-model-in-mvc/#comments</comments>
		<pubDate>Fri, 25 Nov 2011 06:59:54 +0000</pubDate>
		<dc:creator>musselwhizzle</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[OOP]]></category>
		<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[Model]]></category>

		<guid isPermaLink="false">http://www.therealjoshua.com/?p=53</guid>
		<description><![CDATA[MVC General Concepts: To quickly review, MVC is a compound pattern meaning several patterns comprise this architectural pattern. The Model represents our application&#8217;s state. Remember, objects have state (properties) and behaviors (methods). And so applications have state (the model). In essence, models are just big name-value objects that dispatch events when its state changes. Views are the [...]]]></description>
		<wfw:commentRss>http://www.therealjoshua.com/2011/11/android-architecture-part-3-the-model-in-mvc/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

