<?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 Petar Vukašinović on Medium]]></title>
        <description><![CDATA[Stories by Petar Vukašinović on Medium]]></description>
        <link>https://medium.com/@petarvukainovi?source=rss-2ace9dccee9a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*L0T_5q8r0kVYIBYp.</url>
            <title>Stories by Petar Vukašinović on Medium</title>
            <link>https://medium.com/@petarvukainovi?source=rss-2ace9dccee9a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:59:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@petarvukainovi/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[What you need to know about making an app startup]]></title>
            <link>https://medium.com/@petarvukainovi/what-you-need-to-know-about-making-an-app-startup-67bc5054c882?source=rss-2ace9dccee9a------2</link>
            <guid isPermaLink="false">https://medium.com/p/67bc5054c882</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mvp]]></category>
            <dc:creator><![CDATA[Petar Vukašinović]]></dc:creator>
            <pubDate>Thu, 06 Feb 2020 22:18:35 GMT</pubDate>
            <atom:updated>2020-02-14T09:51:31.244Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uogQZbJCXu0Jy9U0.jpg" /></figure><p>Do you have a mobile app idea and don’t know where to start? You already did some prototypes and figured out what you are doing is getting you nowhere, but you really think you have something special?</p><p>Don’t worry, you are not alone. After spending some time answering questions on Quora, the most frequent question out there was: “I have the next big app idea. I have created a product roadmap. What should I do?”</p><p>I am making this guide to help you and other entrepreneurs understand what it means to make a mobile app startup, what is the best way to approach mobile app development and ultimately, how to do it! This guide should get you started and set you on the right path.</p><p>Before we start, I would like to say that I spent the last 7 years of my life helping entrepreneurs build startup companies. My software skills and knowledge contributed to raising millions in funding, getting featured on the app stores, top publications and helped my clients win mobile app innovation awards.</p><p>We will be focusing on a step-by-step approach to building your mobile app startup. If you’ve already gone through some of these steps, feel free to skip them.</p><h3>Market Research</h3><p>Successful businesses have extensive knowledge of their customers and their competitors. Market research is the process of gathering information that will make you more aware of how the people you hope to sell to will react to your current or potential products and services.<br>This is a very crucial step when working on something new because you can determine if there are any markets that would benefit from your solution. Getting the market research right will save you resources and give you a better understanding of your future users. Doing market research should be your first step in creating your mobile app startup.<br>Let me walk you through the process of creating market research.</p><h3>#1. Brainstorm and Market segmentation</h3><p>In this step, write down all the markets that would benefit from your mobile app. For example, if your app is a goal-setting app, markets can be “startup founders, students, developers, athletes, people who go to the gym, etc..”</p><h3>#2. Define Jobs for each market</h3><p>Once you have some potential markets, write down all the jobs people in that market do. Note: Don’t try to match these jobs to your app functionality, you just want to find out what people do and how they are doing it.</p><h3>#3. Based on Jobs, narrow down the list to 3–6 markets</h3><p>Comparing the jobs and your app functionality, narrow down the list to a range of 3 to 6 top markets your app can serve. Also, make sure to ask these questions before narrowing your markets:</p><ul><li>Is the market consistent with your values and goals?</li><li>If you win the chosen market, can you easily go into another?</li><li>Is there any competition in that market that can block you?</li><li>Do your target users have a compelling reason to get your app?</li></ul><h3>#4. Primary research</h3><p>Once you have your markets, for each market on your list gather situations, pain points, opportunities, and market info. Go talk to customers, send surveys, etc.. Make sure you are out there, learning and focusing on your customers.</p><h3>#5. Organize your research and focus on 1 market</h3><p>Take the research you gathered and organize it based on the following questions:</p><ul><li>Who would use the product in that market?</li><li>What is the product used for?</li><li>What value are your users getting?</li><li>Who are influential users in the market?</li><li>What companies can you partner with?</li><li>What is the size of the market?</li><li>Is there any competition?</li></ul><p>Based on these answers, you can organize your research and focus on ONLY 1 market! I can’t stress enough how important it is for you to focus on one market at a time. I launched a Chrome extension a few weeks ago and focused only on baseball fans who use Chrome, search using Yahoo, check baseball stats every day and want to read the news in the morning.</p><p>Extension grew to 800 users in 17 days (growing 50 users per day), all organic. Just because I focused on a very niche market. Do this and dominate there, don’t compete! Then go on to the next market and dominate again!</p><p>Here are some questions that can help you focus on only one market:</p><ul><li>Do people in the market use similar apps?</li><li>What is the user acquisition process in the market?</li><li>Is there any word of mouth between users in the market?</li></ul><h3>#5. Build an end-user profile and make a persona</h3><p>Now is the perfect time to create an end-user profile. That perfect user who needs your app and is dying to get it. This is a great way to understand your users and the ways you can reach them. Make sure you have the following characteristics of your end-user:</p><ul><li>Gender</li><li>Age</li><li>Income Range</li><li>Geo Location</li><li>Motivations</li><li>Fears</li><li>Sites they visit</li><li>Restaurants they visit</li><li>Their story and specialty</li><li>Why should they care, and why they buy similar services to yours.</li></ul><p>By the end of this, you should have a nice overview of your perfect user. Print that out and keep it in your pocket. Keep it as a motivation. That persona is the reason why you are building this app and the same reason why I am writing this to you.</p><h3>#6. Create a value proposition</h3><p>This is the WHY of your startup and your app. What is the value you promise to create for the user? Make sure to create a value proposition and use your website, landing pages, emails, and other mediums to communicate that value to your users. Your value proposition should be to the point, unique and draw attention.<br>For example, I help startup founders create software solutions, and my value proposition is “We help startups bake fresh web and mobile apps”. The tagline is “Freshly baked web and mobile apps”. You see words: “Help startups”, “freshly baked”, “web and mobile”. This tells you right away this agency is working with entrepreneurs, helping them create fresh solutions, and you know those are web and mobile apps. Unique, concise and to the point. Do you agree?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/0*45r8C4qZr9-VYBpq.jpg" /></figure><h3>Idea Validation</h3><p>Now that you have a value proposition, your focused market and persona, use those ingredients to validate your idea. You have to make sure your mobile app is something people need, so let’s go through the idea validation process and try to get those early adopters based on your value proposition. To learn more techniques, here is an article I wrote: <a href="https://startupbakers.com/how-to-validate-your-app-idea/">How to validate your app idea?</a></p><h3>Join Facebook Groups</h3><p>Join Facebook Groups, politely introduce yourself to individuals and make sure to let them know that you found them in the group and then ask them to fill out your survey or answer your questions. I found out that people are very open on Facebook, and 8 out of 10 people reply back. That is great!</p><h3>Linkedin</h3><p>Linked is an amazing tool for validating your mobile app idea. I got around 70% response from the messages and so far it was very helpful. What you should do is introduce yourself as someone who needs help or doing research. Don’t try to sell to people and appreciate their time. You will be surprised at the results you get.</p><h3>Create a landing page</h3><p>Create a landing page, add a form to capture emails and see how it converts. You can spend some small amount of money on advertising and, after a week, see how many emails do you get. If you have 50 emails after a week, Amazing! Have less than 10, something is not right, maybe you messed up with your campaign or value proposition is not good enough. Change those and try again.</p><h3>Hiring</h3><p>If you don’t know how to develop mobile apps, you should read this part as it is important to know who to hire and how to do it. Before you actually go out and start looking for potential development partners, let’s start with your startup brief.</p><h3>Startup Brief</h3><p>Startup brief is a document that outlines what your startup is all about and what you are trying to accomplish. It would be good if your brief includes the background or context of your idea, who are your customers, a typical use case in detail, features, wireframes/prototype, and a monetization plan. This document should act as an insight into your startup and clearly show your potential development partner what you are trying to accomplish.</p><h3>Finding the right development partners</h3><p>Mobile app development takes time, effort and determination from you and your future development partner. If you are looking at native development and targeting Android and IOS platforms, it is most likely that you will need more than one developer.</p><p>You should look for a development company that has great design talent and a solid development team. When searching for a developer, go online to check their credibility and the apps they created.</p><p>There is a website called <a href="http://clutch.co/">clutch.co</a> where you can see verified agencies and their reviews made by actual customers. As an example, here is <a href="https://clutch.co/profile/agilno">our clutch profile</a>.</p><h3>Selecting the right partner</h3><p>Working with the right people is crucial to the success of your future business and you don’t want to work with people who will drag you down. Here are the things you should do when selecting the right developers:</p><h4>Get to know them</h4><p>The first thing you should do is spend some time with them. Have a meeting, go for lunch or anything that would let you learn more about those developers. You have to feel comfortable around them and have a really good vibe. You don’t want to end up with someone who you can’t stand. Make sure you like those people and those people like you.</p><h4>Check their references</h4><p>Checking references and past clients is a great way to see how developers performed for other clients and if they delivered what they promised. If the developers don’t want to give any references, you want to stay away.</p><h4>What is their specialty?</h4><p>Ask developers if they specialized in some specific technology or industry. There are many companies that specialize in certain areas, and if those areas are something you need it is a big plus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*TLjtIcSAQYh3ofYg.jpg" /></figure><h3>Mobile app development</h3><p>You have made proper preparation for your mobile app startup and at this point, you are ready to start developing your mobile apps. Before starting development, we need to make sure we pick the right tech stack that fits your budget, deadline and project brief.</p><h3>Pick a technology stack with your development partner</h3><p>There are a couple of technical decisions that have to be made early on in the development process and this one is very crucial. Your technology stack can greatly influence your budget and your time to market. Choosing between native or hybrid carries many implications for your later development and maintenance. This is why it’s key to leverage your market research and the core purpose and functionality you’ve just defined, so you can make the best decision.<br>Let’s go through the core differences between native and hybrid apps:</p><p>1. Native apps are built using native languages which is much more complicated than making hybrid apps using Javascript. This can affect your budget and desired time to market.</p><p>2. Access to the native device APIs. The hybrid approach relies on the concept of “plugins” and not all functionalities are available in the hybrid approach. Also developing custom plugins is hard and very time-consuming.</p><p>3. Cross-Platform support. Most often, you will want to be present both on Android and Apple stores. When going with native development, you will have to make 2 separate apps while the hybrid approach offers a “write once, run anywhere” concept.</p><p>To learn more about the differences between native and hybrid development, here is a good article about a client whom I helped create a multi-million dollar app. See how we developed a hybrid app, waited until we became big and then moved from hybrid to native Reasons hybrid apps fail in the long run.</p><h3>Create a beautiful design</h3><p>If you are serious about your apps, you want your design to be eye-catching and appealing to your users. People are attracted to something that looks good and having a good design is definitely an advantage. From my experience, the founders who focused on design had much better user acquisition rates. People would often talk about their apps and would always mention how beautiful they looked. Always make sure that your design files are made long before doing development and make sure that you don’t add stuff off the top of your head, which will save you some time on communication and different changes.</p><h3>Feedback and Iteration</h3><p>Your first version of the product is something that people might like, but not want, at least not to the full potential. Your users will always have something to say, especially when you are just starting out. The key is to listen to proposed changes and try to change the apps to accommodate those changes. Making apps in small iterations gives you the opportunity to get feedback faster and change the apps until you get something your users are crazy about.</p><h3>Product Development (MVP)</h3><p>When working from scratch, you should always start with MVP. MVP stands for minimum viable product and is the minimal amount of app features your users need to accomplish their goal. MVP development usually lasts from 2 weeks to 3 months and should be divided into sprints. Sprints are a part of Agile practices that are used when developing software. I would avoid using full Scrum in these early stages. Scrum is very heavy on processes, and at this point, your app will be changing a lot based on the feedback. Most important tools to have are:</p><ul><li>Project Management (Trello or Asana (Jira might be too much))</li><li>Communication (Slack, Gmail)</li><li>Code Versioning tools (Bitbucket)</li></ul><h3>Build your marketing strategy</h3><p>If you ever heard the saying: “If you build it, they will come”, please forget about it, at least when making software. These days people are bombarded with different apps, ads and everything else that can be found online.</p><p>Because of this, you have to stand out and create a killer marketing strategy. If there is an element that so heavily affects your app’s success, it’s the preparation to market and amplify it, including your branding, PR, pre-launch efforts, outreach, and simply overall web presence.</p><p>The sooner you start with your preparation and planning the better results you are going to get. You should start creating the buzz around your app long before it’s in the app stores. Let me walk you through the process of pre-launch preparation:</p><p>1. Set a tone with your branding. Make sure to create a mobile app startup name that resonates with what you do, your logo should do the same and your content should set you apart from the millions of other apps and businesses. Branding is all about consistency. Make sure your branding is consistent across your app and all platforms you exist on.</p><p>2. Find top channels that can deliver your message. Where does your target audience mostly hang out? How can you reach them? Do they use social media? How do they prefer to consume their content? How much time are they spending on their mobile device?</p><p>3. Separate yourself from others and create a trust bond with the content you create. You should know what content your audience craves and where to reach them. Start sharing your content to selected channels and track the engagements.</p><p>4. Reach out to influencers! Influencers are the next big thing in marketing and you should use influencers to put your app in front of their audience. Put some effort into reaching out to them in a personalized manner and make sure to provide a lot of value to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*IMnsT1fXTyevq74g.jpg" /></figure><h3>Important Do and Dont’s</h3><p>Congratulations! If you came this far in reading this, you are a pretty amazing person. The above process is more than enough to set you on a path to having a successful mobile app startup. Many entrepreneurs don’t do all of the above, but I can’t stress enough how important it is to do the above steps. After you launch your app it is all about iterating your product, changing it and adding features your users need. You will also continue tweaking your marketing strategy and keep looking at the best ways to reach your targeted audience. Before we finish with this guide, here are some important do and dont’s.</p><h3>Your users will not come on their own</h3><p>Please don’t think that if you created the app, your users will just jump on it and start using it. Those events are very rare and it is like winning a lottery jackpot. It takes a great amount of work, perseverance, and effort to gain momentum and have that organic traffic. My advice would be to focus on a niche market where people really need your app and start from there. Read more on this issue here: <a href="https://www.quora.com/Whats-the-most-interesting-thing-you-learned-after-founding-your-startup">Most interesting thing I learned after founding my startup 5 years ago</a>.</p><h3>Don’t quit your daily job</h3><p>New entrepreneurs often make this mistake and then run out of resources. You can have your day job and still have a successful mobile app startup. That is also the reason why you work with a development company. They should be your partners and cover the development work so you can focus on strategy and sales. Once your app starts making profits, you can then evaluate if it is worthwhile to quit your day job and focus 100% of your efforts on your startup.</p><h3>Don’t rely on your friends for opinions</h3><p>We always tend to ask people closest to us what they think about the stuff we do. Their opinions matter to us and that is great. The problem is that those opinions may not be relevant and in most cases, they are not. Your close friends and family will have distorted opinions about what you do and will always be affirmative. At the end of the day, they don’t want to hurt your feelings. Always make sure to get an opinion from strangers, and if you really want to know the truth, ask them to pay for your app.</p><h3>Don’t stay fixed on your app idea</h3><p>From the 7 years of my experience helping entrepreneurs, I can’t recall a single time when an entrepreneur had the right vision and idea from the beginning. Your idea will change as you get feedback and that is good. Always make sure you are open to feedback and willing to change based on what people want and not just how you see it.</p><h3>If you want to have an above-average startup, be an above-average person</h3><p>This is something I like to tell everyone. Your startup is YOU! The better and more knowledgeable person you are, the better your company and everything around you will be. Make sure to invest in yourself and strive to become a better person. Read this <a href="https://www.quora.com/What-made-your-startup-go-from-nothing-to-something">Going from nothing to something</a> to get a better idea about self-development.</p><p><em>Originally published at </em><a href="https://agilno.com/making-an-app-startup-here-is-what-you-need-to-know/"><em>https://agilno.com</em></a><em> on February 6, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67bc5054c882" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redux vs Vuex for state management in Vue.js]]></title>
            <link>https://medium.com/@petarvukainovi/redux-vs-vuex-for-state-management-in-vue-js-6e171a0f55ee?source=rss-2ace9dccee9a------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e171a0f55ee</guid>
            <category><![CDATA[redux]]></category>
            <category><![CDATA[single-page-applications]]></category>
            <category><![CDATA[vuex]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Petar Vukašinović]]></dc:creator>
            <pubDate>Wed, 03 Oct 2018 13:08:58 GMT</pubDate>
            <atom:updated>2018-10-03T21:28:38.920Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*0PVd7TZOIskse7fSj3rr_Q.png" /></figure><p>Hi! This is my first post on Codementor and I hope you will like it. I just finished the middle sized project in Vue.js, and since I was building a complex app I needed a solution to manage the app state. I spent some time playing with both Redux and Vuex. In this post, I am going to show you the main differences between those two libraries and which one I picked for my solution. Ready? Let’s go!</p><h3>What is state management?</h3><p>State management is a way of managing the state inside your application, making sure that your UI is always reflecting your app changes. There are multiple ways to manage the state in your app, and in many cases, you don’t need libraries like Redux or Vuex, but if your app starts to become wild and complicated, state management solution can help you evaluate those problems.</p><p>In the past, it was not uncommon to have pieces of state across our application tucked inside of controllers, services, routes, directives (AngularJS), local storage, session storage, cookies, and some other alternatives.</p><p>When the application grows, this approach is really hard to scale and this is where Flux and React stepped in.</p><p>React changed the way we approach state-management. Redux (based on Flux) is front and center of this shift as it introduced an elegant, yet profoundly simple way to manage application state. Vuex followed Redux and found the place amount Vue developers.</p><h3>What is Redux?</h3><p>Redux is a framework agnostic state management library. Something that I noticed during development with React is that Redux is created with React in mind. If you’re thinking about using Vue with Redux, Vuex is probably a better state management library for maintaining performance. Here are some things to know about the two:</p><h3>Actions</h3><p>Let’s start with the easiest part of Redux. Actions! Actions are very simple objects with a “type” property and the minimum number of other properties and values that are necessary to explain the action we intend to make in the state.</p><p>Actions are the only way to change the state and changing state is done by “dispatching” an action using store. Here is an example:</p><pre>import { createStore } from &#39;redux&#39; <br>import { ActionTypes as types } from &#39;../constants&#39; </pre><pre>var defaultState = { name: &#39;&#39; }; </pre><pre>function reducer(state = defaultState, action) { <br>    switch(action.type) { <br>        case types.CHANGE_NAME: <br>            return { ...state, name: action.data.name } <br>        default: <br>            return state <br>     } <br>} </pre><pre>// Let&#39;s create the store, and add root reducer to it var store = createStore(reducer) </pre><pre>// This is where we dispatch action to the store store.dispatch({type: types.CHANGE_NAME, data: {name: &quot;Petar&quot;}})</pre><p>You can see that .dispatch() takes “action” object and sends this to the reducer.<br> If the action isn’t recognized and no change is dispatched, the state defaults to the old state.</p><h3>Reducers</h3><p>This is where the fun stuff happens and where we change the state in the store based on the action “type”. Reducers are pure functions that are used to implement how the next state is calculated from the current state and the action.</p><p>Since Redux has only one store, we use multiple reducers to manage parts of the global state (store). This concept allows you to have multiple parts inside your store, all managed by different reducers.</p><p>These reducers can then be combined into one root reducer to manage all of your application states. The redux store saves the complete state tree returned by the root reducer.</p><h3>Store</h3><p>This is a place where you store the state of your application. The store is nothing more than an object containing different properties and values. There is only one store in Redux (root store) and one root reducer. The point with the root store is that you can have multiple reducers that work on different parts of your store.</p><p>To change the state, you have to dispatch an action to it. Once you dispatched an action you can add a change listener called “subscribe”. By subscribing to the store you can check if an action is ‘dispatched’ and is your state tree changed.</p><p>While this is working, this might not be the best solution for your Vue.js project. The biggest reason why is because Redux replaces the state object on every update.</p><p>React is different from Vue in the way it processes updates: React renders a virtual DOM then calculates optimal DOM operations to make the currently rendered DOM match the new Virtual Dom. But it has no way of knowing whether a particular component needs to re-render or not based on the new data. Vue instances keep track of which bits of data they depend on to render. These instances automatically register what needs to re-render when the data changes.</p><h3>Vuex</h3><p>Vuex is very similar to Redux and also inspired by Flux. Unlike Redux, Vuex mutates the state rather than making the state immutable. This approach removes the need for having a reducer, so in Vuex reducers are replaced with something called Mutations.</p><p>This allows Vue.js to automatically know which components need to be re-rendered when the state changes. Instead of breaking down state logic with specialized reducers, Vuex is able to organize its state logic with stores called modules.</p><h3>Mutations</h3><p>The only way to change state in a Vuex store is by committing a mutation. Mutations are very similar to the events and each mutation has a string type and a handler. The handler function is where we perform actual state modifications, and it will receive the state as the first argument:</p><pre>const store = new Vuex.Store({ <br>    state: { count: 1 }, <br>    mutations: { <br>        increment (state) { <br>            // mutate state <br>            state.count++<br>        }<br>     } <br>})</pre><p>You cannot directly call a mutation handler. Think of it like: “When a mutation with type increment is triggered, call this handler”. To invoke a mutation handler, you need to call store.commit with its type:</p><pre>store.commit(&#39;increment&#39;)</pre><p>One thing to remember is that mutations are always synchronous to ensure that the state isn’t dependent on the timing and order of unpredictable events.</p><h3>Actions</h3><p>Actions are similar to mutations and work like Redux actions. Actions can’t mutate the state, rather action commit mutations. One other benefit of working with Vuex actions is that actions can contain arbitrary asynchronous operations.<br> This is great when you need to call your API and is much more organized comparing to Redux.</p><pre>const store = new Vuex.Store({ <br>    state: { count: 0 }, <br>    mutations: { <br>        increment (state) { <br>            state.count++ <br>        } <br>    }, <br>    actions: { <br>        increment (context) { <br>            context.commit(&#39;increment&#39;) <br>        } <br>    } <br>})</pre><p>To Dispatch an action we use:</p><pre>store.dispatch(&#39;increment&#39;)</pre><h3>Store</h3><p>Vuex uses a single state tree — that is, this single object contains all your application level state and serves as the “single source of truth”. This is very similar to Redux and the Store is the center of every Vuex application.</p><p>Since Vue instances keep track of which bits of data they depend on to render, vuex is taking advantage of that and when components get the state from the store, these components can reactively and efficiently update whenever the store’s state changes. One thing to remember is that the store’s state can only be changed by committing mutations.</p><h3>The finals</h3><p>While Redux and Vuex are amazing state management libraries and patterns, I prefer Vuex over Redux when working with Vue. Here are the main reasons:</p><ol><li>Mutations are easier to work with then Reducers</li><li>Asynchronous actions are much more organized in Vuex. There is no need to write _ON_LOAD, _SUCCESS or _FAIL middle term state actions.</li><li>Out of the box dev tools</li><li>Much easier setup. It is easy as Vue.use(Vuex)</li><li>Vuex takes advantage of Vue.js uniqueness</li></ol><p><em>Originally published at </em><a href="https://www.codementor.io/petarvukasinovic/redux-vs-vuex-for-state-management-in-vue-js-n10yd7g2f"><em>www.codementor.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e171a0f55ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 reasons why your hybrid mobile app will fail]]></title>
            <link>https://medium.com/@petarvukainovi/5-reasons-why-your-hybrid-mobile-app-will-fail-39037ea7b0e7?source=rss-2ace9dccee9a------2</link>
            <guid isPermaLink="false">https://medium.com/p/39037ea7b0e7</guid>
            <category><![CDATA[ionic]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[hybrid-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[cordova]]></category>
            <dc:creator><![CDATA[Petar Vukašinović]]></dc:creator>
            <pubDate>Wed, 03 Oct 2018 09:11:43 GMT</pubDate>
            <atom:updated>2018-10-03T09:11:43.704Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xoftyz9s6UZlROuYqEF1eQ.jpeg" /></figure><p>When you google “Hybrid app development” you will find such a wonderful value proposition. Build once run anywhere, single codebase, cheap development, less time to market, less resource intensity and so on. The first thing clients do when they see that, is they look at that value proposition and think: “What a wonderful thing. I can have an app on both platforms, time to market will be quick, talent easy to find and best of all, it will be cheap!”. This can actually work for a small hybrid app with a few screens, but if you are serious about your business, if you want to have an app that brings revenue and provide great value to your customers, you don’t want to settle with mediocre, you want only the best for your customers.</p><p>Here are 5 reasons your hybrid app will fail and those are based on my personal experience helping my client build a $20 million company.</p><h3>Reason #1: Hidden costs of hybrid development</h3><blockquote>People say: “Hybrid development is cheaper. It is write once, run anywhere.”</blockquote><p>Well, this is very true. At the beginning at least. There are many programmers who do HTML, CSS and Javascript. Wrap that inside the WebView and you’ve got yourself an app. You hire a developer, explain the project to him and right at that moment, your hybrid development journey begins. In the first few weeks, everything is going great. Progress is fast, investors are happy, feedback is great and you start thinking this will be done in no time. Wonderful!</p><p>So what is the problem? The problem is finishing the product. Making sure it is bug-free and ready to be used by real people. You might say this is a problem with building software in general, but when it comes to hybrid app development it becomes impossible to polish it. You depend a lot on the open source libraries, transitions and animations suck and it is very hard to do any customization to the native components.</p><p>If you decide to do any customization of native components, you have to write them for all platforms you are supporting, which leads to more code in a single place, resulting in more issues and making development extremely hard.</p><h3>Reason #2: Poorly maintained libraries</h3><p>When creating a hybrid mobile app, you have to have some sort of bridge between native and web view. I was using Cordova as the framework for building apps. Cordova exposes API to your Javascript and handles all of the native work for you. This is amazing for small apps and prototypes cause it allows you to build and release often, but when it comes to building long-lasting apps for your users, this absolutely sucks.</p><p>You might wonder what happens when there is no API exposed to your Javascript for the feature you need. Well, you have to find a third party plugin written by someone else, or you have to write it yourself! Writing plugins for Cordova is not something developers want to do, and it takes some skill since the developer needs to know languages involved in both native platforms.</p><p>Android and iOS are updated very often, and with new releases, the old ones are changed or become obsolete. The problem is that the plugins you installed are not updated right away, so if something is not compatible you have to wait for days, sometimes weeks to get the update. In the worst case scenario, there will be no update and then you need to find another library.</p><h3>Reason #3: User experience</h3><p>Failing to meet user needs and expectations will give you headaches and lot’s of support calls, resulting in spending a decent amount of money on support tools and processes. Having an amazing user experience plays a key role in getting amazing reviews and keeping your users happy.</p><p>A hybrid solution requires native code to load your app from within WebView. Apple said that on average, apps should load in less than 400ms, and having Cordova, Angular and other libraries inside your project, it can take up to 3 seconds or more to load your app.</p><p>Once you are in the app, the first thing you will notice is that apps don’t have the native look users are used to. Hybrid app frameworks are promising to change the look and feel based on the OS user has, but the experience is definitely not as good as it should be. Existing UI components provided by the framework are hard to edit and you can just forget about advanced animations and transitions.</p><h3>Reason #4: Poor performance</h3><p>Performance plays a key role in leaving a good impression and returning user. With technology progressing, users are getting used to fast and performing applications and that is something users expect these days. You want to make sure your app loads fast, screens have the smooth transitions and there is no waiting or flickering inside your app.</p><p>In a hybrid application, components and logic do not directly interact with the device operating system. Those are loaded through WebView component which then communicates with the other components.</p><p>The downside to this approach is that there are many platforms and platform versions circulating, all of which behave differently when it comes to the WebView component.</p><p>Adding extra complexity to any application is going to have negative side effects in terms of consistency on platforms you are targeting.</p><p>One thing I noticed is that some plugins have memory leaks and your app can force stop just because the plugin you installed didn’t free used memory. One other thing is that not all plugins are compatible, adding additional problems and performance issues.</p><h3>Reason #5: You will fall behind</h3><p>When Google and Apple release new OS versions, they give native developers early access to the SDKs (software development kits) to start testing newly added features. Developers test and integrate new features into their apps making sure they have an update for their app the day their users update to the new OS version.</p><p>Developers of Hybrid apps need to wait for third-party developers to create plugins that bridge the new operating system features to apps. An alternative is to create your own plugin and that will take some additional time and resources. This gives native app developers a few months head start with the new features. Worst case is that hybrid apps may never support your desired features. Trust me, you don’t want to be stuck with hybrid apps while your competitors enjoy the benefits of native development.</p><p>The hybrid approach tricks owners and investors into a false sense of progress until it’s too late to switch to native and they must ship an inferior product.</p><h3>Key takeaways</h3><p>Native development is much superior to hybrid development. If you are at all serious about your business, you will go with native apps and create a truly great product and experience. If you have a good business that has a steady growth, you will realize that your hybrid app will fail to satisfy your users and that you need to switch to native. However, there definitely is a place for hybrid apps.</p><p>Hybrid apps are good for prototyping, testing your ideas and making MVPs. With hybrid development, you can get a functional, cross-platform app within a week or two and test the concept with your users, get the feedback and learn from it. The key when testing your ideas is to develop a feature, ship it to the users and get feedback as fast as possible. Iterate this until your users are happy to use your app. Evaluating your idea, seeing if it is valuable and if your app will get you a good ROI is where the hybrid approach shines.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39037ea7b0e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>