<?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[IDEA CORE - Medium]]></title>
        <description><![CDATA[We Help Brands and Businesses to Reach and Stay Connected to Customers. Learn more at https://idea-core.com/ - Medium]]></description>
        <link>https://medium.com/idea-core?source=rss----84cb06eeab95---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>IDEA CORE - Medium</title>
            <link>https://medium.com/idea-core?source=rss----84cb06eeab95---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:45:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/idea-core" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[JavaScript — What is non-blocking I/O]]></title>
            <link>https://medium.com/idea-core/javascript-what-is-non-blocking-i-o-a2acb5b7594c?source=rss----84cb06eeab95---4</link>
            <guid isPermaLink="false">https://medium.com/p/a2acb5b7594c</guid>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Janith Kasun]]></dc:creator>
            <pubDate>Wed, 31 Jul 2019 12:47:07 GMT</pubDate>
            <atom:updated>2019-10-29T09:18:37.041Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/778/0*cikATHezUYXjF0LR.jpg" /></figure><p>When someone is talking about JavaScript or NodeJS, event loop and non-blocking IO(input/output) are very popular topics, So here is a quick overview of what non-blocking IO really is. I am breaking down this article into a few topics. Please feel free to skip a topic that you may already know.</p><h3>JavaScript is single-threaded</h3><p>Well, first of all, JavaScript ‘sucks’? Well actually, Here is why?</p><blockquote>The <strong>History of JavaScript</strong> [INFOGRAPHIC] <strong>JavaScript</strong> was created by Brendan Eich, a Netscape Communications Corporation programmer, in September 1995. It took Eich only <strong>10 days to develop </strong>the scripting language which was then known as Mocha — Wikipedia</blockquote><p>“Okay, dude! This was supposed to be a non-blocking IO article. I don’t want to hear another hate speech about Javascript”</p><p>Yeah! I get it, but here is the interesting part, Javascript is only developed in 10 days by a single developer. So Javascript didn’t follow the standards of a well-written programming language. Javascript was just written focusing on doing simple programming tasks, maybe changing the color of a DOM element, make a simple calculation. <strong>Also,</strong> <strong>Javascript was not invented to write multi-threaded programming.</strong></p><p>Here is what Amazon looked like in 1995 when Javascript was invented,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aOSlnrp7yneouWJc.jpg" /><figcaption>Figure: Amazon.com in 1995</figcaption></figure><p>But as the rise of WWW and internet Javascript became a highly popular programming language in the world. Today we even develop frameworks and rendering animations using Javascript. So to be clear it does not suck anymore. 👊</p><h3>OS and the state of a process</h3><p>Here is an interesting video of how the process works on your OS, Feel free to skip this if you don’t feel like watching it. Otherwise, I promise it won’t be a waste of your bandwidth or time.</p><p>Anyway, here is the process status diagram,</p><p>When you start a new process (maybe word, excel or even a game), It will change its state according to the following diagram,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/557/0*52FFTQS-6K3qtPRW.png" /><figcaption>Figure: The process status Diagram, Source: superuser.com</figcaption></figure><p>As you can see, there is new, ready, running, waiting and terminated status. If you struggle with what those are, they are what they sound likes. 😛</p><p>But for now, let’s focus on what makes a process to change the state from the ‘running’ state to the ‘waiting’ state. There might be a few factors.</p><p>But in order to understand non-blocking IO, what you need to understand is a process might change it state from the ‘running’ state to the ‘waiting’ state, if it needs some kind of input or output to happen in order to continue the execution (maybe get an image from the HDD, receive an HTTP response from a server) which is called an I/O block. Even if the CPU is available for processing, many programming languages do not support to continue the execution until that I/O block is cleared.</p><p>So here comes the event loop, Javascript event loop made it possible to avoid these kinds of block and let other independent executions to happen, like render an animation while an HTTP response receives from the server.</p><p>Even if Javascript was not able to handle multi-threads in an OS, that gave it the power to manage one thread in the most optimized way like any other programming language couldn’t.</p><p>But today Java uses <strong>java.nio </strong>to address this issue they were having with IO blocking while NodeJS is using child process clustering and microservices to handle multi-treading.</p><h3>NodeJS and non-blocking IO</h3><p>NodeJs is fast. That’s the first thing everyone hears when they start learning the language. Non-blocking IO is one of the main reasons why NodeJS is fast. When traditional server-side languages handle 100 requests per second, NodeJS could handle 2000 requests.</p><p>There is no perfect language in the world. Every language is perfect in its own way. It will always depend on what you want to develop.</p><p>I love Javascript as much as I love Java, Python or PHP. This is my first article and hope you got something out of it.</p><p>Please mention your opinion or comments about this article, good, bad or mistakes. I would love to fix them.</p><p>Finally, Thank you very much for spending a few minutes to read this. ❤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2acb5b7594c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/idea-core/javascript-what-is-non-blocking-i-o-a2acb5b7594c">JavaScript — What is non-blocking I/O</a> was originally published in <a href="https://medium.com/idea-core">IDEA CORE</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Single Page Application Frameworks are not magic]]></title>
            <link>https://medium.com/idea-core/single-page-application-frameworks-are-not-magic-23e42bc33541?source=rss----84cb06eeab95---4</link>
            <guid isPermaLink="false">https://medium.com/p/23e42bc33541</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[ember]]></category>
            <category><![CDATA[single-page-applications]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Janith Kasun]]></dc:creator>
            <pubDate>Wed, 31 Jul 2019 12:46:57 GMT</pubDate>
            <atom:updated>2019-10-29T09:39:54.753Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*83KCVVK2EVOhilN67kXHQw.jpeg" /></figure><p>Greetings!!</p><p>Today, we are going to build our own awesome <strong>Single Page Application (SPA) framework</strong> (like angular, ember or react) from the scratch in 10 minutes. Feels complicated? Then you will be surprised.</p><p>So before continuing to the topic, I assume that you have fundamental knowledge about Modern Javascript (ES6), NodeJS, NPM and some basic knowledge about one SPA Framework.</p><p>Before started learning about SPA you might remember working with JQuery and Bootstrap. But none of these libraries need a node runtime to be installed. Just download and import! it worked.</p><p>So why SPA Frameworks needs a node runtime. Well! There are a few reasons which are watching files that you are editing to live reload your webpage, building the code, minifying the code, and provide a development server<strong> or simply a development environment.</strong></p><p>So let’s get started building our framework,</p><p>Here is the link to the GitHub repository of the finished code <a href="https://github.com/jkasun/sample-spa-framework">https://github.com/jkasun/sample-spa-framework</a>., you either code along with the article or simply clone this Github as you may prefer. But I strongly recommend you to code alone if you have enough time.</p><p>Create an empty folder and then initialize a node project by running</p><blockquote><strong>npm init</strong></blockquote><p>Then install express server using,</p><blockquote><strong>npm install -S express</strong></blockquote><p>Let’s get to the code and write our own development server.</p><blockquote><em>Sidebar: Why we need a development server?</em></blockquote><blockquote><em>Well! The Simple answer is, as definition a </em><strong><em>Single Page Application</em></strong><em> has only one web page. Remember? When you build your angular, ember or react application you get a single html file named </em><strong><em>index.html </em></strong><em>which is that single page, and bunch of javascript files. So no matter what web url path you go (maybe it could be something like </em><a href="http://www.my-spa.com/page1"><em>www.myspa.com/page1</em></a><em> or </em><a href="http://www.my-spa.com/page2"><em>www.myspa.com/page2</em></a><em>) the server will always send you the </em><strong><em>index.html</em></strong></blockquote><p>Create folders named <strong>server</strong>, <strong>app</strong>, a file named <strong>index.js</strong> inside the server folder, and a file named <strong>index.html</strong> inside the app folder. So your folder structure should look like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/381/1*vawMWmKEaQfba-kpCZaiLg.png" /></figure><p>Now let&#39;s write an express server app to serve that <strong>index.html</strong> no matter what request comes in.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6e03da4a74080acd21a00728ae0cfe70/href">https://medium.com/media/6e03da4a74080acd21a00728ae0cfe70/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f08fe3cd4b899d37ec7be95a0173bc92/href">https://medium.com/media/f08fe3cd4b899d37ec7be95a0173bc92/href</a></iframe><p>So I’m calling my framework Jangular Jumber Jeact.</p><p>So for now, let’s install the `nodemon` module globally to live reload our app if we edit any file.</p><blockquote><strong>npm install -g nodemon</strong></blockquote><p>Then let&#39;s boot up our server by running,</p><blockquote><strong>nodemon server</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*-GDur__cmh5p2bBX2nKl9Q.png" /></figure><p>So let’s open up our app on localhost:3000/blahblah, Note that no matter what path you enter the server will always send you the same page</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/434/1*a3FB2481C3ZsuU-K13cbZw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/443/1*D-ijbqZFXesj4opuWukCCQ.png" /></figure><p>Now, let&#39;s create a <strong>public </strong>folder inside the app folder and a javascript file called <strong>route.js</strong> which will do the routing and rendering. So your folder structure should look like this at this point</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/315/1*zWAm2h-5qqBel-tG0ru_Bw.png" /></figure><p>Previously, we configured our server to send <strong>index.html</strong> no matter what request comes in. But now, we have configure the public folder as a static server directory, in order to serve <strong>route.js</strong> and maybe other static assets files that you will need in the future(such as images, javascript libraries, etc).</p><p>So let’s configure that in <strong>server.js</strong><em>,</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/71a06e9ddc4d9cc55f9e7df9cc40b9ac/href">https://medium.com/media/71a06e9ddc4d9cc55f9e7df9cc40b9ac/href</a></iframe><p>Then include the <strong>route.js </strong>file in your app, by adding it to the <strong>index.html. </strong>Remove the app name. Add an HTML element called app-root to render the templates into (app-root could be anything, you name it! this is your framework).</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5378dc0217ce978f0eb8d8cc5a7bbd60/href">https://medium.com/media/5378dc0217ce978f0eb8d8cc5a7bbd60/href</a></iframe><p>Then let&#39;s implement the routing code,</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a3fa92f7718e17e3ee03627fed16c94b/href">https://medium.com/media/a3fa92f7718e17e3ee03627fed16c94b/href</a></iframe><p>So what happens in the above code is,</p><p>We are getting the current path of the web application, for an example if the address is localhost:3000/page1 the path is /page1, if the address is localhost:3000/page2/id_1 the path is /page2/id_1 , and split path by forwarding slash character so we would get an array of [&#39;&#39;, &#39;page2&#39;, &#39;id_1&#39;]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*KSq4O6GtxWzeGGIRBTChmg.png" /><figcaption>split the path localhost:3000/page1/id_1</figcaption></figure><p>Then the script is getting the relevant template from the templates object and append the template to the app-root element that we created before, Now open up your browser and go to localhost:3000/page1 and localhost:300/page2</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*Cp-fcMdp93ySb0_WJ4yfaw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/394/1*WTe5fIXQpO7zINf-_isWpA.png" /></figure><p>Hooray!!! Now our single page application framework is ready. You can implement your own template engine like handlebars.</p><p>You are free to think of any templating technique and implement and also routing, how to pass data and parameters and etc. It’s up to you.</p><p>However, this is the core that every SPA Framework shares, while other implementations make them unique from each other.</p><blockquote>Sidebar: Some developers has that misunderstand that SPA does’t contain any routes or paths like /page1 ,/page2 etc. By single page it doesn’t mean that you have only one uri to access. It means that routing will happen on the client side not the server side.</blockquote><p>SPA loads the whole application at on the first load rather than loading it partially to path to path, which makes a SPA faster compared to a Server Side Rendered application after the initial load. But the SPA could lead to increased initial load time due to its default behavior. One of the solutions for that problem is to combine it with some server-side rendering capabilities. Angular use something called Angular universal to do this, you can read my article “<a href="https://medium.com/@janithkasun/improve-performance-of-angular-using-angular-universal-5d82e2c24426?source=your_stories_page---------------------------">Improve Performance of Angular Using Angular Universal</a>” if you want to learn more.</p><p>So how that happens when we are routing through the paths,</p><p>The simple answer is no matter what path we request the server will only serve the <strong>index.html</strong> after the initial load every other javascript files which also contains the templates, are loaded and cached into the browser.</p><p>Thank you very much for spending your valuable time to read this article. ❤</p><p>This is a high-level implementation of a single page application, just to understand the concepts behind it. To move this to production you may have to do lots of implementations including code minifying, building, core development, two-way binding, advanced routing, etc.</p><p>So I am thankful for the hard-working development community of every SPA Framework for providing us that abstraction.</p><p>Thank you very much for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23e42bc33541" width="1" height="1" alt=""><hr><p><a href="https://medium.com/idea-core/single-page-application-frameworks-are-not-magic-23e42bc33541">Single Page Application Frameworks are not magic</a> was originally published in <a href="https://medium.com/idea-core">IDEA CORE</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is WebRTC? (Peer To Peer in Web)]]></title>
            <link>https://medium.com/idea-core/what-is-webrtc-peer-to-peer-in-web-4786b44db16b?source=rss----84cb06eeab95---4</link>
            <guid isPermaLink="false">https://medium.com/p/4786b44db16b</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[peer-to-peer]]></category>
            <category><![CDATA[webrtc]]></category>
            <category><![CDATA[web]]></category>
            <dc:creator><![CDATA[Janith Kasun]]></dc:creator>
            <pubDate>Wed, 31 Jul 2019 12:46:48 GMT</pubDate>
            <atom:updated>2019-10-29T09:44:36.091Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ih35kyvTcxvt1m87.jpg" /></figure><p>In this article, we will get to know what is WebRTC, how it works, and where to use it, the basics.</p><p>I have a 2 GB video file that I want to share with my friend. So what I would do is open Google drive (or Dropbox or any other cloud storage service), then upload my file to the drive. Then get a shared link from the drive and share it with my friend.</p><p>So behind the scene, what happens is your computer will create a TCP connection with a Google server, then upload your file. So your computer will upload 2GB of content, and Google drive will download 2GB of content. After that, when someone needs to download your file, he/she will create a TCP connection with a Google server and request the file. So the Google server will upload 2GB of content and the receiver will download 2GB of content. Simple right!!</p><p>This is the extract same, for a messenger call or a Skype video chat. The video/audio will stream to the server and then to your receiver.</p><p>This is called the <strong>server, client architecture.</strong> But there are few drawbacks,</p><ol><li>You need to use a centralized service, which may charge you for the service.</li><li>The round trip is long (your information needs to be uploaded from you to the server which could be in New York and then to your friend who could be sitting next to you in Antarctica), so the communication delay will be higher compared to a direct connection with your receiver.</li><li>There is a data wastage since the server acts like a proxy</li><li>Privacy issues, that you have to expose your file to a third-party service provider(the Google drive in this scenario)</li></ol><p><strong>But what if there is a way, that you can send your file directly to your friend. No third parties, no need to download any software but using the same exact web browser.</strong></p><p>I’m not saying that P2P is the most perfect solution for that situation as well, there could be drawbacks too. One of the disadvantages is that you need to be present online at the moment when the receiver downloading the file.</p><p>Personally, I love P2P technologies including torrent. Comparing to HTTP and Web Sockets, WebRTC is less popular among developers. When I first heard that there is a peer to peer communication protocol in my browser, I was amazed.</p><p>WebRTC, (The <strong>Web R</strong>eal-<strong>T</strong>ime <strong>C</strong>ommunication Protocol) is the web version of peer to peer communication. It is an opensource project which is developed at Google. Currently, there are thousands of passionate developers around the world who innovate new things using WebRTC and it is <strong>widely used for video conferencing and audio calls.</strong></p><h3>So Doesn’t WebRTC need any servers?</h3><p>Even though the WebRTC protocol is a peer to peer communication protocol, it needs a few types of servers like STUN and TURN to support the protocol.</p><p>When you need to connect any computer that is connected to the internet, you need to connect them via public IP and the given port, at least the domain name. This is okay with servers, you know their IP or domain name (ex.. facebook.com) already and their firewalls are configured with access. They have assigned a public IP and a domain name in order to make it easier for you to access them, just type google.com on your browser, you are connected.</p><p>But this is not the same with a computer that is connected to a public WiFi connection, shared internet connection or a home internet connection. In this case, the public IP of the gateway(router) is shared between all connected computers and you need to go and configure your router with NAT (Network address translation) which is a stressful task. Then you need to know your receiver&#39;s IP address and finally, you can connect.</p><p>But this is not possible, if we want to start a video chat with someone, right? Why would anyone want to do this, it is not the 90’s anymore.</p><p>Don’t worry!! with WebRTC, the receiver does not need to go through this configuration. Because these support servers are addressing that issue.</p><h3>STUN Server (The signaling server)</h3><p>The STUN (Session Traversal Utilities for NAT) is used to discover your public session information and whether or not your peer can connect you directly behind your firewall or router. Then your client is fed with your session information so the direct connection can be established.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/259/0*qu9iPhkGD7u7W2uM.png" /><figcaption>Diagram STUN</figcaption></figure><h3><strong>TURN Server</strong></h3><p>Major amount of the firewalls allow connection with computers behind the firewall, The success rate is about 80%. However what if your firewall does not allow direct connections.</p><p>TURN (Traversal Using Relays around NAT) servers are used as a fallback in this scenario. So it will act as a proxy server for data communication between peers. But in this case, as your content goes through the server you may not have some advantages that I mentioned before.</p><p>But this is an optional server, maybe in your scenario failure could be an option. Let’s assume that you are developing the torrent on the web (which actually exists). So failure is an option. Every peer in the network may not need to seed the file as there are other peers who have the same file. So failure is an option.</p><p>But think you are developing a video chat service, in that case, you must send your video stream to your client. So failure is not an option, which means you have to host a TURN server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/295/0*ltuUmlg3lRtPYjDC.png" /><figcaption>Diagram TURN</figcaption></figure><p>So that’s it for now. Let’s talk about how to implement this in code in my next article.</p><p>Thank you.</p><p>References:</p><p><a href="https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Protocols">https://developer.mozilla.org/en-S/docs/Web/API/WebRTC_API/Protocols</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4786b44db16b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/idea-core/what-is-webrtc-peer-to-peer-in-web-4786b44db16b">What is WebRTC? (Peer To Peer in Web)</a> was originally published in <a href="https://medium.com/idea-core">IDEA CORE</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The journey from Idea to Mobile App]]></title>
            <link>https://medium.com/idea-core/the-06-stages-of-a-mobile-app-from-idea-to-reality-14b2af6257d8?source=rss----84cb06eeab95---4</link>
            <guid isPermaLink="false">https://medium.com/p/14b2af6257d8</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Janith Kasun]]></dc:creator>
            <pubDate>Mon, 22 Jul 2019 12:11:39 GMT</pubDate>
            <atom:updated>2019-10-29T11:37:27.170Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*89k8-0wfGUKX5j0B" /></figure><p>No matter you have an idea to develop an app to make your business process easier or to make other people&#39;s lives easier, here is how you will get from your idea to the app published in the store.</p><p>This article is written for you, who might be publishing his/her first app to the app store, and wants to have a high-level idea about the process from start to finish.</p><h3>01. Write down your idea</h3><p>First of all, convert your idea to words. Describe your solution in one sentence. This sentence should include a high-level description of what is the problem that you are going to solve, or the end goal.</p><p>Then write a few sentences describing how you are going to solve that problem. Then write down high-level features of the app.</p><p>In this stage, you may have lots of things in your mind. Write down anything and everything that comes into mind.</p><p>Research and ask people who are having the same problem and will it solve their problem. Since you are going to make this solution for them, understanding your users and what they want is crucial.</p><p>Then filter out the most important features which are going to have the most impact on the solution, so you can test and improve the idea and make sure the problem really exists. This strategy will save both money and time and learn what are the changes to do in order to improve it further.</p><p>Now you have a good idea about what you are going to build. After that, you can move on to the next stage.</p><h3>02. The prototyping and designing state</h3><p>In this stage, you should plan the user experience and user interface. In short, user experience is how users interact with the app, it is all about the journey.</p><p>From where the app is installed from the app store, users should enjoy the journey and you should guide them throughout the journey.</p><blockquote><strong>You</strong>’<strong>ve got to start with the customer experience</strong>. and work backwards to the technology. — Steve Jobs</blockquote><p>No matter what your idea is if users don’t have a good experience using the app, they are not going to use it. Your app should be fast, easy to use, well designed and should solve the problem to make a pleasant experience for them.</p><p>User Interface design and user experience should also focus on the user who is going to use it. To stand out from your competitors a well-designed app is a must, it can change everything.</p><p>You can use a prototyping tool like <a href="https://www.figma.com/">Figma</a> to make this step much easier.</p><p>Now you have an idea about the user journey and you have well-designed interfaces. After that, you can start building your app.</p><h3>03. The development stage</h3><p>In this stage, you will start developing your application. After carefully investigating your ideas you can select a technology stack to develop your app.</p><p>You may also use an app creator if you have common features, but it is not flexible as coding your app and the maintenance cost might be higher.</p><p>When selecting between those things, you should consider the following.</p><ul><li>What are the features of your mobile app</li><li>Publication platform — Is it apple app store, play store or Microsoft store or everywhere</li><li>Performance of the application</li><li>Your budget</li></ul><p>and many more.</p><h3>04. Testing the app</h3><p>There is no app that has no issues, and this is okay. But at least your app should be usable without breaking every time it is opened otherwise the end-user will get frustrated using the app.</p><p>So it is very crucial to publish an app with the least number of issues that are possible.</p><p>You can test your app by playing with it or by automating the test process. Even if you use test automation there will be certain things that machines are not good at identifying.</p><p>Most of the app stores provide a testing environment in which you can provide access to few defined users or the limited number of users to install your app, so you can identify what are the issues of your apps before publishing the app.</p><h3>05. Publishing the app</h3><p>There are three major app stores that you can publish your app. Apple app store, Google play store and Microsoft Store.</p><p>Each of these stores has some slimier steps to publish your app.</p><h4>Purchase a License (Developer Account) to Publish the App.</h4><p>For publishing apps in the apple app store, you will have to buy a developer account which is 100 USD per year, for Android play store you will have to pay 25USD one-time fee while Microsoft is charging 49 USD — 99 USD annual fee. All of these stores will also take you a small percentage of your revenue.</p><h4>Upload your app</h4><p>After purchasing a license, you can upload your app to the store. Usually, you will have to do an app sign to verify your publication.</p><h4>Review Process</h4><p>After you have uploaded your app to the store, they will review your app. Each of their teams will verify if the app is following guidelines and the quality of the app is okay to publish.</p><p>After this review process, your app will be visible in the store.</p><p>So here is a high-level idea of how you can publish your idea as an app.</p><p>If you find this useful, It would be awesome if you can like and share it. Good luck with your next app.</p><p>Thank you very much for spending a few minutes of your valuable time to read this article. Have a very nice day!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14b2af6257d8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/idea-core/the-06-stages-of-a-mobile-app-from-idea-to-reality-14b2af6257d8">The journey from Idea to Mobile App</a> was originally published in <a href="https://medium.com/idea-core">IDEA CORE</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>