<?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 AppUnite on Medium]]></title>
        <description><![CDATA[Stories by AppUnite on Medium]]></description>
        <link>https://medium.com/@appunite?source=rss-425a559dfbd9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*BVAGQiAv6kg6iRxvIrmanw.png</url>
            <title>Stories by AppUnite on Medium</title>
            <link>https://medium.com/@appunite?source=rss-425a559dfbd9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:52:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@appunite/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[Our perspective on software development]]></title>
            <link>https://medium.com/appunite-edu-collection/our-perspective-on-software-development-c8059922c6e3?source=rss-425a559dfbd9------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8059922c6e3</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[enterpreneurship]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[AppUnite]]></dc:creator>
            <pubDate>Fri, 09 Apr 2021 12:58:21 GMT</pubDate>
            <atom:updated>2022-07-12T08:07:55.692Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5lZLLUsIGvMcysa4.png" /></figure><blockquote>“Look at the bigger picture” — Francis Underwood, House of Cards</blockquote><p>Over the coming decades and across the world professional tech product builder companies will replace internal product departments.</p><p>SaaS and subscription businesses will emerge in traditional businesses based on innovative products that will increase the productivity and well-being of people.</p><p>All of us will collaborate on ventures they solely believe in, supported by collectives that will help them build their careers and exchange experiences.</p><p>Companies will look for long-term cooperation based on joint venture projects that will solve big problems using technological achievements.</p><h3>Startups are reinventing the wheel all the time</h3><p>A real estate broker who wants to build a second Empire State Building to rent office space, won’t start with hiring an HR department to look for architects and construction workers. Instead, they’ll seek a company with know-how in skyscraper construction.</p><p>There are staggering numbers of founders who can’t take their ideas off the ground because they don’t have the strong technical skills to build out their often disruptive ideas. They sometimes look for a technical founder that isn’t committed the same way to the idea as the original founder is.</p><p>We work with our customers as if we were an internal team. This speeds up time to market as well as focus on the results of the venture. Building highly performant teams is hard, but AppUnite can build them more efficiently because of experience and knowledge of inner motivations of each AppUniter. This reduces risks for founders exposed to building a team from the ground up. Our approach allows us to effectively move starting from product-market validation phases, through finding market-fit and ending with further growth of the product.</p><p>Most startups are losing a lot of energy to build teams responsible for their software, while those startups don’t strictly solve software problems. They should focus on the transformation of the industry they work with. Is it logistics, communication, real estate, housing, medicine, poverty, goods exchange — technology is here to solve human problems. It shouldn’t be an obstacle.</p><h3>AppUnite singular focus</h3><p>Build the best teams to deliver software.</p><p>We are tech veterans that know how to create products, help businesses emerge, and transform their industries. Most software houses are optimizing software creation by standardizing their processes to deliver as many tasks received from a business without taking into account if these tasks are beneficial or harmful to those businesses. From our experience, businesses at different stages have different requirements from tech teams. We would like to build and share best practices on how to create products and teams from the ground up and become the best knowledge center in this area.</p><p>We don’t want to compete with Accenture, Capgemini, Luxsoft, Infosys or Netguru. They are focused on staffing, project execution and skill allocation. We build products and teams around them with our partners to deliver software. We should extract best practices from each team we build, replicate them and further improve the best software creation processes for any business.</p><h3>Improving our service</h3><p>We want to integrate deeply with our customers as in our experience it creates the best results for businesses we work with. We want our intentions to be clear to the partners from the moment we start cooperation — long-lasting cooperation based on mutual gains. Our service needs to be way better than if they created their own product teams. We need to understand their vision, strategy and execute it well with tech context. Understand opportunities we get with the newest technology developments and use it solving business problems. Be focused on the outcomes of the business we aim to help.</p><p>We want to improve overall inefficiencies that exist in the software development sector. As a company we create autonomous teams that can experiment and learn from each other. We want to share this knowledge and experience internally and externally. We want to discuss verbally and in a written form how the products should be created. How to communicate with business, how to understand their problems, how to create environments for experimentation, how to pick the technology, how to transform it, predict problems, solve them, build engineers and product people careers, design software and products — to create best results for the businesses. Only a handful of companies do share the knowledge of how to build the best products. To transform the industry, we need to be the best one.</p><h3>Investors frown upon outsourcing</h3><p>Investors traditionally look for tech teams inside startups. Taking the skyscraper example, the investor should be inspecting the building after it is built, not the team that has built it. Over time, our approach will deliver a more efficient way of creating products, that’s why it will have a positive effect on how our services are perceived by investors. Investors look at ROI, sustainability, effectiveness that in our approach to building teams and products will give much better results. We will be able to reduce the risks that the investors may face by building the team for software development on their own.</p><h3>Finding a talent</h3><p>People want to work in intrusive environments, not in extrusive, corporate ones. The best talents want to feel the purpose of work. They want freedom on what they work on, not punch cards to work from 9–5. They want to see the results of their work and an impact it’s creating on society or businesses. They want to experiment and try different environments looking for the best fit for them. We have a great number of ventures that we work on simultaneously. AppUnite, therefore, is able to meet different, long term needs of talents.</p><p>Teams will always try to keep the talent as long as possible. They know that knowledge that remains with each member can’t be valued, and most questions will be raised when a talent exits the organization. Especially at early stages, that’s something that may kill the business. We are able to address these concerns with a much bigger diversity of people with the same position/experience in our structures.</p><p>We work with a number of products at different stages of their lifecycle. Working closely with clients allows us to create positions in organizations as if they were their own. Therefore, we may create opportunities to grow for AppUniters for their desired career paths, internally create multiple architect, CTO, manager or expert positions with different products we work with. We know the strong and weak sides of each member and it’s never related to maturity. Therefore, will be much better at supporting these careers.</p><p>We will have an opportunity to connect business requirements with talent needs and retain knowledge when transitioning to a new, big opportunity in another product. Creating a workplace based on freedom and responsibility is our great advantage over single product teams.</p><p>A workplace created for people with the same interests, but different backgrounds will boost engineers’, product owners’, QAs’ and designers’ growth.</p><h3>Software houses and talent marketplaces will exist</h3><p>There will always be a certain number of companies that look for an expert or have a project to execute. They exactly know who they are looking for or what they want to build. Software houses and talent marketplaces will exist to solve these companies’ needs. We don’t want to compete with them, we might even look for help from such kind of companies in certain situations.</p><p>Moreover, over time, we will see specialization in software houses work, for instance, there will be specialized e-commerce software houses, IoT software houses, R&amp;D software houses.</p><h3>Our cooperation with partners</h3><p>We need to have partners, not customers. We will open to new kinds of relationships where we will be a joint-venture or exchange shares with organizations we cooperate with. This will create a synergy where AppUnite investors will care about product value we create and product investors will also care about AppUnite’s value. Moreover, this way we are able to create ESOP plans that traditional early startups have for their early employees. It will even strengthen the intrinsic workplace of the future.</p><p>On the other hand, we will help young businesses with a seed fund, that will allow them to raise funds for their businesses way faster.</p><p>With our approach, we will be able to create sustainable teams working with partners as if they were built from scratch. We are able to think about product needs at different stages and take lessons from previous or other partners’ experiences, something that is not possible in a single product team. It will enable us to work much more efficiently with partners, that will benefit from this cooperation, reducing risks related to software development.</p><p><em>Originally published at </em><a href="https://appunite.com/blog/appunite-long-term-view"><em>https://appunite.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8059922c6e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appunite-edu-collection/our-perspective-on-software-development-c8059922c6e3">Our perspective on software development</a> was originally published in <a href="https://medium.com/appunite-edu-collection">Appunite Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 2019 year summary | AppUnite]]></title>
            <link>https://medium.com/appunite-edu-collection/the-2019-year-summary-appunite-391be2cd38e3?source=rss-425a559dfbd9------2</link>
            <guid isPermaLink="false">https://medium.com/p/391be2cd38e3</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[enterpreneurship]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[AppUnite]]></dc:creator>
            <pubDate>Thu, 20 Feb 2020 10:19:53 GMT</pubDate>
            <atom:updated>2022-07-12T08:07:48.259Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YxSGHEW2DoEx0-JZ" /></figure><p>Dear AppUniters,</p><p>2019 was quite a year! It’s the first time I write such a summary, but as the CEO, I know that change is the only constant. The past year was a year of transition in mindset.</p><p>It was a tough time but we learned that experiment is a way to improve, that mindset is crucial, and we want to work on it. We shifted to unknowns and questioned the status quo.</p><p>It was a time of rebuilding fundaments. We redefined our vision and mission. We have sought core values. We decided to go with meritocracy as a way to make decisions.</p><p>I have had the privilege to work with the most passionate and intelligent people I have ever met. Without you, nothing that I have just mentioned couldn’t be possible. Thank you for the many conversations we had!</p><p>What we achieved in 2019:</p><ul><li>We have started a leadership program. We learned that leadership has many faces and the most important one is serving people,</li><li>Our approach to leadership is to holistically support team members in their growth. There is a lot to improve, but each journey starts with a single step,</li><li>Started working with new recognized clients (e.g. Allegro, CafeX), increased teams for existing clients (Helium Health, Zumba),</li><li>We continued investing in knowledge sharing, not only internally, but also outside the AppUnite; we resurrected the iOS meetup where we invite well-known personalities from the world of iOS/Swift and we strenghten our brand as an Elixir development team in the region,</li><li>Our team grew by 20 new AppUniters, it’s a 25% increase,</li><li>We learned that it’s important to look for people with the same values when recruiting,</li><li>We extended our technical stack by investing in Flutter platform, and we can boast of projects made in this technology,</li><li>We opened a new role — marketing/growth hacking,</li><li>We get to know how marketing should work with people and sales, which isn’t so obvious. Finding the right processes took us a while. We aren’t there yet but we still striving to get better,</li><li>You need to work hard to find a proper purpose for a team, it’s pretty easy to misalign and focus on wrong things when you do work in a dynamic environment. Establishing purpose is important, ensuring that everybody understands that is even more,</li><li>We built up a lot of knowledge on agile, we started to look at what is the right value for consumers. That redefined a way of work with most of our customers and helped us feel more motivated and engaged,</li><li>We have much more experience in how to look at complex systems and how not to make them chaotic! We learned that small improvements are the key to complex systems. We know that elements in the system are dependent on each other, and the system itself,</li><li>We decided to make the office bigger and more comfortable. It was not a management decision, but we decided in a meritocratic way on what we should choose, and what to do next,</li><li>We continued to organize epic parties, we supported it by introducing a budget for integration for teams (it supported many Jager sponsored). Boszkowo is a great place for organizing a retreat party. We finished our year with great Xmas party in Cucina!</li></ul><p>What we have been recognized for in 2019:</p><ul><li>Clutch Top B2B companies in Poland</li><li>Clutch Global 1000 companies</li><li>Diamenty Forbesa 2020</li></ul><p>Thank you for the many conversations we had in 2019. This year feels us special because of the 10th anniversary. Looking back at what we achieved last year, it’s clear to me that the sky is the limit. Whooo! I strive to learn new things with you, dear AppUniters. Because the people who are crazy enough to think they can change the world are the ones who do!</p><p><em>Originally published at </em><a href="https://appunite.com/blog/2019-summary-at-appunite"><em>https://appunite.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=391be2cd38e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appunite-edu-collection/the-2019-year-summary-appunite-391be2cd38e3">The 2019 year summary | AppUnite</a> was originally published in <a href="https://medium.com/appunite-edu-collection">Appunite Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How announce your absences to the team and ensure transparency and readability?]]></title>
            <link>https://medium.com/appunite-edu-collection/how-announce-your-absences-to-the-team-and-ensure-transparency-and-readability-215d65aa0a12?source=rss-425a559dfbd9------2</link>
            <guid isPermaLink="false">https://medium.com/p/215d65aa0a12</guid>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[AppUnite]]></dc:creator>
            <pubDate>Fri, 21 Jun 2019 12:32:55 GMT</pubDate>
            <atom:updated>2022-07-12T08:07:40.070Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oW2PfiXkJG0dmzbO4NHsIA.jpeg" /></figure><p>We recommend using project calendar. It can really helps with tracking important events related to the project, such as: certificates expiration, client’s meetings, release deadlines or team member absences. It brings us a lot of benefits, like transparency and improve our work planning.</p><h4>Absences</h4><p>At ApppUnite we’re using our internal tool called <a href="https://github.com/appunite/absence-bot"><strong>AbsenceBot</strong></a> to track team members absences. Bot adds events to one of our company internal calendars which is available <a href="https://calendar.google.com/calendar?cid=YXBwdW5pdGUuY29tX3VhZDhrcGEwMHU3YnYybDk3aGl1OGo5bWkwQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20">here</a>. The amount of events collected by this calendar is sometimes overwhelming, and sometime interesting information can be hidden. That’s why when absence is accepted it’s better to make a copy of an event to dedicated project’s calendar, to better track those types of event by team members.</p><p>There are no changes in actual process of taking absences, just few additional steps. After your absence is accepted, chatbot is automatically creating a calendar event and informs you about it in a message with appropriate link.</p><p>Steps:</p><ol><li>Open Google Calendar by tapping event link in AbsenceBot feedback message,</li><li>Tap on settings button in Google’s Calendar Event detail page</li><li>Tap on “Copy to {calendar}” to copy event to desired project calendar — you can copy to multiple calendars, if necessary</li></ol><p>By doing so you inform your team members about you absences, and everything is well organized. The main benefit of this is that you don’t have to deal with clumsy global absences view anymore in order to check your team absences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=215d65aa0a12" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appunite-edu-collection/how-announce-your-absences-to-the-team-and-ensure-transparency-and-readability-215d65aa0a12">How announce your absences to the team and ensure transparency and readability?</a> was originally published in <a href="https://medium.com/appunite-edu-collection">Appunite Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>