<?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 Sérgio Santos on Medium]]></title>
        <description><![CDATA[Stories by Sérgio Santos on Medium]]></description>
        <link>https://medium.com/@sdsantos?source=rss-a487b3974f1b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8U_KuHlYRaECzSz1X2tHOA.jpeg</url>
            <title>Stories by Sérgio Santos on Medium</title>
            <link>https://medium.com/@sdsantos?source=rss-a487b3974f1b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:06:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sdsantos/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[Introducing Envelop]]></title>
            <link>https://medium.com/blocoio/introducing-envelop-cb7b764710a5?source=rss-a487b3974f1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb7b764710a5</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[blockstack]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Sérgio Santos]]></dc:creator>
            <pubDate>Fri, 19 Jul 2019 17:31:44 GMT</pubDate>
            <atom:updated>2019-07-19T17:31:44.659Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*VzBTGHyxZGn_2UGMpPTURw.png" /></figure><p>TL;DR: We launched a new app to easily share private files called Envelop. Try it out at <a href="https://envelop.app/">envelop.app</a></p><p>To keep up-to-date with the industry, we’re always researching for new ways of building apps. And one movement that got our attention was decentralized apps, or dapps as they’re commonly called. They’re usually associated with crypto currencies, and sometimes get a bad reputation because of it.</p><p>Decentralized apps don’t rely on a single server or entity to work. They’re built with pear-to-pear mechanisms, usually built with the blockchain, to be able to save and send data, while ensuring trust between the pears.</p><p>It sounds complicated, but they bring important advantages, even for regular app users. Being able to own your data, have privacy and not rely on the benevolence of a single company are advantages that shouldn’t be available only to tech-savvy people.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*kqmLXgBRKVeitmvt0fJR1Q.png" /></figure><p>So we looked for good use cases for our first decentralized app. Something that we would use regularly, and could have a broad audience. And we remembered about file-sharing apps. How they’re business model is overcharging users for storage, storage you never actually control.</p><p>And we researched technologies for how to build it, coming across <a href="https://blockstack.org/">Blockstack</a>. It interested us because it only used the blockchain for the hard decentralization problems, like authentication and routing. For the rest, it builds upon the current web technologies we use and know how to scale.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*XD8rmBCmRYWaKNLZFFsniQ.png" /></figure><p>That’s the story behind Envelop, an app to easily share private files without losing their ownership.</p><p>Just drop a file, get a download link and share it.</p><p>As a reviewer told us: “In all sincerity, if my grandmother was to be alive at this moment, she would testify to how easy it is to use the Envelop file-sharing service just to emphasize how simple the user interface is.” (<a href="https://steemit.com/steempress/@mistakili/envelopfilesharingservice-welcometodecentralizedeverything-mz50egpmqv">source</a>)</p><p>We partnered with <a href="https://twitter.com/joaodiogocosta">João Diogo Costa</a> to build both an Android and a Web apps.</p><p>To get users going with decentralized apps, Blockstack is offering their own free unlimited storage. But at any time you can configure your own storage hub and all Blockstack apps start storing their data somewhere you own. It’s still a bit techy process to setup your own storage hub, but we believe it’s going to become easier in the near future.</p><p>So, try out our <a href="https://envelop.app/">Web app</a> and our <a href="https://play.google.com/store/apps/details?id=app.envelop">Android app</a>. We’re looking forward to your feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb7b764710a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blocoio/introducing-envelop-cb7b764710a5">Introducing Envelop</a> was originally published in <a href="https://medium.com/blocoio">Bloco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Random thoughts about the Web Summit]]></title>
            <link>https://medium.com/@sdsantos/random-thoughts-about-the-web-summit-ba69e15459d7?source=rss-a487b3974f1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba69e15459d7</guid>
            <category><![CDATA[portugal]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[conference]]></category>
            <dc:creator><![CDATA[Sérgio Santos]]></dc:creator>
            <pubDate>Wed, 17 Oct 2018 12:42:19 GMT</pubDate>
            <atom:updated>2018-10-17T12:49:04.936Z</atom:updated>
            <content:encoded><![CDATA[<p>Conclusions I’ve been sharing on the conference stay in Portugal</p><p><strong>It’s not good for startups</strong></p><p>It’s very unlikely they will get investment or new clients at the conference. There’s too many startups each day. Investors, company executives and speakers are taken to private rooms and events, they’re not roaming around the startup booths. A very small percentage gets a chance to pitch (and pays well for it) and only the top 10 will get some media attention.</p><p><strong>Startups are the product being sold</strong></p><p>All the other exhibitors at the conference are there to sell things to the startups. Companies that offer tech infrastructure, development services, or organisations that want to convince startups about their accelerator/city/country. It’s surprising startups even have to pay to attend the conference. Startups should just be selected, get a free entry and expenses covered.</p><p><strong>It’s good for big companies</strong></p><p>Big companies that sell their services to large audiences and governments. And that need to hire a lot of engineers. That’s why developers are given free tickets for the conference: <a href="https://websummit.com/open-source">https://websummit.com/open-source</a>. Plus, those companies also know that startups founders make great employees after the likely failure.</p><p><strong>The side events are the best part</strong></p><p>The evening meetups are the best opportunity to meet new people. Small groups, calm environments and focused discussions. But there are many and all happening at the same time, so you’ll have to prepare in advance and gamble on those worth it.</p><p><strong>It’s a safe investment for Lisbon/Portugal</strong></p><p>Even if it’s very expensive to bring Web Summit, Lisbon and Portugal will get their investment back in foreign money being spent and large companies investing in Lisbon. But it’s not an investment in our startup ecosystem, and should not be advertised as such.</p><p><strong>Foreign companies skew the market</strong></p><p>Many foreign tech companies open offices in Portugal to hire from our talent pool. Web Summit has accelerated this. It helps the economy, creates more opportunities for engineers and it raises salaries. But it puts pressure on the startup ecosystem. It’s unlikely that the current big Portuguese startups would have been able to grow as fast, if they were just starting out now. And it all the tech companies we have in Portugal are foreign, the profit won’t stay here.</p><p><strong>More centralisation</strong></p><p>It’s another initiative for Lisbon, with no clear strategy for the rest of the country. Is the government going to attract other tech conferences to other regions as well? Or they’ll continue to say that other cities should copy the “Lisbon model”, but with none of the investment?</p><p><strong>There’s nothing special about Web Summit</strong></p><p>Some past Portuguese conferences could have become what Web Summit is now if they had investment at the right time (SHiFT, Switch, PFC, Upload, i9, LIS…). But we prefer to buy an already peaked conference than to invest in our own communities, bottom-up. Like we also prefer to attract IKEAs and Teslas than to invest to create our own. It’s more expensive this way, but it doesn’t require a medium/long term strategy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba69e15459d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Selling automated tests to colleagues, managers and clients]]></title>
            <link>https://medium.com/blocoio/selling-automated-tests-to-colleagues-managers-and-clients-909810274089?source=rss-a487b3974f1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/909810274089</guid>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Sérgio Santos]]></dc:creator>
            <pubDate>Tue, 31 Jul 2018 08:58:43 GMT</pubDate>
            <atom:updated>2018-07-31T10:42:23.533Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QC5_B4wBahFSF9WTV3IR8A.jpeg" /></figure><p>This is not an article to explain what are automated tests and why you should write them. If the title got your attention, chances are you already know that. But you’re having a hard time convincing others why they should invest in a automated test suite. It’s not an easy sell, specially for mobile apps, where testing is harder to do and has been less advocated.</p><p>As an external Android developer, I’ve discussed testing with clients, project managers and developer teams. It’s a different conversation every time, but I gathered some tips that have helped me in the process.</p><h3>Colleagues</h3><p><strong>Start slowly<br></strong>Not all developers write automated tests, unfortunately. And if you never done it before, it can be daunting. It’s a new skill to learn and added work. It’s important to onboard them into testing. Rather than start testing everything, discuss with your colleagues where they feel more risk. Which parts of the project they aren’t as confident in? It’s easier to convince to test those parts first.</p><p><strong>Be the example<br></strong>This goes without saying: you need to set the example. Write tests for your new features, write regression tests for bugs you fix, and avoid breaking existing tests.</p><p><strong>Keep improving the infrastructure</strong><br>One of the hard parts of writing automated tests is all the infrastructure required. API calls need to be mocked, dummy objects generated, distinct databases and preference files, etc.. You don’t need to start with everything in place. But it’s important to keep improving the stack, always make the next test easier to write. And spend some time implementing Continuous Integration, it will keep things in shape and save everyone’s time.</p><h3>Managers</h3><p><strong>Don’t hide the overhead, discuss it</strong><br>Overhead is the main concern of project managers not accustomed to automated testing. They fear spending effort on something invisible to stakeholders. Your reaction might be to write tests anyway and hide it from the manager. Some features might even require that you write tests to check if it’s working correctly. But the best approach is again to discuss where the main challenges of the project lie and to focus the testing efforts there.</p><p><strong>Sell stability and predictability</strong><br>As projects grow in size and complexity, delivering on time and avoiding bugs gets harder. Stability and predictability become key in the manager’s mind. Which means it’s easier to convince managers to spend time writing tests. And the results of those efforts become more noticeable.</p><p><strong>Don’t skip manual QA</strong><br>Note that automated tests don’t substitute manual testing. It’s worth having a step where someone other than the developer runs through the application.</p><h3>Clients</h3><p><strong>No need to discuss it<br></strong>Unless the client has technical knowledge, I don’t feel the need to discuss automated tests with them. Our project proposals mention it on our Process section. But it’s not something optional and it doesn’t have a specific cost associated with it.</p><p><strong>The advantages will be felt<br></strong>Clients will likely not notice their app has an automated test suite. They will feel the advantages over time. Less bugs appearing or re-appearing, smoother deliveries, but they won’t be able to tell what’s causing it. Unless the client passes the project to another team and they compliment the fact it has tests. :)</p><p>After all this talk about writing tests, it’s important to remember they are one part of building software. Don’t spend all of your social capital on it. Other factors like documentation, communication, experience and team cohesion also influence the quality of the app you’re developing.</p><p>Good luck selling!</p><p><em>Originally posted at </em><a href="https://www.bloco.io/blog/2018/selling-automated-tests-to-colleagues-managers-and-clients"><em>Bloco’s Blog</em></a><em> on July 16, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=909810274089" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blocoio/selling-automated-tests-to-colleagues-managers-and-clients-909810274089">Selling automated tests to colleagues, managers and clients</a> was originally published in <a href="https://medium.com/blocoio">Bloco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our Android Masterclass at The New Digital School]]></title>
            <link>https://medium.com/blocoio/our-android-masterclass-at-the-new-digital-school-8a309bdad98f?source=rss-a487b3974f1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a309bdad98f</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[teaching]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[schools]]></category>
            <dc:creator><![CDATA[Sérgio Santos]]></dc:creator>
            <pubDate>Wed, 20 Sep 2017 09:56:46 GMT</pubDate>
            <atom:updated>2017-09-20T09:56:46.325Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z6zmWow8nQPTFSFxcr6OGw.jpeg" /></figure><p><a href="http://thenewdigitalschool.com/">The New Digital School</a> challenged us to organize an Android masterclass. If you don’t know about them, it’s a different kind of school with an innovative yearly course, student-centred. What does that mean? They help people discover what skills can advance their career and build a curriculum around them. See this video to <a href="https://www.facebook.com/newdigitalschool/videos/1812760672351430/">learn more</a>.</p><p>So, the students asked to learn more on how to building mobile apps. And not just the concepts, but to actually be able to design and build an app, through a 3-days workshop.</p><p>We had already done a 2-days introduction to Android development before, but most attendees had an engineering background. In this case, students had a mixed background, leaning towards design and with less programming experience. Thus, we decided to try out a mixed teaching approach. Together we would show how to build an Android app from scratch, with both the design and the programming knowledge required.</p><p>Like any experiment, we kept readjusting our plan and expectations throughout the workshop. Programming concepts can feel daunting to students, until they try them and understand their purpose. As an engineer, I’m used to work on top of abstractions, without much concrete matter to guide me on. But to keep non-engineers on board, it’s important to be simple and concrete on what we’re trying to achieve. Link concepts with their results.</p><p>We realised that, on a 3 day workshop, we could skip complex Android concepts like RecyclerViews. Simpler methods can achieve similar results, while helping students maintain a sense of progress. If all goes well, students will be the ones asking for features missing on their app, instead of following a theoretical plan of learning topics.</p><p>Mixing both programming and design also brings its own advantages:</p><ul><li>Using different parts of your brain helps you get through an intensive workshop;</li><li>It gives a broader picture of what building an app is like.</li></ul><p>Not everyone finished with an app released by the end of the masterclass. Some preferred to use their last day improving app designs, with their new knowledge. But here are 2 apps released by the students:</p><ul><li><a href="https://play.google.com/store/apps/details?id=com.thenewdigitalschool.ana.random">Random</a></li><li><a href="https://play.google.com/store/apps/details?id=es.elcolorado.android">Color by Elcolorado</a></li></ul><p>It’s great for design students to learn how to build an app by themselves. But there are other advantages from learning app development. You understand better the effort and constraints that come from design decisions, and you gain the confidence to dig into the code and iterate on front-end details by yourself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qGSeAEn0AWceF-y2ez-Q1w.jpeg" /></figure><p>This kind of training is definitely something we will explore more. So keep an eye out for our next training announcements. In the meantime, if you are looking for an Android training tailor-made for your team, let’s talk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a309bdad98f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blocoio/our-android-masterclass-at-the-new-digital-school-8a309bdad98f">Our Android Masterclass at The New Digital School</a> was originally published in <a href="https://medium.com/blocoio">Bloco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Native or Hybrid Apps — Our advice to clients]]></title>
            <link>https://medium.com/blocoio/native-or-hybrid-apps-our-advice-to-clients-52bce14b4413?source=rss-a487b3974f1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/52bce14b4413</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[hybrid-app-development]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[mobile-apps]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Sérgio Santos]]></dc:creator>
            <pubDate>Mon, 28 Aug 2017 13:20:49 GMT</pubDate>
            <atom:updated>2017-08-28T13:23:08.580Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qgYXEnKR4xZf8Od3ymOByg.jpeg" /></figure><p>A common doubt clients have is whether to develop their mobile apps natively or through a hybrid framework, like <a href="https://ionicframework.com/">Ionic</a>, <a href="https://www.xamarin.com/">Xamarin</a> or <a href="https://facebook.github.io/react-native/">React Native</a>. We focus only on building native Android apps. But we try our best to help with this decision, even if it means losing a project. In this article we explain our thought process.</p><p>First some background. Since iOS and Android became popular, many hybrid frameworks appeared. They pick a popular non-native technology and create a framework to build mobile apps with it. The goal is to build an app once and have it running on all platforms with as few specific changes as possible. There is <a href="https://ionicframework.com/">Ionic</a>, <a href="https://phonegap.com/">PhoneGap</a>, <a href="http://www.appcelerator.org/">Titanium</a> and <a href="https://facebook.github.io/react-native/">React Native</a> based on web technologies (HTML, CSS and Javascript), <a href="http://www.rubymotion.com/">Ruby Motion</a> based on Ruby, and <a href="https://www.xamarin.com/">Xamarin</a> based on Microsoft’s C#.</p><p>Hybrid frameworks are attractive to companies because they can apply existing knowledge into mobile apps. And with a single codebase, there’s potential to save time and effort. But they are aware of the risks of depending on third-party abstractions.</p><p>Here are the factors for and against building apps with hybrid frameworks. You should weigh them on the specificities of the app you’re building.</p><h3>For Hybrid Frameworks</h3><p><strong>Complex mobile back-end</strong></p><p>Non-UI related code is similar between platforms. So if the back-end logic is the biggest component of an app, a hybrid framework should save time. What kind of apps have complex back-ends? Apps that read and write data offline and have complex business logic that can’t be delegated to the server.</p><p><strong>Proof of concept that requires multi-platform</strong></p><p>When building an MVP, you want to keep development expenses low and you need to iterate to get it right. If a product is not validated, we recommend starting out with a single platform. The goal should be to have a great app that does one single thing very well, not 3 features hacked together.</p><p>However, if for some reason the proof-of-concept requires multiple platforms, it’s faster and cheaper to iterate with a hybrid framework. Just don’t forget, to re-evaluate your decision after your MVP is validated.</p><h3>Against Hybrid Frameworks</h3><p><strong>Complex native-feeling UI</strong></p><p>If the front-end is complex and the UI should look and feel native (and most should), a hybrid framework will drag you down. Even if you can write platform specific code, abstractions make problems likelier.</p><p><strong>Deep hardware integrations</strong></p><p>Again, like for the UI, abstractions are the culprit. You won’t have issues getting a photo from the camera or the current user location. But for deep integrations with hardware features (camera, sensors, GPS, NFC, Wifi, …), you’ll need platform specific code and run into problems more frequently.</p><p><strong>Latest OS features</strong></p><p>If you want to be the first integrating with the latest Android and iOS features, a hybrid framework slows you down. And you won’t be able to predict the delay until it gets supported.</p><h3>Current patterns</h3><p>We notice that B2B products lean towards hybrid frameworks, while B2C products lean towards native. But B2B companies that want to step themselves apart on their UI/UX quality, also lean towards Native frameworks.</p><h3>Disclaimers</h3><p><strong>Note 1<br></strong>Some hybrid frameworks handle the shortcomings mentioned above better than others. But in general, the advice holds.</p><p><strong>Note 2<br></strong>Team experience trumps all. An experienced team with any tech should outperform a less experienced team, even with a more adequate technology. This article is for someone building a team or outsourcing the development of a new product. If you already have a team comfortable with a technology, using that technology should get better results than picking something new.</p><p><strong>Note 3<br></strong>Careful on taking tech advice from big companies. With a big enough team you can and likely will write components from scratch. But small teams implementing MVPs don’t have access to the same resources. Take that in mind when reading advice from companies like Google, Facebook, Twitter, Airbnb…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52bce14b4413" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blocoio/native-or-hybrid-apps-our-advice-to-clients-52bce14b4413">Native or Hybrid Apps — Our advice to clients</a> was originally published in <a href="https://medium.com/blocoio">Bloco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We launched intern.camp!]]></title>
            <link>https://medium.com/interncamp/we-launched-intern-camp-1a0529e29809?source=rss-a487b3974f1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a0529e29809</guid>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[summer-internships]]></category>
            <category><![CDATA[university]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Sérgio Santos]]></dc:creator>
            <pubDate>Tue, 30 May 2017 16:46:27 GMT</pubDate>
            <atom:updated>2017-05-30T16:46:27.836Z</atom:updated>
            <content:encoded><![CDATA[<p>Our new platform for short-term internships is live 🍾</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2NWQf41es-QKuFC-Zm4vsg.jpeg" /><figcaption>The platform unveiling at the launch party.</figcaption></figure><p>Last week, on May 22, we organised a small party at <a href="http://www.nestcollective.co/">Nest</a> for the launch of <a href="https://intern.camp/">intern.camp</a>. It was just a small friendly gathering, but we wanted to mark the date for posterity.</p><p>Six companies joined the platform at the start: <a href="https://intern.camp/whitesmith">Whitesmith</a>, <a href="https://intern.camp/feedzai">Feedzai</a>, <a href="https://intern.camp/mimicry">Mimicry Games</a>, <a href="https://intern.camp/10digital">10.digital</a>, <a href="https://intern.camp/ubiwhere">Ubiwhere</a> and, of course, <a href="https://intern.camp/nestcollective">Nest Collective</a> (our thanks to all). Together they have 8 internships available and student applications are already coming in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7s3GOy6W_RVRNPkkCQrJhA.png" /><figcaption>The 6 initial companies and what you can learn from them.</figcaption></figure><p>Starting a new product like this also comes with its challenges and constraints. We want to validate there’s a real need behind <em>intern.camp</em>. So we decided to start only with companies from Coimbra (our home city) because we can reach most university students here. And we focused on tech companies because we know them better. But if all goes well with the first internships and there’s demand, we want to expand into other cities and markets.</p><p>And since this is a part-time project for us, we asked <a href="http://jeknowledge.pt/">jeKnowledge</a> to help us move the project forward. As the organiser of <a href="http://www.dotworks.pt/">.works</a>, they know the world of internships well. And has university students themselves and give us their perspective as university students themselves.</p><p><strong>In conclusion</strong></p><p>If you are student, check out our current internships available: <a href="https://intern.camp/">https://intern.camp</a></p><p>If you work at a company, read why you should why provide short-term internships and join the platform: <a href="https://intern.camp/for_companies">https://intern.camp/for_companies</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a0529e29809" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interncamp/we-launched-intern-camp-1a0529e29809">We launched intern.camp!</a> was originally published in <a href="https://medium.com/interncamp">Intern.Camp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The motivation for a short-term internships platform]]></title>
            <link>https://medium.com/interncamp/the-motivation-for-a-short-term-internships-platform-5cc6a64506ce?source=rss-a487b3974f1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cc6a64506ce</guid>
            <category><![CDATA[university]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[summer-internships]]></category>
            <dc:creator><![CDATA[Sérgio Santos]]></dc:creator>
            <pubDate>Thu, 11 May 2017 09:55:03 GMT</pubDate>
            <atom:updated>2017-05-11T09:55:03.053Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lB7X8bNHml7DK7rE1aWclg.png" /></figure><p>Students find university education detached from the industry. They want to learn the skills that are really needed by companies. And they want to experiment with different roles before deciding what job they want.</p><p>On the other side, it’s harder for companies to hire modern workers. They need to be involved with the student community as early as possible to avoid losing touch.</p><p>That’s why short-term internships are becoming popular. But there’s a lot of noise and traps around internships.</p><p>We created <a href="https://intern.camp/">intern.camp</a> to highlight the right short-term internships. The internships where the companies aren’t looking for free labour, but want students to learn, grow and build their careers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cc6a64506ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interncamp/the-motivation-for-a-short-term-internships-platform-5cc6a64506ce">The motivation for a short-term internships platform</a> was originally published in <a href="https://medium.com/interncamp">Intern.Camp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best resources (books, guides and blogs) for your first product]]></title>
            <link>https://medium.productcoalition.com/best-resources-books-guides-and-blogs-for-your-first-product-97fad363b07e?source=rss-a487b3974f1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/97fad363b07e</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Sérgio Santos]]></dc:creator>
            <pubDate>Wed, 15 Feb 2017 02:26:44 GMT</pubDate>
            <atom:updated>2017-02-15T02:26:44.074Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lCTLDor7hpyRwBgM47D6PQ.jpeg" /></figure><p>As an engineer or a designer, you get most projects already planned out. Someone else decided what the solution will be. You just receive the requirements and implement. You are building a product, but you don’t see the full complexity behind it.</p><p>But if you’re building your own app, or join a small startup, you’ll realize solving a real problem is hard. There are no straightforward tradeoffs as in tech and there are no rule books as in design. And it’s not just coming up with a solution. The final product needs to grow and generate sustainable revenue to survive.</p><p><a href="https://twitter.com/MarioCadeiras">Mário</a>, who will be our intern next year, asked where could he learn more about Product. So we’ve compiled here a selection of resources.</p><p>Product spans many areas: tech, business, marketing, design… And it goes against what your learn in University. It’s iterative, counter-intuitive, and designed to fail-fast. Its complexity also varies, whether you’re working on a new product or on a big product company with a huge team.</p><p>The resources here focus on building a new product, much like the challenges a startup faces.</p><h4>What to build</h4><p>It’s common to start with a concrete idea of what to build. But you should take a step back to check if the problem is worth solving and if your solution is effective. <a href="https://en.wikipedia.org/wiki/Customer_Development">Customer Development</a> is the most popular strategy. To read more about it:</p><ul><li><a href="http://theleanstartup.com/">The Lean Startup</a></li><li><a href="http://www.custdev.com/">The Entrepreneur’s Guide to Customer Development</a></li><li><a href="http://www.nailthenscale.com/">Nail It Then Scale It</a> (the most pragmatic and our favourite)</li></ul><h4>Monetize</h4><p>Specifically on business models, word is you shouldn’t invent new business models. Instead, you should replicate existing ones. For inspiration, <a href="https://www.amazon.com/Art-Profitability-Adrian-Slywotzky/dp/0446692271">The Art of Profitability</a> covers 23 different business models.</p><p>The Business Model Canvas became a popular way of describing and analysing business models. Read the <a href="https://strategyzer.com/books/business-model-generation">Business Model Generation</a> book to know more about the proccess.</p><h4>Iterate</h4><p>Once you’re confident with a direction, with <a href="http://www.gv.com/sprint/">Design Sprints</a> you can quickly iterate and validate concrete solutions. Created by the design team at Google Ventures, this process has spread to the whole industry. You have the official book <a href="http://www.thesprintbook.com/">Sprint</a>, a <a href="https://www.udacity.com/course/product-design--ud509">free course</a> on Udacity, or <a href="https://robots.thoughtbot.com/the-product-design-sprint">Thoughbot’s adaptation</a> together with <a href="https://github.com/thoughtbot/design-sprint">materials</a>.</p><h4>Launch</h4><p>Much can be said about marketing and growing a product. There are some good resources on the blogs section below. But the main takeaway is to <a href="http://www.startuplessonslearned.com/2009/03/dont-launch.html">Don’t launch</a>: avoid the big marketing push until you’re sure you nailed it.</p><h4>Track results</h4><p>As you start getting users, you need to look at your metrics. They’ll tell you if you are on the right path. <a href="http://slideshare.net/dmc500hats/startup-metrics-for-pirates-founderx-may-2016">Startup Metrics for Pirates</a> is the default guide (a <a href="https://www.youtube.com/watch?v=XJRq5cP_xJk">short</a> and a <a href="https://vimeo.com/83962056">long</a> video on the same topic).</p><h4>More</h4><p>Here are some great blogs to follow:</p><ul><li><a href="https://blog.intercom.com/">Inside Intercom</a> (onboarding, product management)</li><li><a href="http://okdork.com/okdork-virgin-guide/">Okdork</a> (growth)</li><li><a href="http://andrewchen.co/">Andrew Chen</a> (retention, growth)</li><li><a href="https://medium.com/@rjs">Ryan Singer</a> (design)</li></ul><p>And I asked on Twitter for suggestions:</p><p><a href="https://twitter.com/f">Fred Oliveira</a></p><ul><li><a href="https://www.ideo.com/post/change-by-design">Change By Design</a>, Tim Brown</li><li><a href="http://www.nirandfar.com/hooked">Hooked: How to Build Habit-Forming Products</a>, Nir Eyal</li><li><a href="http://leahbuley.com/book/">The User Experience Team of One</a>, Leah Buley</li></ul><p><a href="https://twitter.com/Ugo_alves">Hugo Alves</a></p><ul><li><a href="https://foldingburritos.com/">Folding Burritos</a>, Daniel Zacarias</li></ul><p><a href="https://twitter.com/jlft">João Alfaiate</a></p><ul><li><a href="https://medium.com/@dannysauter/what-i-learned-reading-36-blog-posts-about-product-management-fcfd15801ee">Product Management is struggling for a definition</a>, Danny Sauter</li></ul><p><a href="https://twitter.com/jpmgoncalves">João Gonçalves</a></p><ul><li><a href="http://zerotoonebook.com/">Zero to One</a>, Peter Thiel</li><li><a href="http://www.creativeconfidence.com/">Creative Confidence</a>, Tom &amp; David Kelly</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97fad363b07e" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/best-resources-books-guides-and-blogs-for-your-first-product-97fad363b07e">Best resources (books, guides and blogs) for your first product</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 2 user onboarding strategies for mobile apps]]></title>
            <link>https://medium.com/blocoio/the-2-user-onboarding-strategies-4ce377e2be97?source=rss-a487b3974f1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ce377e2be97</guid>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Sérgio Santos]]></dc:creator>
            <pubDate>Thu, 19 Jan 2017 09:55:37 GMT</pubDate>
            <atom:updated>2017-01-19T10:03:09.426Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wCqdJhUAWngcnzwqT0TXBw.jpeg" /></figure><p>Let’s keep talking about app activation. After <a href="https://www.bloco.io/blog/2015/how-to-track-you-app-activation-and-3-tips-to-improve-i">learning how to track your results</a>, it’s time to talk about the most effective way of improving your user’s first experience, the onboarding.</p><p>The goal of onboarding is for the user to go from confused to delighted in the shortest time span possible. Even right after installing a new app, a user is still suspicious if that’s application he/she was looking for. The first experience will tell if he/she keeps the app or uninstalls it right away.</p><p>Yes, a simple and self-explaining UI/UX improves the first experience, but it doesn’t replace a good onboarding process.</p><p>There’s two strategies (that may be combined):</p><h4>Specific Onboarding Screens</h4><p><em>Those initial screens, just for onboarding, different from the rest of the UI.</em></p><p>Best when you have to explain something complex. Something that can’t be understood from a laid-back exploration of the app. Like why you need to ask for a location permission (now with Android M revokable permissions). Or to present a final outcome of using the app, that could take hours or days to be reached.</p><p>Tips:</p><ul><li>Avoid meaningless splash screens</li><li>Keep only one action per screen</li><li>Use images besides text (they explain things faster)</li><li>Present benefits (outcomes), not features</li><li>Leave a way for users to come back to these screens later</li></ul><h4>Interface Tours</h4><p><em>Guiding the user through your UI using tooltips.</em></p><p>Best for simple, utility apps that users want to start using immediately. Or complex interfaces only needed later on, like privacy settings. You can use a library like <a href="https://github.com/worker8/TourGuide">TourGuide</a> to implement them.</p><p>Tips:</p><ul><li>Have a good blank state, that already compels the user to take initiative</li><li>Use reassuring microcopy (next to actions)</li><li>All actions should be reversible (to avoid frustration)</li><li>Avoid too many tooltips and too many actions per screen (always a good rule to follow)</li></ul><p>But more important than implementing a good onboarding experience, is to actually test it. You need to do usability tests with real users, to perfect the process. And then A/B test completely different strategies, while tracking your Activation metrics.</p><p>Need inspiration? Look at these <a href="https://www.useronboard.com/">onboarding teardowns</a> of popular apps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ce377e2be97" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blocoio/the-2-user-onboarding-strategies-4ce377e2be97">The 2 user onboarding strategies for mobile apps</a> was originally published in <a href="https://medium.com/blocoio">Bloco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Signs of Technical Debt in your Android app]]></title>
            <link>https://medium.com/android-news/10-signs-of-technical-debt-in-your-android-app-602d9d27bd71?source=rss-a487b3974f1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/602d9d27bd71</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[technical-debt]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[java]]></category>
            <dc:creator><![CDATA[Sérgio Santos]]></dc:creator>
            <pubDate>Mon, 16 Jan 2017 16:22:44 GMT</pubDate>
            <atom:updated>2017-01-28T11:58:40.600Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*05ZKvqv5BodZCKohA9L8NQ.png" /></figure><p><a href="https://en.wikipedia.org/wiki/Technical_debt">Technical debt</a> creeps up into our software projects. Sometimes we notice it, sometimes we don’t. But the debt is obvious when you’re the new person on a project and you’re trying to make sense of it all. Android app development is prone to the same symptoms all software development can have. General signs like:</p><p><strong>Inconsistent code style</strong></p><p>The most noticeable are variations in indentation, argument wrapping and naming notations.</p><p><strong>Inconsistent naming</strong></p><p>Difference names for the same thing, like having classes named Service, Manager, Helper, Getter and Provider doing the same thing: fetch something from a database.</p><p><strong>Lack of automated tests</strong></p><p>Testing is a complex subject and having tests missing might point to other factors. But usually you can tell the least loved parts of an app from their lack of tests.</p><p>But there are Android specific symptoms we all have seen before. The ones that make us take a deep breath before continuing. Here’s our top 10 signs of Android development technical debt:</p><p><strong>1. Not compiling for the latest SDK</strong></p><p>Or building with the latest build tools.</p><p><strong>2. MultiDex enabled</strong></p><p>Do you really need all those libraries, like Guava or the full Google Play Services suite?Do you know why you need each library and if they are still in use? Which leads us to…</p><p><strong>3. Two or more libraries for the same purpose</strong></p><p>Picasso and Glide, Retrofit and Volley… just pick one of each.</p><p><strong>4. Stuck on an outdated version of a library (or worst, a jar!)</strong></p><p>We know libraries can have bugs, but staying on an old version of a popular library is usually a sign of not enough maintenance.</p><p><strong>5. Random crashes after using the app for some time</strong></p><p>Crashes like OutOfMemory are the consequence of cumulative bad decisions. Those decisions aren’t noticeable individually, but together make the application fragile.</p><p><strong>6. Long Activities</strong></p><p>Who hasn’t seen them? They always start small, but as the project grows, features pile up creating monster Activity classes. And nobody had the time to break them down into fragments or custom views.</p><p><strong>7. Layouts with repeated sections</strong></p><p>“I’ll just copy this section over here…”. Building reusable layout components with custom views and styles takes effort, but it saves time in the long run.</p><p><strong>8. Disorganized values xml files: colors, dimens, strings</strong></p><p>Lack of organization makes it harder to reuse them and to tell which ones are no longer used.</p><p><strong>9. Copy strings inside code</strong></p><p>That’s just lazy 😀</p><p><strong>10. Multiple communications strategies</strong></p><p>Communication between components is a complex challenge that needs many approaches. But you shouldn’t mix callbacks, events and observables all in the same component.</p><p>At any given time, you will have 1 or 2 of these signs appearing on your projects. But if many become a common sight on a project, it’s time to pay back the Technical Debt. If you don’t, the code will continue to get worse on every change, bugs will increase and features will take longer to finish.</p><p>Want to do a more thorough analysis of your project status? Check out <a href="https://github.com/Karumi/AndroidAudit">Karumi’s Android Audit</a> guide list.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F3e491f%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F3e491f%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2ae57c1b4448392f65f474b01a127fbf/href">https://medium.com/media/2ae57c1b4448392f65f474b01a127fbf/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=602d9d27bd71" width="1" height="1" alt=""><hr><p><a href="https://medium.com/android-news/10-signs-of-technical-debt-in-your-android-app-602d9d27bd71">10 Signs of Technical Debt in your Android app</a> was originally published in <a href="https://medium.com/android-news">AndroidPub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>