<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Siva G</title>
    <description/>
    <link>https://speakerdeck.com/sivag1</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/sivag1.rss"/>
    <lastBuildDate>2016-04-03 23:00:53 -0400</lastBuildDate>
    <item>
      <title>Android for Java Developers</title>
      <description></description>
      <media:content url="https://files.speakerdeck.com/presentations/358e74f0eb6c4a149014169fe8d498b3/preview_slide_0.jpg?7682774" type="image/jpeg" medium="image"/>
      <content:encoded></content:encoded>
      <pubDate>Wed, 15 Mar 2017 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/sivag1/android-for-java-developers</link>
      <guid>https://speakerdeck.com/sivag1/android-for-java-developers</guid>
    </item>
    <item>
      <title>Android: Develop fast with Libraries; well not too fast!</title>
      <description>Anyone beginning to develop in Android will be intimated by things like the amount of boilerplate coding, boring stock look and feel of the UI elements etc. Never to worry - Third Party libraries to the rescue.
 
We can save lot of valuable coding time by looking for already developed third party libraries. That could be for simple material design UI elements, or saving time on Image processing coding, or simplifying the Rest calls or even getting yourself like a ORM layer for the SQL DB.
 
But wait, usage of too many libraries poses its own serious issues.
 
We'll discuss some good library solutions and how to avoid issues that comes up with too many libraries.</description>
      <media:content url="https://files.speakerdeck.com/presentations/1c967e7d2f9343a3ad5d07d84f465eba/preview_slide_0.jpg?6077157" type="image/jpeg" medium="image"/>
      <content:encoded>Anyone beginning to develop in Android will be intimated by things like the amount of boilerplate coding, boring stock look and feel of the UI elements etc. Never to worry - Third Party libraries to the rescue.
 
We can save lot of valuable coding time by looking for already developed third party libraries. That could be for simple material design UI elements, or saving time on Image processing coding, or simplifying the Rest calls or even getting yourself like a ORM layer for the SQL DB.
 
But wait, usage of too many libraries poses its own serious issues.
 
We'll discuss some good library solutions and how to avoid issues that comes up with too many libraries.</content:encoded>
      <pubDate>Sat, 02 Apr 2016 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/sivag1/android-develop-fast-with-libraries-well-not-too-fast</link>
      <guid>https://speakerdeck.com/sivag1/android-develop-fast-with-libraries-well-not-too-fast</guid>
    </item>
    <item>
      <title>iOS for Android Developers</title>
      <description>If you know Java, you can start with Android easily. But how about iOS, especially after Swift?
 
 This session is about the core similarities and differences in the development of apps for iOS and Android. In the platform competition, there are two winners now. Neither of these platforms are going to outshine the other. So a developer is better equipped with developing for both, or at the least knowing both.
 
 Some familiarity with Android suggested, though not mandatory.</description>
      <media:content url="https://files.speakerdeck.com/presentations/6709f76aa2264203949b9fd46fb525b6/preview_slide_0.jpg?6076972" type="image/jpeg" medium="image"/>
      <content:encoded>If you know Java, you can start with Android easily. But how about iOS, especially after Swift?
 
 This session is about the core similarities and differences in the development of apps for iOS and Android. In the platform competition, there are two winners now. Neither of these platforms are going to outshine the other. So a developer is better equipped with developing for both, or at the least knowing both.
 
 Some familiarity with Android suggested, though not mandatory.</content:encoded>
      <pubDate>Sat, 02 Apr 2016 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/sivag1/ios-for-android-developers</link>
      <guid>https://speakerdeck.com/sivag1/ios-for-android-developers</guid>
    </item>
  </channel>
</rss>
