<?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 Nicholas Lewanowicz on Medium]]></title>
        <description><![CDATA[Stories by Nicholas Lewanowicz on Medium]]></description>
        <link>https://medium.com/@nicklewanowicz?source=rss-3b893ccd1787------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5v5fYhorOu1R9YXvjHk2Dg.jpeg</url>
            <title>Stories by Nicholas Lewanowicz on Medium</title>
            <link>https://medium.com/@nicklewanowicz?source=rss-3b893ccd1787------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:07:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nicklewanowicz/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[Lazy guide to saving smart in Canada]]></title>
            <link>https://medium.com/@nicklewanowicz/lazy-guide-to-saving-smart-in-canada-2f9f5caf153e?source=rss-3b893ccd1787------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f9f5caf153e</guid>
            <category><![CDATA[saving]]></category>
            <category><![CDATA[money]]></category>
            <category><![CDATA[canada]]></category>
            <dc:creator><![CDATA[Nicholas Lewanowicz]]></dc:creator>
            <pubDate>Wed, 08 May 2019 01:06:13 GMT</pubDate>
            <atom:updated>2019-05-09T13:56:09.059Z</atom:updated>
            <content:encoded><![CDATA[<h3>I HATE saving.</h3><p>As a lazy person I hate having to do things more than once. Having to think about my finances, savings strategy, and retirement goals at 23 year old is generally not fun and if you&#39;re anything like me you probably feel hopelessly lost when figuring out what to do with your extra loonies and toonies. To solve this I built a dead easy strategy so I don’t need to keep worrying about it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mxpsgqWGbsI6hENtQRpIVw.jpeg" /></figure><p><strong><em>Disclaimer</em></strong><em>: While this strategy works for me and I don’t see any reason it couldn’t work for the vast majority of people it’s definitely not for everyone and can always be improved. If you have suggestions feel free to tell me </em><a href="https://www.twitter.com/imnickdev"><em>@ImNickDev</em></a><em>!</em></p><h3>Step 0: Be Cash Flow Positive</h3><p>As a person who put themselves through university while living on my own I will be the first to say this is definitely easier said than done but you gotta be making money before you can save it. The only advice I have is often times your spending is much easier to control than your income, so to get into a positive cashflow take a hard look at your spending habits, break out the scissors, and start cutting. I have been lucky to have some amazing influences in my life. My mom as a single parent was able to raise 6 children on less than $30k/year and all I can say is where there is a will there is generally a way.</p><h3>Step 1: Get the right vehicle for the job 🏎</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fTzg30c4SXAhCM_6eu_-qQ.jpeg" /></figure><p>You wouldn’t use a ferrari to move your couch, so why use a checkings account to save for retirement. This is a obvious for some but not all; my optimal lazy saving strategy requires 3 accounts:</p><ol><li><strong>💵Parking Account</strong>: Something with a high interest rate that is hard to get money out. I suggest <a href="https://www.eqbank.ca/">EQBank</a> as it provides a 2.3% interest rate (double what most chequing accounts offer) and there is no debit card meaning it’s easier to save and harder to spend out of impulse. <br><em>Edit: Worth noting EQBank offers unlimited EFTs and 5 free e-transfers a month so you can access your money quickly if needed.</em></li><li><strong>💸Spending Account</strong>: Something with NO fees and cash back credit card. I suggest Tangerine as fit both these criteria and offer a pretty great user experience all around. <br><em>Edit: Use my code ‘</em><strong><em>45973813S1’ </em></strong><em>and we both get $50 free for your first deposit, it’s appreciated if you do👍</em></li><li><strong>💰Saving Account</strong>: Hold registered accounts (TFSA and RRSP) and have minimal MER’s and fees. I suggest Wealthsimples robo-advisor because its dead easy to use, has none of the hidden fees or inflated MER’s most big banks have, and they continue to push forward modern online banking. <br><em>Edit: </em><a href="https://wealthsimple.com/invite/PYNGJG"><em>Use my referral link for wealthsimple and we both get 10k in fee-less investments</em></a><em>, it’s appreciated if you do👍</em></li></ol><h3>Step 2: Put them all together 📎</h3><p>Now you might be thinking “Nick this was hard enough before when I have one account, how is this is going to be easier with 3 accounts?!”, it’s a valid concern but trust me optimal laziness is coming! Just follow this diagram:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wvf_9YkiMTB-lMvINgrvhg.png" /></figure><p>Once you get get your direct deposits going to your parking account all you need to do is setup 2 automatic recurring transactions; the first one to your spending account with all your monthly expenses (rent, utilities, misc, etc) and the second with whatever amount your comfortable sending to your savings account.</p><h3>Step 3 (optional): Rules of thumb 👍</h3><p>By this point your pretty rock solid. You no longer are paying any dumb fees to banks, you are setting up barriers to protect you from impulse spending, and your have the almighty power of compound interest on your side! In only a day or two you have netted thousands to tens of thousands down the road so you should give yourself a hand 👏👏👏. Now if you feel like you want to put a little more time in here are some rules I like to follow:</p><ul><li><strong>Emergency Fund</strong>: Never have more than 6 months total for expenses in cash (Parking Account). If you have contribution room in your TFSA or RRSP seriously consider making a contribution. <em>Exceptions include </em><strong><em>immediate</em></strong><em> plans to buy a house or other large investment (not “I think I might buy a house maybe sometime soon ish”</em> 😤<em>).</em></li><li><strong>RRSP or TFSA?</strong>: If you think your income will be more next year than this year prioritize TFSA over RRSP and vise versa. Wealthsimple will tell you what your contribution limits are for these accounts.</li><li><strong>Monthly or annual contributions?</strong>: Once January rolls around if your financial situation supports it you should put as much of your TFSA contribution amount as you can. If you are limited to monthly contributions there is no reason to be concerned.</li><li><strong>Free Banking or Student Banking?</strong>: Do your future self a favour and switch to a free banking option NOW. When you graduate you’re probably gonna forget to cancel it and worse your gonna be worried about graduation, jobs, loans, etc. Unless you have pretty specific needs most free banking options offer similar experiences to the student accounts.</li><li><strong>Points program or cashback?</strong>: Cash is king; period. It’s possible you have a points program that compliments your life style but for most people a normal cashback card will net you $12 in about the same time you get the points to buy a movie ticket.</li><li><strong>“My mom/dad/uncle/guy in a medium article told me to…”</strong>: If anybody tries to tell you need to do exactly what they’re doing financially it’s always good to question it and be objective when you research (especially when it’s ‘guy in a medium article’).</li></ul><h3>Caveats and Extras 🚫</h3><ul><li>Most of this is just simplified info from the kind folks on <a href="https://www.reddit.com/r/PersonalFinanceCanada">/r/PersonalFinanceCanada</a> and <a href="https://www.reddit.com/r/fican/">/r/fican</a></li><li>There are absolutely alternatives to my banking suggestions (and maybe some better ones you can find) I purposely provided only one example cause if I did more than one you would need to do research and that’s not lazy</li><li>This article doesn’t mention much about carrying debt which is becoming surprisingly more common for young people. If you are carrying debt and you want to do what’s best for you I encourage you to post on <a href="https://www.reddit.com/r/PersonalFinanceCanada">/r/PersonalFinanceCanada</a> and see what the great people there might suggest for your situation.</li><li>I’m just as qualified as your local Subway sandwich artist or TD financial advisor to give you this advice so take it with a BIG grain of salt.</li></ul><p>If you enjoyed this article claps are appreciated 🙇‍♂️, if you have comments I usually respond on <a href="https://www.twitter.com/imnickdev">twitter</a>, and best of luck with your lazy savings! 😴</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f9f5caf153e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a Service Worker?]]></title>
            <link>https://medium.com/@nicklewanowicz/what-is-a-service-worker-c33dc4c86c31?source=rss-3b893ccd1787------2</link>
            <guid isPermaLink="false">https://medium.com/p/c33dc4c86c31</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[service-worker]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Nicholas Lewanowicz]]></dc:creator>
            <pubDate>Fri, 16 Nov 2018 14:02:41 GMT</pubDate>
            <atom:updated>2019-07-31T17:08:19.714Z</atom:updated>
            <content:encoded><![CDATA[<p>If you read <a href="https://medium.com/@nicklewanowicz/pwa-the-future-of-mobile-and-web-development-d3138cf91e0a">my first article talking about PWAs</a>, you know I mentioned that a core pillar of PWAs is the ServiceWorker (SW)— but I didn’t quite explain what that was.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*xkqKYdHsLjkuEuFlYGkMCA.png" /><figcaption>The service worker serves as a intermediary between your web app and the internet</figcaption></figure><blockquote>A service worker is a script that your browser runs in the background, separate from a web page, opening the door to features that don’t need a web page or user interaction. — <a href="https://developers.google.com/web/fundamentals/primers/service-workers/">Google</a></blockquote><p>Sounds cool right? Well it is! If you’re making a web app at <strong><em>MyApp.com</em></strong> the service worker will act as an event driven proxy which is given control over the network requests to or from <strong><em>MyApp.com</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*RMb-1E5WKf5l0ooWOLZCiA.png" /></figure><p>The interface for defining behaviour is quite simple. You can write logic for your SW on any of the following events:</p><ul><li><strong><em>Install</em></strong><em>: </em>This is generally the first thing you do when your app loads. You will want to begin caching any files that are required for the page to work incase the network connection is lost. This way, you can switch to offline-mode or fail gracefully.</li><li><strong><em>Activate</em></strong><em>: </em>You will likely need to iterate on your service worker and add functionality. The ‘<em>activate</em>’ hook is the first thing to run when a new version of your service worker is installed and is generally used to invalidate cache (this is action is known as cache-busting) or get your application in a happy state.</li><li><strong><em>Message</em></strong><em>: </em>Given that SWs are so powerful, you’ll likely want to trigger them for actions unrelated to network events or get data from them that isn’t stored in the remote database. The <em>message</em> hook allows you to communicate between your web app and your SW. <a href="http://craig-russell.co.uk/2016/01/29/service-worker-messaging.html#.W-yyAZNKiL4">You can see a use case here</a>.</li><li><strong><em>Fetch</em></strong><em>: </em>If you want to create a native experience for your users, this is where that work will happen. On any client request you will be able to trigger a hit the network and even fallback to cache if it fails, you could immediately respond with the cache while the network pends, or even query the cache and network at the same time and serve whichever comes back first. Whatever is done here is highly dependent on the type of data you’re requesting. <a href="https://developers.google.com/web/fundamentals/instant-and-offline/offline-cookbook/">You can read more here</a>.</li><li><strong><em>Sync</em></strong><em>: </em>This event allows the developer to queue up future events to fire based off criteria like time of day or losing/gaining network connection. If this event fails it will queue another until it succeeds. (Read caveats**)</li><li><strong><em>Push</em></strong><em>: </em>This trigger is fired by your remote server and allows you to perform actions even when your web app has been closed. The single most valuable feature of the native app experience is probably push notifications and this gives web apps that luxury.</li></ul><p>This primitive API is easily extensible into powerful libraries like <a href="https://developers.google.com/web/tools/workbox/">WorkBox</a> (stay tuned for tutorial) to abstract the developer from complex caching validation strategies and enable reliable app functionality even in poor network conditions.</p><h3><a href="http://forecaast.us/">Forecaast: Another Progressive Weather App</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7o4tXYYblhzoFXdoWrZC5g.gif" /><figcaption>Service worker is installed</figcaption></figure><p>I <a href="https://github.com/nicklewanowicz/forecaast">made a demo app Forecaast</a>; as you can see by the console log above I’m using the ‘install’ event to cache all the files needed to to run the app offline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jcs1OMy5FVY4gEmcfMkb1Q.gif" /><figcaption>Forecaast runs offline</figcaption></figure><p>As can be seen above, when chrome is switched offline, the application will still load like normal as the service worker responds with the cached assets.</p><h3>Caveats</h3><p>With great power comes great restrictions! While I highly suggest using service workers and building cool apps there are some prerequisites for them.</p><ul><li>In order to install a service worker you must be serving it over HTTPS (I hope this isn’t an issue for your app, USE HTTPS!)</li><li>You can only have one active SW for your origin</li><li>A service worker can only be triggered by events on its origin. For example I use an open source weather api in Forecaast meaning I cannot use the ‘Fetch’ trigger to cache weather data</li><li>Don’t get too excited about background sync, check out <a href="https://jakearchibald.github.io/isserviceworkerready/">isServiceWorkerReady</a> for the most up to date information but currently chrome is the only browser supporting this feature</li></ul><h3>Thank you for making it here!</h3><p>If you enjoyed this post, please leave some claps. 👏👏👏</p><p><strong>You can clap up to 50 times</strong>, so get clicking/tapping! 😉</p><p>Make sure to follow me on <a href="https://medium.com/@nicklewanowicz">Medium</a>/<a href="https://twitter.com/imnickdev">Twitter</a>/<a href="https://github.com/nicklewanowicz">Github</a> to see what I’m up to.</p><p>Please share the post with your developer friends on your social media outlet of choice.</p><p>Thanks to <a href="https://medium.com/@matschmidy">Mat Schmid</a> and <a href="https://www.linkedin.com/in/chris-ermel-391650a6/">Chris Ermel</a> for revising drafts of this post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c33dc4c86c31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PWA: The Future of Mobile and Web Development]]></title>
            <link>https://medium.com/@nicklewanowicz/pwa-the-future-of-mobile-and-web-development-d3138cf91e0a?source=rss-3b893ccd1787------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3138cf91e0a</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[pwa]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Nicholas Lewanowicz]]></dc:creator>
            <pubDate>Wed, 14 Nov 2018 14:38:39 GMT</pubDate>
            <atom:updated>2019-07-31T17:10:09.141Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/925/1*RuMEG05QVgZ-V1r4l8soHQ.png" /></figure><p>Over the last 5 years the web has been evolving at break neck speed to catch up to the snappy and reliable experience that Native Apps are known for. Finally they might be taking the lead. The good news is you’re not late to the party, <strong><em>yet</em></strong>.</p><h3>Native Apps have not aged well.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lfuAucPysEioaTlZzqcz4w.png" /></figure><p>Unbounded access to broadband internet in developed countries has allowed native applications to become bloated. Though Google has made efforts to reduce overall package sizes in the Play Store both iOS and Android applications exceed 100MB regularly and average 34MB and 12MB respectively; this may not seem bad but lets look at Instagrams iOS app at 161MB while the PWA is 233KB; 1/500th the size. This may be inconsequential for us, that same bandwidth could be a significant portion of a users annual salary. In <a href="https://webfoundation.org/2017/11/what-does-it-cost-to-purchase-broadband-data-in-developing-countries/">Africa 1GB of mobile data can cost ~10% of your annual income</a>.</p><h3>Web Apps are better.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*HhSQDyoaEwXn2gS6Box-mA.png" /></figure><p>The average American installs less than 2 new apps a month. This is a scary (and expensive) prospect if you are trying to launch an application with a large install base. Google suggests that every action required to install an application doubled the chance of abandonment. Web apps offer what Native apps can’t as they are immediately demo-able; simply clicking a google search result can drop you immediately into the app experience. Rather then being forced to install an app to fulfill a need, you use the app first and decide after if you want to install it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*rpmgHpHoCa9rHTZ6hTqW-g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/1*ZDXkn8TUS41A0qrTLw0vDA.png" /><figcaption>Left: Native Instagram App on Ipad, Right: Instagram PWA</figcaption></figure><p>Since 2012 the number of unique android device types have quadrupled and iOS has been following suit. Due to Web apps being run on many more devices than Native Mobile Apps and having been much more time to build tools which make responsive design easier, there is a clear advantage working with web frameworks for this purpose atleast until some point where Native frameworks have equally robust tools to support responsive design.</p><h3>Why PWAs are great!</h3><p><em>(in a nutshell)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*IIko2MMQZG4j7_puU3EX2Q.png" /></figure><p>If you have been in the industry for any amount of time you might be asking what makes PWAs different than using PhoneGap, React Native, Ionic, or any other technology that promises a homogenous codebase. <strong>ServiceWorkers</strong> and <strong>Web deployment/install</strong>.</p><ul><li><strong>ServiceWorkers</strong>: Put simply a “service worker” is a process your web app controls beyond the scope of your application, this exists outside the single browser tab and allows you to mimic features the were previously only available to native apps (mobile or desktop). This is a feature available to any web app with <a href="https://caniuse.com/#feat=serviceworkers">nearly any browser</a>.</li><li><strong>Web Deployment: </strong>Web based installs give you one click install on any platform from the same place. Tools like React Native and Ionic are fantastic for building fully native experiences, but with them comes the cumbersome process of submitting to an centralized store and thus forfeiting a significant percentage of your revenue.</li></ul><h3>Final Thoughts</h3><p>Native Apps still have a important role to play and are capable of doing many things web apps cannot but it’s time to realize that the gap between the two is narrowing quickly. Its clear to see that 2019 is going to be a big year for PWAs, and it will be exciting to see how native apps evolve as a result.</p><h3>Thank you for making it here!</h3><p>If you enjoyed this post, please leave some claps. 👏👏👏</p><p><strong>You can clap up to 50 times</strong>, so get clicking/tapping! 😉</p><p>Make sure to follow me on <a href="https://medium.com/@nicklewanowicz">Medium</a>/<a href="https://twitter.com/imnickdev">Twitter</a>/<a href="https://github.com/nicklewanowicz">Github</a> to see what I’m up to.</p><p>Please share the post with your developer friends on your social media outlet of choice.</p><p>Thanks to <a href="https://medium.com/@matschmidy">Mat Schmid</a> and Sam Wheating for revising drafts of this post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3138cf91e0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>