<?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 Pooja Chauhan on Medium]]></title>
        <description><![CDATA[Stories by Pooja Chauhan on Medium]]></description>
        <link>https://medium.com/@poojachauhan_16919?source=rss-6eadd1c3c02d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Um5yQnteQ9mTxAlE.</url>
            <title>Stories by Pooja Chauhan on Medium</title>
            <link>https://medium.com/@poojachauhan_16919?source=rss-6eadd1c3c02d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:34:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@poojachauhan_16919/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[HOW TO SCRUM-BAG A MILLION DOLLAR PROJECT]]></title>
            <link>https://medium.com/@poojachauhan_16919/how-to-scrum-bag-a-million-dollar-project-d4bafa62404d?source=rss-6eadd1c3c02d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4bafa62404d</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[sprint-planning]]></category>
            <category><![CDATA[startups-in-uk]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Pooja Chauhan]]></dc:creator>
            <pubDate>Fri, 03 Nov 2017 07:54:04 GMT</pubDate>
            <atom:updated>2017-11-03T07:55:18.861Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*yyYLsOyRsgQZY5lL.jpg" /><figcaption>@ <a href="https://www.vayuz.com/">VAYUZ Technologies</a></figcaption></figure><p>If you are in Software Development then you would have surely heard the terms “AGILE” and “SCRUM”. If you aren’t familiar with these terms then simply treat them on face value to decode their definition scope.</p><p>AGILE literally means nimble, light-footed, flexible etc. SCRUM literally means the formation of people.</p><p>Simply putting them together, SCRUM methodology is nothing more than a formation to keep you agile.</p><p>One of the biggest takeaways of life is to break up a problem into small pieces and then go about solving them. Scrum methodology does the same thing, breaking up product development into small goals (a.k.a. SPRINTS) and then running cycles to achieve those goals.</p><p>Every goal is a small functional module, which means you can run those lines of code.</p><p>So it’s all about Goal, Code, Iterate, Review ….an iterative cycle till you meet your SPRINT goals.</p><h4>Now how do you achieve the above?</h4><p>Meetings are of paramount importance to put the ball in motion and then ensure you put it in the right hole</p><p>SCRUM itself defines different types of meetings required to make your system AGILE in true sense. Today I will touch upon one such very important meeting, it’s called “Daily Scrum”.</p><ol><li>Duration: Typically 25–40 mins.</li><li>Each team member answers the following questions in our Daily Scrum Meeting:</li></ol><p><em>What did you do since the last Scrum Meeting (which would be yesterday)?</em></p><p><em>What are the speed breakers (if any)?</em></p><p><em>Tas</em>k list for the day (until next Scrum meeting).</p><p>3. What do you need:</p><ol><li>Meeting Room</li><li>Presence of all Stakeholders (developer, leads, BA etc.)</li><li>White Board, Marker &amp; Duster</li><li>Camera Phone</li><li>Project Dashboard: We use Trello to track all projects.</li><li>An anchor/reviewer to orchestrate the meeting in the right spirit.</li></ol><p>4. What do we achieve:</p><ol><li>Clear and crisp communication</li><li>Increased team cohesiveness since everyone is aware of each other’s task.</li><li>Transparency, no last-minute shocks</li><li>Increased accountability</li><li>Clear sense of where we are</li><li>Collaboration</li><li>Get processed and organized</li><li>Close big projects</li></ol><p>Start Scrumming your team, if you’re not doing it already, to close big-ticket projects and what better way to initiate than the easiest of them all. I’ll follow this blog with other types of Agile / Scrum Meeting practices we follow at <a href="https://www.vayuz.com/">VAYUZ</a>.</p><p>If you too are a Scrum-Bag or are interested in knowing more about it, do let us know in the comments below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4bafa62404d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The App Killer !]]></title>
            <link>https://medium.com/@poojachauhan_16919/the-app-killer-ebdfb69e54b9?source=rss-6eadd1c3c02d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebdfb69e54b9</guid>
            <category><![CDATA[vayuz]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[mobile-app-developers]]></category>
            <category><![CDATA[mobile-app-design]]></category>
            <dc:creator><![CDATA[Pooja Chauhan]]></dc:creator>
            <pubDate>Fri, 25 Aug 2017 11:58:35 GMT</pubDate>
            <atom:updated>2017-08-25T11:58:35.958Z</atom:updated>
            <content:encoded><![CDATA[<p>Chunibabu aaj kaha phaas gaye…well this is one joke, which everyone @ <a href="http://www.vayuz.com/">VAYUZ</a> can relate to.</p><p>English Translation (not exact) would be something like….Where do you have your neck stuck today?</p><p>The most obvious adage in the world of development. Most of you would agree, Is not it?</p><p>While developing an <a href="http://www.vayuz.com/">app</a>, you constantly face new challenges every other day. At times, if it’s too easy then you feel that something is wrong. So today let’s look at one of the bigger challenges in <a href="http://www.vayuz.com/">product development</a> — Identifying Exceptions.</p><p>Why Exceptions?</p><p>Well typically, the last few weeks of the development are lost just identifying and closing exceptions. We also call these exceptions — Bleeding Point. Presence of exceptions in your app / product can leave a huge dent on user experience. So even the best of product would fall flat on its face if these exceptions are not handled aptly.</p><p>As per our Center of Excellence Framework, we focus on identifying these exceptions during the documentation phase. But can you identify them all in the beginning?</p><p>Well no! That’s why it makes perfect sense to capture these exceptions during modular level UATs.</p><p>So today let me touch upon a very important element, absence of which can put your App into limbo.</p><p>What’s that?</p><p><a href="http://www.vayuz.com/">INTERNET</a> !!!</p><p>Have you ever been in a situation where you are showcasing your App to someone and you are frantically clicking on a button but nothing is happening. Next thing you get to hear is, “this **** ain’t working, looks like we have a dud of an App”. Suddenly all those lines of code seem to be waste of everyone’s time and you have just triggered a perfect storm.</p><p>So you go back, dig in and then you realize it was the dropping / intermittent internet, which had sponsored your last 60 mins of “you don’t know how to code” session. Well ! you can’t blame anyone cause at the end of the day “results are tangible”.</p><p>So let’s look at how can you manage or catch Internet dropping exception. Typically there are two ways of going about it.</p><p>Lets start with the the traditional approach, which is also the more popular one used in Android development.</p><p>The Traditional Approach</p><ol><li>Create a broadcast receiver</li></ol><blockquote><em>public class ConnectivityReceiver<br> extends BroadcastReceiver {</em></blockquote><blockquote><em>public static ConnectivityReceiverListener </em>connectivityReceiverListener<em>;</em></blockquote><blockquote><em>public ConnectivityReceiver() {<br> super();<br> }</em></blockquote><blockquote><em>@Override<br> public void onReceive(Context context, Intent arg1) {<br> ConnectivityManager cm = (ConnectivityManager) context<br> .getSystemService(Context.</em><strong>CONNECTIVITY_SERVICE</strong><em>);<br> NetworkInfo activeNetwork = cm.getActiveNetworkInfo();<br> boolean isConnected = activeNetwork != null<br> &amp;&amp; activeNetwork.isConnectedOrConnecting();</em></blockquote><blockquote><em>if (</em>connectivityReceiverListener <em>!= null) {<br> </em>connectivityReceiverListener<em>.onNetworkConnectionChanged(isConnected);<br> }<br> }</em></blockquote><blockquote><em>public static boolean isConnected() {<br> ConnectivityManager<br> cm = (ConnectivityManager) AppController.</em>getInstance<em>().getApplicationContext()<br> .getSystemService(Context.</em><strong>CONNECTIVITY_SERVICE</strong><em>);<br> NetworkInfo activeNetwork = cm.getActiveNetworkInfo();<br> return activeNetwork != null<br> &amp;&amp; activeNetwork.isConnectedOrConnecting();<br> }</em></blockquote><blockquote><em>public interface ConnectivityReceiverListener {<br> void onNetworkConnectionChanged(boolean isConnected);<br> }<br>}</em></blockquote><ol><li>Next up, register this in manifest</li></ol><blockquote><em>&lt;receiver<br> android:name=“.service.ConnectivityReceiver”<br> android:enabled=“true”&gt;<br> &lt;intent-filter&gt;<br> &lt;action android:name=“android.net.conn.CONNECTIVITY_CHANGE”/&gt;<br> &lt;/intent-filter&gt;<br>&lt;/receiver&gt;</em></blockquote><ol><li>Now, in each Activity you have to override a method and typically you will show a snackbar over there that says “No internet connection” like this:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/0*RFOZzKRL3l2-9LTy.png" /></figure><p>This solution works, but will cause an overhead in case of multiple activities.</p><p>The Smooth Criminal Approach</p><p>With this, the best part is you don’t have to write the code for internet connectivity in each activity, like we did above. Write once and you are good to go !</p><ol><li><strong>Broadcast Receiver code:</strong></li></ol><blockquote><em>public class NetworkReceiver extends BroadcastReceiver {<br> static Snackbar </em>snackbar<em>; </em>//make it as global<br> <em>@Override<br> public void onReceive(Context context, Intent intent) {<br> ConnectivityManager connectivityManager<br> = (ConnectivityManager) context.getSystemService(Context.</em><strong>CONNECTIVITY_SERVICE</strong><em>);<br> NetworkInfo activeNetworkInfo = connectivityManager.getActiveNetworkInfo();</em></blockquote><blockquote><em>if (activeNetworkInfo == null || !activeNetworkInfo.isConnected()) {<br></em>// Toast.makeText(context,”NO Internet connection”,Toast.LENGTH_LONG).show();<br> <em>NetworkReceiver.</em>snack<em>(null, 0, “No Internet Connection.”,context.getApplicationContext());<br> }else{<br> NetworkReceiver.</em>hideSnackbar<em>();<br> }<br> }</em></blockquote><blockquote><em>public static void snack (HashMap&lt;String,View.OnClickListener&gt; actions, int priority, String message, Context context) {<br> if(AppController.</em>appActivity <em>!= null){<br> </em>snackbar <em>= Snackbar.</em>make<em>(AppController.</em>appActivity<em>.findViewById(android.R.id.</em><strong>content</strong><em>), message, Snackbar.</em><strong>LENGTH_INDEFINITE</strong><em>);</em>//MyApplication.appactivity from Application class.<br> <em>if (actions != null) {<br> Iterator iterator = actions.entrySet().iterator();<br> </em>snackbar<em>.setDuration(Snackbar.</em><strong>LENGTH_INDEFINITE</strong><em>);<br> while (iterator.hasNext()) {<br> Map.Entry pair = (Map.Entry) iterator.next();<br> </em>snackbar<em>.setAction((String) pair.getKey(), (View.OnClickListener) pair.getValue());<br> iterator.remove(); </em>// avoids a ConcurrentModificationException<br> <em>}<br> }<br> switch (priority) {<br> case 0:<br> </em>snackbar<em>.getView().setBackgroundColor(context.getResources().getColor(R.color.</em><strong>black</strong><em>));<br> break;<br> case 1:<br> </em>snackbar<em>.getView().setBackgroundColor(Color.</em>parseColor<em>(“#66ccff”));<br> break;<br> case 2:<br> </em>snackbar<em>.getView().setBackgroundColor(Color.</em>parseColor<em>(“#66ff33”));<br> break;<br> }<br> </em>snackbar<em>.show();<br> }<br> }<br> private static void hideSnackbar(){<br> if(</em>snackbar <em>!=null &amp;&amp; </em>snackbar<em>.isShown()){<br> </em>snackbar<em>.dismiss();<br> }<br> }<br>}</em></blockquote><ol><li>Register this in Manifest:</li></ol><blockquote><em>&lt;receiver<br> android:name=“.helper.NetworkReceiver”&gt;<br> &lt;intent-filter&gt;<br> &lt;action android:name=“android.net.conn.CONNECTIVITY_CHANGE” /&gt;<br> &lt;/intent-filter&gt;<br>&lt;/receiver&gt;</em></blockquote><ol><li>Now create a Application class and implement that with Application.ActivityLifecycleCallbacks</li><li>In onActivityResumed() method, you’ll need to add</li></ol><blockquote><em>appActivity = activity; </em>//here we get the activity<br><em>Intent i = new Intent(this, NetworkReceiver.class);<br>sendBroadcast(i); </em>//here we are calling the broadcastreceiver to check connection state.</blockquote><p><strong>Conclusion</strong></p><p>So this is one of those things, which can save you from those App Killer moments. One chunk of code in one location and you are done. Try this out and let me know if this works for you and if it has saved you from those “How bad a coder” sessions then feel free to send me some goodies. Coding is fun but the fun becomes fantastic when you know those smart tweaks. Also remember to pick brains of people with prior experience of launching successful Mobile Apps. Their insights could help you in covering your base well. This is where <a href="http://www.vayuz.com/"><strong>VAYUZ</strong></a> can help you in your <a href="http://www.vayuz.com/"><strong>mobile application development</strong></a><strong> </strong>journey.</p><p>I would love to hear your thoughts on how you are handling app killer exceptions at your end, so leave a comment or drop me a note on pooja.chauhan@vayuz.com.</p><p><strong>Till we meet again, keep shining!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebdfb69e54b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FAST AND FURIOUS WEB APPLICATION DEVELOPMENT]]></title>
            <link>https://medium.com/@poojachauhan_16919/fast-and-furious-web-application-development-c3223fc8dd6c?source=rss-6eadd1c3c02d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3223fc8dd6c</guid>
            <category><![CDATA[php]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[mobile-apps]]></category>
            <category><![CDATA[vayuz]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Pooja Chauhan]]></dc:creator>
            <pubDate>Wed, 23 Aug 2017 11:53:23 GMT</pubDate>
            <atom:updated>2017-08-23T11:57:39.568Z</atom:updated>
            <content:encoded><![CDATA[<p>There are many PHP frameworks available in the market and Laravel is one of them. When we started our journey in <a href="http://www.vayuz.com/">VAYUZ</a> we started with Codeigniter and CakePHP, but with time we moved on to Laravel, a much younger MVC framework of PHP. The switch is not that difficult if you are proficient with CI, typically it would take couple of weeks to make this adjustment. The journey with Laravel started 2 years back and the bond has grown stronger over the years. To the extent, when it comes to development in PHP, Laravel is the obvious choice.</p><blockquote><em>Nothing against the good ole CI we still love working on it.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*8IoJ6qlUhtoJ2kd2zzhI3A.jpeg" /><figcaption>ww.vayuz.com</figcaption></figure><blockquote>The Power packed features<br>In the age of Fast and Furious, Laravel has everything that a developer needs to build a complicated platform in the most secure, scalable and fastest possible time. Laravel speeds up the development process, provides very secure authentication tools,and enables dynamic use all around. Laravel has its own lightweight templating engine called “Blade”, elegant syntax that facilitates tasks you frequently need to do, such as authentication, sessions, queueing, caching and RESTful routing. Laravel also includes a local development environment called Homestead that is a packaged Vagrant box. Routing, sessions are some tasks, which are commonly performed, and are made easier, thanks to Laravel.</blockquote><blockquote>Unit testing support and authentication, which are the base development components, are inbuilt. Use of libraries and models is easier as Laravel has object-oriented libraries. These libraries are supported with autocomplete feature. Laravel has its own command-line interface. Called as Artisan, it enables developers to perform abundant tasks. Tasks like migrating databases and seeding databases. Also performed is clearing the cache, etc.</blockquote><blockquote>Object-Relational Mapping or ORM in Laravel is simple, eloquent and fast. Due to this developers find it very easy to organize the application’s database.</blockquote><blockquote><em>Laravel is best suited for building RESTful APIs.</em></blockquote><blockquote><em>Laravel is the Most Starred PHP Framework on Github, more than 30000 developers from all over the world (mostly from the USA) greatly appreciate robust features of this platform.</em></blockquote><p>So is Laravel better than other frameworks?<br>Not all frameworks are able to solve each of the problems equally well. The best web frameworks such as Laravel help developers to do it and this means that Laravel-based development will make software delivery timely and cost-effective. Development of a web application is a mix of common and creative tasks. Good developers like to do all this common work (repeating from project to project) in as little time as possible (without loss of quality) before starting to write custom functions much sooner. Laravel just makes everything faster.</p><p>PHP is a language known to be very dynamic, but with Laravel, PHP has become even more powerful, faster, and much simpler. Ask developers, who have worked on Laravel, about how good Laravel is and they would vouch for it.</p><p>The History<br>Taylor Otwell created Laravel as an attempt to provide a more advanced alternative to the CodeIgniter framework, which did not provide certain features such as built-in support for user authentication and authorization. Although Laravel is a relatively new PHP framework (released in 2011), the recent trend and surveys suggest that it has become choice amongst developers. Laravel has a huge ecosystem with an instant hosting and deployment platform, and its official website offers many screencast tutorials called Laracasts. Laravel was first released under an MIT license on June 9, 2011, and since then it has had 14 version upgrades. The latest upgrade, Laravel 5.5, will be released in July 2017.</p><p>To Know more reach out to us @ <a href="http://www.vayuz.com/">VAYUZ</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3223fc8dd6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>