<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Radim Vaculík on Medium]]></title>
        <description><![CDATA[Stories by Radim Vaculík on Medium]]></description>
        <link>https://medium.com/@radimvaculik?source=rss-dc7f55510e04------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tJz7HC-TWQhsGpe3z4JXfQ.jpeg</url>
            <title>Stories by Radim Vaculík on Medium</title>
            <link>https://medium.com/@radimvaculik?source=rss-dc7f55510e04------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:24:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@radimvaculik/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Static code analysis for Kotlin in Android]]></title>
            <link>https://medium.com/@radimvaculik/static-code-analysis-for-kotlin-in-android-8676c8d6a3c5?source=rss-dc7f55510e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/8676c8d6a3c5</guid>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[static-analysis]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[detekt]]></category>
            <dc:creator><![CDATA[Radim Vaculík]]></dc:creator>
            <pubDate>Sun, 12 Nov 2017 12:08:20 GMT</pubDate>
            <atom:updated>2017-11-12T12:08:20.881Z</atom:updated>
            <content:encoded><![CDATA[<p>In The FUNTASTY, the clean and well-readable code is very important for us. For Android project in Java, there are plenty of tools such as pmd or checkstyle and <a href="https://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis#Java">more others</a>, how to do static code analysis. But when we switched to Kotlin, we had to find another tool or solution, how to keep our Kotlin codebase on same good shape as Java’s one.</p><p>Since we started looking for the proper tool, we found <strong>ktlint</strong>. It looks really easy to configure it, but it has one big problem — there is no custom configuration. Ktlint is great idea and in my opinion, it could be suitable for small projects, where you don’t need to bother about configuration, but you need any basic static code analysis. You can find more info on project website <a href="https://ktlint.github.io/">https://ktlint.github.io/</a>.</p><p>But then, we found <strong>detekt</strong>. Detekt is open source project with loads of configuration tweaks and it also works very well with Android projects. The project’s website is <a href="https://github.com/arturbosch/detekt">https://github.com/arturbosch/detekt</a>. We also contributed with some small changes and bugfixes to the project.</p><p>It’s really easy to setup detekt. You need to edit main build.gradle file and add these lines:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ea9e9fc1d83cfa2ce666ce4b625a41c0/href">https://medium.com/media/ea9e9fc1d83cfa2ce666ce4b625a41c0/href</a></iframe><p>When you sync your project, you need to run:</p><pre>./gradlew detektGenerateConfig </pre><pre>Successfully copied default-detekt-config.yml to project location.</pre><p>This command generates a default config YML file with all rules. You need to rename the file and move it to proper folder. Since you have done it, you can run your code static analysis:</p><pre>./gradlew detektCheck</pre><pre>&gt; Task :detektCheck<br>Analyzing 0 kotlin files:</pre><pre>Project Statistics:<br>        - number of properties: 0<br>        - number of functions: 0<br>        - number of classes: 0<br>        - number of packages: 0<br>        - number of kt files: 0</pre><pre>detekt finished in 609 ms.</pre><pre>BUILD SUCCESSFUL in 1s<br>1 actionable task: 1 executed</pre><p>I’d like to share our The FUNTASTY Android configuration detekt.yml file with you:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c203fca69f2ccde32975528f22ffda77/href">https://medium.com/media/c203fca69f2ccde32975528f22ffda77/href</a></iframe><p>Detekt has also some dark sides — the project is still under rapid development and some features are changing every release. Sometimes we don’t know, if the code is wrong or just detekt changed their behaviour. But we can live with it and despite a few bad things, detekt is great tool for Kotlin static analysis.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8676c8d6a3c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Developer Days Europe]]></title>
            <link>https://medium.com/@radimvaculik/google-developer-days-europe-9bd645eb4a07?source=rss-dc7f55510e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/9bd645eb4a07</guid>
            <category><![CDATA[krakow]]></category>
            <category><![CDATA[gdd2017]]></category>
            <category><![CDATA[google-developer-day]]></category>
            <dc:creator><![CDATA[Radim Vaculík]]></dc:creator>
            <pubDate>Thu, 07 Sep 2017 09:41:20 GMT</pubDate>
            <atom:updated>2017-09-07T10:16:52.381Z</atom:updated>
            <content:encoded><![CDATA[<p>Jediná Google Developer konference v Evropě se konala 5. a 6. září v Krakově 🇵🇱. Proto jsme s nákupem vstupenek moc neváhali a nenechali si tuto událost ujít. A můžeme vám říct, že bylo na co koukat 👀.</p><p>Celá konference se konala v ICE Krakow Congress Centre, což byla naprosto výborná volba 👍. Velké sály a pohodlná místa na sezení a velmi dobrá dostupnost z centra města.</p><h3>Den 1</h3><p>Jak je již na takových akcích zvykem, celou akci započala Keynote, kde se představily hlavní kategorie o kterých GDD bude — Android, Firebase, Machine Learning, IoT, Progressive Web Apps nebo Google Cloud. My se zaměřili hlavně na přednášky týkající se Androidu nebo Firebase.</p><p>První přednáška od <a href="https://medium.com/u/84c8e3357532">Sam Dutton</a> na téma <strong>Progressive Web Apps: What, why and how?</strong> porovnávala webové aplikace vs. nativní aplikace. Musíme uznat, že load-time (v řádu stovek milisekund), velikost aplikace (do 1 MB) nebo multiplatformní využití hraje PWA do karet a určitě do budoucna bude PWA konkurovat nativním mobilním aplikacím. Stream najdete na <a href="https://www.youtube.com/watch?v=eodArdGRIVQ">https://www.youtube.com/watch?v=eodArdGRIVQ</a></p><p>Velmi podařená byla přednáška od <a href="https://medium.com/u/89d5869ff685">Shailen Tuli</a>, který v prezentaci <strong>Building for Android O </strong>převážně mluvil o tom, co se v Android O změnilo (hlavně k horšímu) pro vývojáře. Android Oreo výrazně omezil prostor cokoliv provádět na pozadí 😕 — Location Limits, omezení BroadcastReceiveru nebo zrušení Service na pozadí. Důvodem je větší životnost baterie pro uživatele. Stream k dispozici na <a href="https://www.youtube.com/watch?v=MOHVrrEAQZE">https://www.youtube.com/watch?v=MOHVrrEAQZE</a>.</p><p>Skočili jsme také na přednášku od <a href="https://medium.com/u/7bef290f1d79">Hadi Hariri</a> o Kotlinu — <strong>What can Kotlin do for me?</strong>. Jelikož v The FUNTASTY již pracujeme s Kotlinem 🤓, bylo to pro nás jen jednoduché zopakování základů. Pokud se Kotlin teprve učíte, koukněte na stream <a href="https://www.youtube.com/watch?v=YbF8Q8LxAJs">https://www.youtube.com/watch?v=YbF8Q8LxAJs</a>, který ve 30 minutách shrnuje podstatné základy Kotlinu.</p><p>Velký ohlas sklidila přednáška od <a href="https://medium.com/u/7f2ab73b39f8">Sara Robinson</a> na téma <strong>ML APIs by Example</strong>, která ukazovala, jak použít Machine Learning 📚, aniž byste museli plně rozumět celé problematice ML. Mluvila o tzv. Democratizing machine learning. Video najdete na <a href="https://www.youtube.com/watch?v=hJtTdunppn4">https://www.youtube.com/watch?v=hJtTdunppn4</a>.</p><p>Poslední talk prvního dne nesl název <strong>Introducing ARCore: Augmented Reality at Android Scale </strong>od Toma Saltera. Docela jsme se na talk těšili, protože ARCore je velmi horké téma na poli Androidu od doby, co Apple zveřejnil ARKit. Bohužel bylo pouze shrnuto, co je v dokumentaci na internetu a vesměs žadná nová informace 😐. Stream tady <a href="https://www.youtube.com/watch?v=rFbcOGuDMPk">https://www.youtube.com/watch?v=rFbcOGuDMPk</a>.</p><h3>Den 2</h3><p>Druhý den začal opět Keynote, tentokrát mnohem zajímavějším, protože byl hlavně o Google Cloud a o novém Google Assistentovi, o kterého už můžeme říci, že konkurenční Siri od Apple hravě strčí do kapsy. Bohužel musíme říci, že program druhého dne nebyl tak atraktivní a spěchali jsme už zpátky do Brna, proto jsme stihli jen pár talků.</p><p>Zajímavý talk měl <a href="https://medium.com/u/736d2e87b505">Amit Chopra</a> na téma <strong>Google Developers Agency Program</strong>. Mluvil hlavně o tom, jak vybírají agentury do programu a jaké výhody program umožňuje — EAP nebo třeba 1:1 online support přímo od Google. Bohužel záznam není.</p><p>Polední přednáška od <a href="https://medium.com/u/57387f5314d0">Robert Kubis</a> na téma <strong>Containers, Kubernetes and Google Cloud</strong> živě ukazovala, jak jednoduché je spravovat kontejnery v Google Cloud. Mám pocit, že brzy Heroku vyměníme právě za Google Cloud. Záznam najdete na <a href="https://www.youtube.com/watch?v=mhYJ1AX4dG4">https://www.youtube.com/watch?v=mhYJ1AX4dG4</a>.</p><p>Docela jsme se těšili na talk od <a href="https://medium.com/u/d5885adb1ddf">Florina Muntenescu</a>, která mluvila o <strong>Architecture Components</strong>, bohužel to byl jen rychlý průlet toho, co všichni známe. Záznam zde <a href="https://www.youtube.com/watch?v=Ts-uxYiBEQ8">https://www.youtube.com/watch?v=Ts-uxYiBEQ8</a>.</p><h3>Shrnutí</h3><p>Google ví, proč takové konference pořádá — spojuje vývojáře a ukazuje jim nástroje, které mají používat, aby vytvořili lepší a rychlejší aplikace. K tomu skvělá organizace, workshopy, zábavné koutky s IoT nebo skvělé jídlo dělá z Google Developer Days jednu z must-attend konferencí.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LEX9xXOODyc4PC8x7kbO-g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iX0CZqz5r5EOZiw5jYbcSw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pQoB4subwjWZWxkD6PoELg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cwQ4vgq8r2x7FZH2phw3Rg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-W_7MvMnR6O6yU1JmeYFQA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pdUwmcMUXS9DqMx0mM4jEQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9bd645eb4a07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The FUNTASTY Hackathon Day 2017  ⌨️]]></title>
            <link>https://medium.com/@radimvaculik/the-funtasty-hackathon-day-2017-%EF%B8%8F-39691dda4f2?source=rss-dc7f55510e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/39691dda4f2</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[apple-tv-os]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[mac-os-x]]></category>
            <dc:creator><![CDATA[Radim Vaculík]]></dc:creator>
            <pubDate>Mon, 03 Jul 2017 12:59:22 GMT</pubDate>
            <atom:updated>2017-07-03T12:59:22.153Z</atom:updated>
            <content:encoded><![CDATA[<p>Last Friday we hosted our first internal hackathon. Our goal was to create an application or tool in teams of <strong>3 members</strong> within <strong>12 hours</strong>. The hacking was finished with presentation of all projects and results announcement. <strong>Six teams</strong> competed and created <strong>6 awesome projects</strong>.</p><p>One of the best projects is <strong>TasteWatch</strong> from <strong>Strong Dept.</strong> team. TasteWatch is a macOS app, which displays running builds on <a href="https://www.bitrise.io/">Bitrise</a> with option to cancel the build. What a handy tool! 👏</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*g0Ul3SzM11MOGisRgc_SFA.png" /><figcaption>TasteWatch macOS app</figcaption></figure><p>The next really good project is tvOS app called <strong>Currant</strong> 🍇 from <strong>RAP</strong> team. Currant is a dashboard with all important informations such a meeting room calendar, best <a href="https://slack.com/">Slack</a> messages or <a href="https://toggl.com/">Toggl</a> leaderboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Krbo2k0KKtYee5-min54A.png" /><figcaption>Currant tvOS app</figcaption></figure><p>The winning app 🥇 called <strong>Funspace</strong> from team <strong>Božský kopeček</strong> is a simple Android and iOS application for vacation management in our company. So we can easily add vacation 🏖️ or sickday through the app and see the number of days left.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*IUDpbBHHwlhaRES0o_4N7w.png" /><figcaption>Funspace iPhone app</figcaption></figure><p>We had a such great day ☀️ and we will do hackathon days more often in the future. Do you like any of apps we created? Share it with us! 👍</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39691dda4f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git — The FUNTASTY’s rules]]></title>
            <link>https://medium.com/@radimvaculik/git-the-funtastys-rules-a37bf29da4e1?source=rss-dc7f55510e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/a37bf29da4e1</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Radim Vaculík]]></dc:creator>
            <pubDate>Tue, 14 Feb 2017 09:02:00 GMT</pubDate>
            <atom:updated>2017-02-14T09:02:00.545Z</atom:updated>
            <content:encoded><![CDATA[<p>The FUNTASTY, as the company, exists for more than 4 years now and we started with proper startup spirit. You know that — commit messages like “fix” and “typo”, <strong>git-flow</strong> was a dirty word and <strong>code review</strong> was a waste of time, because we are mobile dev heroes, right? So we decided to create some rules to avoid these situations.</p><pre>fd851820 reformat<br>4c2eaa9e reformat<br>95efabc6 reformat<br>53374c39 Fix typo<br>d12fc502 reformat overrides<br>87622ab4 reformat override<br>44a0fde6 remove inject and reformat overrides<br>53b8dbe9 reformat overrides<br>be5ad52e Fix typo<br>22d4ce5d reformat overrides<br>51d907da reformat layout<br>07eb74d7 fix method name typo<br>b6b31742 generalize and reformat models<br>d07003f9 fix typo</pre><p>As we grew, we realised that we need to change it and we need to bring some <strong>rules</strong> — especially when there are already about <strong>20 developers</strong> and more than <strong>100 git repos</strong> in our company.</p><p><strong>There are most of the rules that we have agreed on and began to practice:</strong></p><ul><li>We use <strong>master</strong> and <strong>develop</strong> branch — these branches are protected, so we can’t delete them. Also, we can’t commit directly into these branches. Only way to contribute is through <strong>pull request</strong>.</li><li>We can create <strong>any branch</strong>, but this branch must begin with <strong>feature</strong> or <strong>hotfix</strong> prefix. For example feature/user-service-refactor .</li><li><strong>Commit message</strong> must be verbose, with title and content.</li><li>Each feature or hotfix can be merged via pull request, but only after proper <strong>code review</strong> and after <a href="https://blog.thefuntasty.com/how-we-adopt-bitrise-in-our-company-66eb94300e65"><strong>successful CI build</strong></a>. The PR with new feature or hotfix points to <strong>develop.</strong></li><li>If we want to make a <strong>release</strong>, we can grab develop any time and make PR from <strong>develop</strong> to <strong>master</strong>. We use <strong>git-tag</strong> for tagging versions in the repo.</li></ul><p>We use <a href="https://bitbucket.org/">Bitbucket</a> and we are happy with it — of course because of pricing. There is also integration between <strong>Bitbucket</strong> and <strong>JIRA</strong>, which we use for the task &amp; time tracking.</p><p>Our rules are not <strong>complicated</strong> or <strong>difficult to understand</strong> and to be honest, it’s a such relieve that we don’t need to think about these things (e.g. inconsistency between projects, meaningless commit messages, …) anymore and we can start focus on more interesting bits.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a37bf29da4e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android Testing — Timeouts]]></title>
            <link>https://medium.com/@radimvaculik/android-testing-timeouts-498c2bc2da41?source=rss-dc7f55510e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/498c2bc2da41</guid>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Radim Vaculík]]></dc:creator>
            <pubDate>Fri, 25 Nov 2016 08:59:47 GMT</pubDate>
            <atom:updated>2016-12-05T12:18:39.867Z</atom:updated>
            <content:encoded><![CDATA[<p>In our company, we try to write unit and integration/instrumentation tests for each component of the Android app. Unit tests are simple to write, because it’s basically Java-only test. It’s quick, short and lightweight. But on the other hand, there are lots of issues with Android instrumental tests — you need an emulator, which is pain itself. The runtime of instrumentation tests is longer in comparison to unit tests and also, there are some troubles with flaky tests.</p><p>One more problem are <strong>stuck tests</strong>. The default timeout for each test is <strong>0L</strong>. So the test can be run indefinitely and your tests can’t be finished.</p><p>There are couple solutions how you can prevent this problem.</p><p>The first (and really nice) solution is to use <strong>timeout</strong> parameter in @Test annotation. The time is in milliseconds.</p><pre><strong>@Test(timeout=100)</strong><br>public void myTestFunction() { ... }</pre><p>The other solution is to use <strong>@Rule</strong> annotation. This is really handy if you want to setup timeout for the whole testcase (for every test in the file).</p><pre>public class MyTests {<br>   <br><strong>    @Rule<br>    public Timeout globalTimeout = Timeout.seconds(10);</strong><br><br>    @Test<br>    public void test1() throws Exception {<br>        ...<br>    }<br><br>    @Test<br>    public void test2() throws Exception {<br>        ...<br>    }<br>}</pre><p>If the timeout is reached, you’ll get TimeoutException.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*WsXC2qnQf8OlhNunq3Lrcg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=498c2bc2da41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we adopt Bitrise in our company ]]></title>
            <link>https://medium.com/@radimvaculik/how-we-adopt-bitrise-in-our-company-66eb94300e65?source=rss-dc7f55510e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/66eb94300e65</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[bitrise]]></category>
            <dc:creator><![CDATA[Radim Vaculík]]></dc:creator>
            <pubDate>Thu, 27 Oct 2016 11:42:23 GMT</pubDate>
            <atom:updated>2016-10-27T11:49:33.086Z</atom:updated>
            <content:encoded><![CDATA[<p>As a company, we grow really really fast. We hired more developers, we did more projects. We also improve our code style and we started to write unit and integration tests. We use <a href="https://bitbucket.org/">Bitbucket</a> as our CVS to store all the code. We also start to use <a href="https://github.com/nvie/gitflow">Git-flow</a> — we use different branches for each feature/bugfix change and we also do pull-request review.</p><p>And there is our <strong>problem</strong> — as reviewer, I’d like to see in Bitbucket, if all tests are passed or not and I’d like to try the build with new feature on my phone. There are couple ways — you can checkout the code, build it, run tests on your local and test it — but it’s long process.</p><p>So we decided to <strong>automate</strong> it with any existing CI solution. We had couple conditions for new CI system:</p><ul><li>not extremely expensive</li><li>Android &amp; iOS support</li><li>open-source</li><li>well documented</li><li>perfectly working blackbox</li><li>support</li></ul><p>We tried <a href="https://travis-ci.org/">Travis CI</a>, <a href="https://circleci.com/">Circle CI</a> or <a href="https://jenkins.io/">Jenkins</a> as self-hosted solution. We had also problem to find a solution with iOS support, because you need to have iOS hardware to run Xcode and compile iOS app.</p><p>We exclude <strong>Travis CI</strong>, because of the price — it starts from $129. <strong>Circle CI </strong>does not support one solution for both platform — you need to pay for Linux and iOS box separately. <strong>Jenkins</strong> is not outsourced solution and we would like to avoid to manage any server.</p><p>And then, we found <a href="https://www.bitrise.io/"><strong>Bitrise.io</strong></a><strong>!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/199/1*K08Vu3YHBNHPW28Dsj_Xog.png" /><figcaption>Bitrise.io</figcaption></figure><p>We started with <strong>14-days trial plan</strong>, so we tested all our apps, all looked great. It’s really easy to add a new app — you need to link Bitbucket account with Bitrise, pick some options and after 10 minutes, you can see the first build. Now, we use <strong>1 concurrency</strong> plan <strong>$50</strong> with <strong>unlimited builds</strong>. There is only condition — one build can run only <strong>45 minutes</strong>, but it’s absolutely OK for our purpose.</p><p>Also, if you <a href="https://github.com/bitrise-io/bitrise-contrib">contribute</a> with your code to Bitrise, you will get <strong>50% discount</strong> — so much wow!</p><p>For each app, you can setup own <strong>workflow</strong> with steps. It’s like LEGO, you can build your own workflow really easily. You can also use your <strong>own steps </strong>— another wow!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fq586goe_SyY4ojXt6Yx5g.png" /><figcaption>Bitrise workflow manager</figcaption></figure><p><strong>Bitrise</strong> community is great — you can chat with Bitrise guys on <a href="http://bitrise.slack.com/">Slack</a>. And if you want awesome stickers, just send them a message and they’ll send you some ;)</p><p>Conclusion: <strong>I recommend Bitrise as mobile development CI solution.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66eb94300e65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gradle, please]]></title>
            <link>https://medium.com/@radimvaculik/gradle-please-1ecfd50e9450?source=rss-dc7f55510e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ecfd50e9450</guid>
            <category><![CDATA[gradle]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[libraries]]></category>
            <dc:creator><![CDATA[Radim Vaculík]]></dc:creator>
            <pubDate>Sat, 28 Feb 2015 20:01:51 GMT</pubDate>
            <atom:updated>2015-02-28T20:01:51.876Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are good Android developer, you are using <a href="http://developer.android.com/tools/studio/index.html">Android Studio</a> with Gradle. Gradle is new build system for Android application. One of advantages is external loading of libraries. Basically, you can just add one line into your build.gradle file and your library is included. Easy, huh? But do you know precisely that line?</p><blockquote><a href="http://gradleplease.appspot.com/">http://gradleplease.appspot.com/</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZDqRAZV9agfUPUgJ6uO5sg.png" /></figure><p>Easily just type name of your library and results will appear below. You shouldn’t miss this website in your bookmarks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ecfd50e9450" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Joda-Time as a full replacement for date and time classes]]></title>
            <link>https://medium.com/@radimvaculik/joda-time-as-a-full-replacement-for-date-and-time-classes-5f004432b346?source=rss-dc7f55510e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f004432b346</guid>
            <category><![CDATA[datetime]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[joda-time]]></category>
            <dc:creator><![CDATA[Radim Vaculík]]></dc:creator>
            <pubDate>Sat, 28 Feb 2015 19:54:42 GMT</pubDate>
            <atom:updated>2015-02-28T19:54:42.405Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m working with date or time in almost each Android application. I was using <a href="http://docs.oracle.com/javase/7/docs/api/java/util/Calendar.html">Calendar</a>, <a href="http://docs.oracle.com/javase/7/docs/api/java/util/Date.html">Date</a>, <a href="http://docs.oracle.com/javase/7/docs/api/java/sql/Time.html">Time</a> classes. But it’s really hard to work with it. For example, if you want to get yesterday’s time as human string, you need to do like:</p><pre>DateFormat dateFormat = new SimpleDateFormat(&quot;dd. MM. yyyy HH:ii&quot;);<br>Calendar c = Calendar.getInstance();<br>c.add(Calendar.DATE, -1);<br>System.out.println(dateFormat.format(c.getDate()));</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*0yNMKhxZPT3bFaDX9aueSw.jpeg" /></figure><p>There is another solution for that — <a href="http://www.joda.org/joda-time/">Joda-Time</a>.</p><blockquote><strong>Joda-Time</strong> provides a quality replacement for the Java date and time classes.</blockquote><pre>DateTime dt = new DateTime();<br>System.out.println(dt.plusDays(-1).toString(&quot;dd. MM. yyyy HH:ii&quot;));</pre><p>All you need to do is add one line into <strong>build.gradle</strong>:</p><pre>compile &#39;net.danlew:android.joda:2.5.0&#39;</pre><p>And add one line into your <strong>Application</strong> file:</p><pre>JodaTimeAndroid.init(this);</pre><p>Easy, right? So don’t scare about new library for date and time. Joda is really handy and easy to use.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f004432b346" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Need API for your app? Use Slim!]]></title>
            <link>https://medium.com/@radimvaculik/need-api-for-your-app-use-slim-e20a8bbc729d?source=rss-dc7f55510e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/e20a8bbc729d</guid>
            <category><![CDATA[slim]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Radim Vaculík]]></dc:creator>
            <pubDate>Sat, 28 Feb 2015 19:35:17 GMT</pubDate>
            <atom:updated>2015-02-28T19:35:17.234Z</atom:updated>
            <content:encoded><![CDATA[<p>As Android developer, you need server API almost always, then you developing application. Best solution is JSON or XML data type. And because I love PHP as programming language, I decided to use <a href="http://www.slimframework.com/">Slim framework</a>.</p><blockquote>Slim is a PHP micro framework that helps you quickly write simple yet powerful web applications and APIs.</blockquote><p><strong>Example</strong> is worth more than 1000 words:</p><pre>&lt;?php<br>$app = new \Slim\Slim();<br>$app-&gt;get(&#39;/hello/:name&#39;, function ($name) {<br>    echo &quot;Hello, $name&quot;;<br>});<br>$app-&gt;run();</pre><p><strong>Yep, that’s it!</strong> So simple and elegant. And installation is simple as well thanks <a href="https://getcomposer.org/">composer</a>:</p><pre>composer require slim/slim</pre><pre>&lt;?php<br>require &#39;vendor/autoload.php&#39;;</pre><p>Check <a href="http://www.slimframework.com/">http://www.slimframework.com/</a> for more information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e20a8bbc729d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Easy OpenVPN for your Ubuntu/Debian]]></title>
            <link>https://medium.com/@radimvaculik/easy-openvpn-for-your-ubuntu-debian-54984fe9af1f?source=rss-dc7f55510e04------2</link>
            <guid isPermaLink="false">https://medium.com/p/54984fe9af1f</guid>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[debian]]></category>
            <category><![CDATA[vpn]]></category>
            <dc:creator><![CDATA[Radim Vaculík]]></dc:creator>
            <pubDate>Sat, 28 Feb 2015 19:19:30 GMT</pubDate>
            <atom:updated>2015-02-28T19:19:30.333Z</atom:updated>
            <content:encoded><![CDATA[<p>I have one VPS in Sweden for personal usage. Since I’m in London, UK, there are a LOT of website with denied access. So I decided to create VPN tunnel through my VPS in Sweden.</p><p>I searched, how to easily install and setup VPN, because manual setup is hell for me (noob, I know). After couple hours of searching, I found this solution:</p><pre>wget http://git.io/vpn --no-check-certificate -O openvpn-install.sh; chmod +x openvpn-install.sh;</pre><p>After download just run SH file:</p><pre>sudo ./openvpn-install.sh</pre><p>Follow instruction on screen and after 60 seconds, you have working VPN.</p><p>If you want to add more users, just run command again.</p><p><em>Source: </em><a href="https://vpnreviewer.com/openvpn-howto-debian-ubuntu-vps"><em>https://vpnreviewer.com/openvpn-howto-debian-ubuntu-vps</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54984fe9af1f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>