<?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[Chip - Medium]]></title>
        <description><![CDATA[We’re the team behind Chip, the AI savings app. We’re automating your money stuff, so you can make the things you want in life happen. getchip.uk - Medium]]></description>
        <link>https://medium.com/get-chip?source=rss----52f466a2d2a---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Chip - Medium</title>
            <link>https://medium.com/get-chip?source=rss----52f466a2d2a---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:35:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/get-chip" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Chippin’ away at the Monolith]]></title>
            <link>https://medium.com/get-chip/chippin-away-at-the-monolith-eb0ab8e2bbe?source=rss----52f466a2d2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/eb0ab8e2bbe</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[monolith]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Jack Tudor]]></dc:creator>
            <pubDate>Thu, 14 Nov 2019 11:31:12 GMT</pubDate>
            <atom:updated>2019-11-14T11:37:36.676Z</atom:updated>
            <content:encoded><![CDATA[<h4>An overview of how the iOS team at Chip is moving to a modular codebase!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*Z1D2tkZX3WE00zTd5TRtgg.png" /><figcaption>Breaking big things into small things, one Chip at a time.</figcaption></figure><p>This isn’t a “how-to” guide, but really documenting what challenges we have faced and what solutions we came up with, I hope it sparks some ideas you can use in your own project.</p><p>To provide a bit of context, I’ve only been at Chip for around four months, but the codebase is around 18–24 months old. We are using RxSwift with the Model-View-ViewModel (MVVM) design pattern.</p><p>When I first joined, the app did have Cocoa Touch Frameworks for common/shared modules but not at all for feature modules, which if introduced would help the codebase scale, make it a lot easier to navigate and ultimately pleasant to work with. This is very similar to what Backend Engineers call Micro-services.</p><p>The distinction between them is; feature modules know nothing about each other, so must never import each other. Any code that needs to be shared between feature modules should be moved into a common module.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hHfVFDYuuYMVO_WTeG_S-Q.png" /><figcaption>What we set out to achieve.</figcaption></figure><h3>Where did we start?</h3><p>Within the first week, <a href="https://medium.com/@adam_chip">Adam</a> and myself (Chip’s iOS team), decided to start moving some of the app’s tabs into separate feature modules. First being Chip X.</p><p>This was the Tab with the smallest amount of logic, so it was fairly easy to decouple and we were able to immediately reap rewards, as we not long after had to build some new features within it.</p><p>After getting a taste of modularisation, I tried to move another Tab (Account) into its own module.</p><p>This turned into a nightmare as I tried to move one object, it was relied upon by multiple others, so rather than wasting anymore time I stopped. We had to take a bit of a step back to work out what was causing us the biggest pain when trying to move anything, when creating the Accounts module, the biggest issue was anything relating to our models / API resources.</p><h3>Solving our first problem</h3><p>The problem: No clear separation of concerns within the main project or at least a clear binding between the ViewModels and our domain objects. To solve this we moved all of our models out of the main project and into a common module (ChipAPI).</p><p>This was not ideal but was necessary to achieve what we wanted to do. The reasoning behind this was to allow us to freely move all of our UI code out and into feature modules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HCX8NSSzE4r9lGtKJr_swQ.png" /><figcaption>After moving Chip X into its own module.</figcaption></figure><p>We agreed that this was temporary solution, and that when a new feature module was created we should move the models and API functions so they aren’t shared with the whole codebase. This allowed us to start moving code into feature modules.</p><h3>It wasn’t our only problem…</h3><p>If you come from a codebase that has been built in a way where everything is tightly coupled, there are going to be a few things you’ll need to extract and use a bridge between those components until you’ve completed the migration.</p><p>For example, we have a UserService which is responsible for fetching any resources relating to the user and populating model objects. This is used throughout the codebase as we need to know details about the users state across the app.</p><p>But we didn’t want to share any of that implementation detail with the “Activity” framework, because it doesn’t need to know about the inner-workings of the class. We created a ActivityAdapter that has our UserService injected and conforms to our ActivityAdapterType which declares what is needed from our UserService:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/474/1*hew3NSqWJmD-1l20JsFMSA.png" /><figcaption>Our ActivityAdapter which is responsible for transforming our models</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/1*EXo6cl0yCtGQoYphkAw3sw.png" /><figcaption>ActivityFramework doesn’t need to be exposed to UserService</figcaption></figure><p>With an adapter we’re able to pass this into our ActivityCoordinator, to enable it access to these shared models whilst still being able to test the adapters by providing a mock type in our unit tests. Our Coordinator is the entry point into our framework and manages the relationship between the controllers in the framework.</p><h3>What were the biggest benefits of doing this?</h3><p>Some readers might be thinking if everything works, where is the benefit?</p><p>As the team begins to scale, we want to be able to work on features and areas of the codebase in isolation of one another. We don’t want to deal with huge conflicts when there’s many developers committing code.</p><p>It allows us to set a solid foundation for which we can build upon over the next few years, whilst the job isn’t complete it’s important to bear in mind that this will really set us up for the future.</p><p>Improved build times with a modular approach because we don’t need to rebuild the whole project, but rather that module so it’s much quicker developing features.</p><p>We’re able to see tangible evidence of this, we’re releasing at such a frequent rate (around every 1–2 weeks on average). The number of bugs we’re finding in the app is much lower than a few months ago, and our App Store rating has increased by nearly one whole star!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/298/1*139vfhIPi2rt6HjF_u17VA.png" /><figcaption>This is how the Chip iOS codebase highlevel structure looks now</figcaption></figure><h3>What’s next?</h3><p>This process is always evolving and never stops, it’s likely we’ll want to breakdown these feature modules further as they continue to grow, this is something we’re beginning to do now with some of the older parts of the codebase.</p><p>We’re constantly looking to make improvements in our ways of working, whether that’s architecture, testing or code styling.</p><p>If you’re interested in learning how to create a Cocoa Touch Framework, Sam Dods has an excellent <a href="https://edit.theappbusiness.com/modular-ios-strangling-the-monolith-4a6843a28992">blog series</a> outlining how you can make a start.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb0ab8e2bbe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/get-chip/chippin-away-at-the-monolith-eb0ab8e2bbe">Chippin’ away at the Monolith</a> was originally published in <a href="https://medium.com/get-chip">Chip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Bug’s Life: From Initial Reports to Fixed & Deployed]]></title>
            <link>https://medium.com/get-chip/a-bugs-life-from-initial-reports-to-fixed-deployed-51d1740d74cd?source=rss----52f466a2d2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/51d1740d74cd</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Harry Fisher]]></dc:creator>
            <pubDate>Thu, 26 Sep 2019 11:16:29 GMT</pubDate>
            <atom:updated>2019-09-26T12:47:36.175Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Bug’s Life: from initial reports to fixed &amp; deployed</h3><h4>How we report, fix and squash any bugs we find in the app.</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F12GnkxDFm8PVKg%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F12GnkxDFm8PVKg%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F12GnkxDFm8PVKg%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="177" frameborder="0" scrolling="no"><a href="https://medium.com/media/94ab0fee0518c50bcea3ddb521af1f1a/href">https://medium.com/media/94ab0fee0518c50bcea3ddb521af1f1a/href</a></iframe><p>Over the past year the Chip app has gone from strength to strength unveiling many new releases, from v1.0 all the way to the current v2.3 app.</p><p>Each new release increases the power and capabilities of the app meaning we are able to process saves at lightning fast speeds, set funds aside with ease and make things happen.</p><p>With better builds of the app, however, comes a more complex internal system that can bring forward new bugs that we need to amend. We’ve recognised this, and changed our approach to bug reporting so no bug goes unnoticed.</p><h3><strong>Identification</strong></h3><p>Firstly, we need to identify the ins and outs of any bug brought to our attention. That is where you come in! Whilst we currently rely on reading our own data, monitoring certain backstage metrics and rigorous QA testing — we often become aware of a bug once it has been raised on either Chip app’s live chat feature or our help email address (hello@getchip.uk).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FlXiRHerN9QScmNrYQ%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FlXiRHerN9QScmNrYQ%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FlXiRHerN9QScmNrYQ%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/258243db65fe6876a4f8d15084ecc44b/href">https://medium.com/media/258243db65fe6876a4f8d15084ecc44b/href</a></iframe><p>This process begins with a Chip user flagging an issue they are experiencing with their app, and we as Customer Success team will explore the issue to the best of our ability and knowledge.</p><p>If this is a known bug then we will be able to guide the customer to a solution there and then; be that amending their account or giving a timeline that lays out when they can expect this to be back to normal in the app.</p><p>If this is an issue we are unaware of, we are not afraid to ask for help. In a situation like this, we require the Operations team to help explore the finer details of your Chip account.</p><h3>The bug squishing squad</h3><p>We currently operate within a Slack channel that includes all of the Customer Success Team, Operations, and Samy (our Scrum master, more on him later!) and use this as an internal forum for any new issues that come our way.</p><p>Anyone in the channel can submit a query (normally this is customer specific and very detailed) and the different departments can offer any advice or solutions that they see fit.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FKsr5BrQ9YhGnK%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FKsr5BrQ9YhGnK%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FKsr5BrQ9YhGnK%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/2a34a1347ecbe1b0c229248a2d9a48a0/href">https://medium.com/media/2a34a1347ecbe1b0c229248a2d9a48a0/href</a></iframe><p>If between Operations and Customer Success we cannot get to the bottom of an issue, Samy will then take the issue and assign it a ticket on our developer’s online JIRA board (where all known bugs/fixes are kept).</p><p>This is a board of virtual tickets that Samy can then discuss with his two development teams and put into a developers’ sprint. The aim of the sprint is to have the issues selected for that sprint fixed to be deployed by the end of the two week period.</p><h3>Scrum and agile: so hot right now</h3><p>Made famous by not only by companies such as Google, Microsoft, and Amazon, but also HBO TV series Silicon Valley: Scrum is a way of working that allows priority and focus on a certain task.</p><p>In essence, it is an agile framework that focuses on delivering business value incrementally as a team — not as individuals.</p><p>The team can then accept responsibility for their achievements and attempted achievements. Samy enjoys this system and has implemented it because it encourages constant reflection and growth and allows teams to be more responsive to change.</p><p>The developers then amend these issues ready for release onto the app. If successful, this fix can be deployed into our system and go live on the app.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxT1XGOGdyDrL2BTfxK%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FxT1XGOGdyDrL2BTfxK%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FxT1XGOGdyDrL2BTfxK%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/98902a00c7c960885c6f031d40761b04/href">https://medium.com/media/98902a00c7c960885c6f031d40761b04/href</a></iframe><h3>The end of bugs</h3><p>So that’s the journey in a nutshell: from live chat to app fix.</p><p>With this new system we have already noticed a sharp decrease in the time taken to amend bugs in the app.</p><p>We can’t guarantee there’ll be no more bugs in the future (as the maxim goes: where’s there’s bugs), but we’re very confident that any bugs that rear their ugly heads in future will now be dealt with faster than the flap of a bee’s wings.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51d1740d74cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/get-chip/a-bugs-life-from-initial-reports-to-fixed-deployed-51d1740d74cd">A Bug’s Life: From Initial Reports to Fixed &amp; Deployed</a> was originally published in <a href="https://medium.com/get-chip">Chip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Property Wrappers in Swift 5.1]]></title>
            <link>https://medium.com/get-chip/propert-wrappers-in-swift-5-1-14f610530710?source=rss----52f466a2d2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/14f610530710</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Adam Waite]]></dc:creator>
            <pubDate>Thu, 26 Sep 2019 10:56:55 GMT</pubDate>
            <atom:updated>2019-10-02T17:53:10.970Z</atom:updated>
            <content:encoded><![CDATA[<h4>An introduction to one of Swift 5.1’s powerful new features: Property Wrappers. We implement a property wrapper to improve a common pattern we’re faced with when writing unit tests.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7sFmEX9u1AcddsP1ow7i0w.jpeg" /><figcaption>Vincent Pradeilles presents Property Wrappers or How Swift decided to become Java</figcaption></figure><p>Chip sent the Apps Team to <a href="https://2019.nsspain.com/">NSSpain</a> last week. All of the talks were excellent but my personal favourite was “<em>Property Wrappers or How Swift decided to become Java” </em>by <a href="https://twitter.com/v_pradeilles">Vincent Pradeilles</a>.</p><p>In his talk Vincent introduced a new feature in Swift 5.1 that perhaps got overshadowed in the excitement of SwiftUI and Combine: <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0258-property-wrappers.md">property wrappers</a>.</p><p>Property wrappers are comparable to <a href="https://kotlinlang.org/docs/reference/annotations.html">Kotlin’s annotations</a>. Simply put, property wrappers encapsulate read and write access to a property while adding extra behaviour. We might use a property wrapper, for example, to read and persist values to UserDefaults when accessed.</p><p>If you’ve played with SwiftUI, then you might have written something along the lines of:</p><p>@State var labelText: String = &quot;Make it happen!&quot;</p><p>That @State bit, that’s a property wrapper. It adds behaviour to var labelText so that whenever it’s mutated any associated bindings are updated to reflect the change.</p><h3>Implementing a property wrapper</h3><p>Let’s discover the power of property wrappers by building our own. Our property wrapper will address a common pattern we’re faced when writing unit tests.</p><p>As well behaved iOS developers, we strive to use dependency injection techniques to promote clear separation of concerns, modularity and highly testable code. In a unit test we might inject a dependency in the form of a <a href="https://martinfowler.com/bliki/TestDouble.html">test double</a> and later verify it was called with the expected arguments. We might also verify the count of calls. This is often called a spy.</p><h4><strong>Our app: Dog Browser</strong></h4><p>Our app presents dogs (because, dogs):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C9JsPxrMbRdt2Bf4snaRKg.png" /><figcaption>Dog model</figcaption></figure><p>We have an API client interface APIType that we’ll use to fetch dogs from a remote service (perhaps the <a href="https://dog.ceo/dog-api/">dog-api</a>):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QC5jzQI_NIoaw9ujDqnacw.png" /><figcaption>APIType interface</figcaption></figure><p>And we have a view model that will drive a view controller with some dogs to display:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P2dAu74CGbFiyemBxFYnfQ.png" /><figcaption>DogsViewModel will drive a view controller (we might handle errors in production, if we feel like it)</figcaption></figure><h4>Testing</h4><p>Let’s test DogsViewModel. We want our test to make sure that when we invoke getDogs on our subject, our injected API is instructed to fetch dogs at the correct URL (inferred from breed).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XtZbR-b4dIqDJBmRv3Vvyg.png" /><figcaption>DogViewModelTests</figcaption></figure><p>As previously mentioned, in a unit test we’ll often want to count how many times a dependency is invoked, and with what arguments. Below we’ve added this behaviour by making getCalledWithURL an Array, and appending each call:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SdG7yP6ljRouOCoG5Plnbg.png" /><figcaption>DogViewModelTests this time appending invocations in an Array</figcaption></figure><p>Having invocations tracked in an array allows us to verify multiple calls to the stub, but that’s going to get tedious when most of the time we’ll just want to verify the latest call.</p><p>It’s tedious because we’d have to pull values out of the collection to assert on them (e.g XCTAssert(testAPI.getCalledWithURL.last?,...). We could split them into two variables: latestGetCalledWithURL: URL and getCalledWithURLHistory: [URL], but doing that for every variable in every test creates duplication.</p><h4><strong>Enter @Spy, our @propertyWrapper!</strong></h4><p>We want to add behaviour to getCalledWithURL to track set history so that we can assert the count and ordering of mutations. At the same time we don’t want to have to deal with pulling the latest value out of an array type. We’re going to implement a property wrapper called @Spy to do just this.</p><p>To be a property wrapper a type must:</p><ol><li>Be defined with the attribute @propertyWrapper</li><li>Have a property named wrappedValue</li></ol><p>Let’s implement @Spy as a struct:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wa1saZLcRwhkMgWK8rLZ2A.png" /><figcaption>A property wrapper called Spy</figcaption></figure><p>We can now decorate getCalledWithURL with @Spy :</p><pre>@Spy var getCalledWithURL: URL? = nil</pre><p>As if by magic the compiler has synthesised that as a private variable holding the property wrapper (prefixed with an underscore), and a property that forwards any getter and setter calls to the wrapper (going through Spy’s implementation).</p><p>i.e @Spy var getCalledWithURL: URL? = nil is synthesised as:</p><pre>private var _getCalledWithURL = Spy&lt;URL?&gt;(wrappedValue: nil)</pre><pre>var getCalledWithURL: URL? {<br>  get { return _getCalledWithURL.wrappedValue }<br>  set { _getCalledWithURL.wrappedValue = newValue }<br>}</pre><p>This means that you’ll be able to access _getCalledWithURL inside the scope of the defining type without doing anything.</p><p>Let’s implement a history and set count to Spy:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LSO9JUL6zCuxJPUVNZmHWQ.png" /><figcaption>Adding behaviour in Spy wrappedValue setter</figcaption></figure><p>By updating the wrappedValue setter, every time getCalledWithURL is mutated the spy is updated with a record of the set in the history variable. The computed property count will return the number of times that the variable has been mutated.</p><p>It took me a long time to figure this one out…but we can expose the property wrapper to the outside world by implementing projectedValue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3VEow5tr2tB0qOj9-Y9sUA.png" /><figcaption>Implementing projectedValue to expose the property wrapper</figcaption></figure><p>When projectedValue is present, a new variable prefixed with $ is synthesised exposing the property wrapper:</p><pre>public var $getCalledWithURL: Spy&lt;URL?&gt; {<br>  get { _getCalledWithURL.projectedValue }<br>  set { _getCalledWithURL.projectedValue = newValue }<br>}</pre><p>We’re now ready to use the property wrapper in our tests:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jwtRdbMPFy77Kac6O0RIDg.png" /><figcaption>Using the property wrapper in the tests to track call history</figcaption></figure><p>Going forward, any variable annotated with @Spy will hold a history of any mutations and an associated count. They’re accessible through $getCalledWithURL.</p><p>Since we have defined Spy&lt;Value&gt; ourselves we can add infinite behaviour. We might for example want to add a log of time stamps, the thread the set was performed on, or even a time delta if we’re implementing throttle behaviour.</p><h3>Conclusion</h3><p>Property wrappers are a powerful new feature in Swift 5.1. By implementing @propertyWrapper we can decorate variables with additional behaviour on read and write. Property wrappers come with great potential for improving safety, reducing complexity and removing boilerplate code.</p><p>Enjoy!</p><p>Some further reading:</p><ul><li><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0258-property-wrappers.md#proposed-solution">Property Wrappers Swift Proposal</a></li><li><a href="https://nshipster.com/propertywrapper/">NSHipster: Swift Property Wrappers</a></li><li><a href="https://www.swiftbysundell.com/articles/the-swift-51-features-that-power-swiftuis-api/">Swift by Sundell: The Swift 5.1 features that power SwiftUI’s API</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14f610530710" width="1" height="1" alt=""><hr><p><a href="https://medium.com/get-chip/propert-wrappers-in-swift-5-1-14f610530710">Property Wrappers in Swift 5.1</a> was originally published in <a href="https://medium.com/get-chip">Chip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing the Chip Community Forum!]]></title>
            <link>https://medium.com/get-chip/introducing-the-chip-community-forum-1154b14b73cb?source=rss----52f466a2d2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/1154b14b73cb</guid>
            <category><![CDATA[social-media-marketing]]></category>
            <category><![CDATA[community-engagement]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Sarah Dyer]]></dc:creator>
            <pubDate>Tue, 30 Jul 2019 17:05:01 GMT</pubDate>
            <atom:updated>2019-07-30T17:05:01.126Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why we started moving our community discussions to our own forum.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r-vJne3gC5RywRdv3WND5w.png" /></figure><p>Last week, we launched the <a href="https://community.getchip.uk/">Chip Community Forum</a> to the world, and we’ve been blown away by the reception so far!</p><p>But why did we decide to start our own forum, how did we go about getting it ready for launch, and what’s coming next? I thought I’d take some time to answer these questions, and hopefully you’ll be rushing to sign up and get involved before I’m done!</p><h3>The limits of social media</h3><p>First up, why start a forum? Especially when we already have Facebook groups for the <a href="https://www.facebook.com/groups/1813887475332477/">ChipMunks</a> and our <a href="https://www.facebook.com/groups/Chipinvestors/">investors</a>?</p><p>To put it politely, Facebook isn’t an ideal platform. Topics and conversations can be hard to follow, even if Facebook’s algorithm decides to show them to you!</p><p>By moving to our own forum, we can better organise the categories and topics so that whatever you’re looking for, or want to post, you can quickly and easily find the best place for it.</p><p>The forum also means that the whole Chip community are in one place. Sure, there’s special sections for investors and ChipMunks (more on that in a bit), but the majority of it is open for all Chippers to come together and chat about… well, anything, really!</p><p>Want to chat about your latest Netflix binge or ask for help on ways to save money? On the Chip forum, you can!</p><h3><strong>Getting the forum ready</strong></h3><p>So how did we go about getting the forum ready? First, we created the categories, based on the type of conversations which we want to encourage, in a structure which we think makes sense.</p><p>Of course, it may be changed in the future depending on how it works in reality! It’s all about seeing what’s best for the community.</p><p>We then invited members of the Chip community to join the forum in stages; starting with investors, then ChipMunks, and then everyone.</p><p>This slow rollout meant we could keep an eye out and see how the layout and software was working and make changes easily, rather than get swamped with new users and have everything go horribly wrong!</p><p>Luckily, the rollout went nice and smoothly, and the forum is now open to everyone! We hope you’ll come and join us for some chat, to ask the Chip team some questions, or get some advice from your fellow Chip users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w4lNtRoCqOClLp2WVL_pQw.jpeg" /></figure><p>But what if you want to help make Chip better than ever, give feedback on new features and get the chance to win some special goodies and prizes to boot?</p><p>Then you’ll want to join the ChipMunks, our super-special group of Chippers. As a ChipMunk, we’ll be coming to you to see what you think of Chip’s upcoming features way ahead of everyone else, you’ll be able to take part in exclusive Q&amp;As with Team Chip, and so much more.</p><p>To sign up, just create your account on the Chip Forum and then <a href="https://www.getchip-community.uk/chipmunk-application-page">head here</a> to apply to join the ChipMunks!</p><p>And if you’re an investor? Well, we have a special investor-only section of the forum, just for you. Once you’ve created your forum account, you can request access to this section <a href="https://www.getchip-community.uk/investor-forum-access">here</a>.</p><p><a href="https://community.getchip.uk/">See you on the forum!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1154b14b73cb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/get-chip/introducing-the-chip-community-forum-1154b14b73cb">Introducing the Chip Community Forum!</a> was originally published in <a href="https://medium.com/get-chip">Chip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Faster, better, stronger networks at ChipHQ]]></title>
            <link>https://medium.com/get-chip/corporate-network-improvements-b3756bb8682b?source=rss----52f466a2d2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/b3756bb8682b</guid>
            <category><![CDATA[firewall]]></category>
            <category><![CDATA[ubiquiti]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[wifi]]></category>
            <dc:creator><![CDATA[Charlie Jennings]]></dc:creator>
            <pubDate>Tue, 02 Jul 2019 14:31:55 GMT</pubDate>
            <atom:updated>2019-07-04T00:36:32.552Z</atom:updated>
            <content:encoded><![CDATA[<h4>Making some improvements to our network</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xo2-Vu63MNXFFBiNZFDT9g.jpeg" /></figure><p>The more Chip grows, the more strain we are putting on our networking infrastructure.</p><p>In order to facilitate the growth of our teams, we are investing in beefing up our networking facilities for our London HQ.</p><p>One of the fun things about being a developer at a fast growing start-up is the variety of challenges you need to deal with. Unlike in a big company, if you don’t take initiative and fix it, no one else will (the upshot of this is stuff is probably actually fixed much quicker).</p><p>My job has evolved to become a bit of a “hacker in residence”, i.e. Chip’s official fixer. I love solving problems - whether it’s a mechanical issue with hardware, or fixing some code.</p><p><a href="https://getchip.recruitee.com/">Drop us a line</a> if you like solving problems and can code!</p><p>So when I decided I wanted to tidy up Chip’s network infrastructure, I received the full support of <a href="https://medium.com/u/f442d21ad0fd">Alan Cole</a>, our VP of Engineering, and everyone at Chip!</p><h3>Productivity</h3><p>We live in a digital era where the reliability of your connection to the internet can determine how productive you are.</p><p>Not only can it be frustrating to struggle through a s-l-o-o-w connection, it can also hinder productivity. Just about every discipline in the modern workplace (particularly in the tech and start-up sector) relies on fast, reliable internet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fDC32SGlW_5ZvuPg" /><figcaption>Photo: <a href="https://unsplash.com/@marcojodoin?utm_source=medium&amp;utm_medium=referral">Marc-Olivier Jodoin</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Think fast</h3><p>I researched into the best bang-for-buck solution for us as a company, Ubiquiti Networks offer solutions which include up-to-date hardware with super intelligent software.</p><h3>Hardware</h3><h4>Ubiquiti Unifi AP AC PRO</h4><p>Access points (APs to those of us in the IT infrastructure business) offer 802.11ac with 3x3 MIMO, water resistant design with Power over Ethernet (PoE), allowing us to extend our network to where is required (within reason).</p><p>They also have a very nice appearance, so will look good in the office (believe it or not). This is a big plus, given how most networking hardware aren’t going to win any beauty pageants.</p><p>But these APs tick both appearance and performance boxes!</p><p>Despite having multiple access points, we only have one network. This means we don’t need to remember multiple passwords, or manage many networks, as our devices seamlessly ‘hop’ between the access points.</p><p><a href="https://www.ui.com/unifi/unifi-ap-ac-pro/">Ubiquiti Networks - UniFi® AP AC PRO</a></p><h4><strong>UniFi® Security Gateway</strong></h4><p>To keep us protected from the outside world, we opted for a UniFi® Security Gateway. Not only does this act as our firewall, it also allows us to run multiple WAN connections to ensure we stay online at all times.</p><p>This level of redundancy is something we have had for a while, but it was two different networks previously. Now, with this hardware, we have one network.</p><p>This also allows staff to connect via VPN from off site locations (including our Latvia office).</p><h3>Unified configuration</h3><p>Traditional networking hardware usually has a configuration UI per device.<br>UniFi® hardware is a bit different in that respect, no device has any configuration utility per-say, it’s all configured centrally via a self hosted tool.</p><p>I guess it’s all in the name, ‘UniFi®’.</p><blockquote>Developer note: The Unifi UI is actually built in <a href="https://angularjs.org/">Angular</a>!</blockquote><p>If you don’t want to get involved in hosting your own you can use a <a href="https://www.ui.com/unifi/unifi-cloud-key/">CloudKey</a>.</p><h3>The roll-out</h3><p>The new network was rolled out along side the existing network setup to eliminate any downtime for staff. Feedback across the team has been great.</p><h3>Here’s to fast &amp; reliable internet!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*NNFV5kCAwJ9O52q5pXFK0w.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3756bb8682b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/get-chip/corporate-network-improvements-b3756bb8682b">Faster, better, stronger networks at ChipHQ</a> was originally published in <a href="https://medium.com/get-chip">Chip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to setup Ghost with Gatsby]]></title>
            <link>https://medium.com/get-chip/how-to-setup-ghost-with-gatsby-add924674873?source=rss----52f466a2d2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/add924674873</guid>
            <category><![CDATA[gatsbyjs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[ghost-cms]]></category>
            <dc:creator><![CDATA[Aditya Agarwal]]></dc:creator>
            <pubDate>Fri, 14 Jun 2019 08:03:03 GMT</pubDate>
            <atom:updated>2019-06-14T08:03:03.747Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bo0AHvG_vb2KBV7unCCptA.png" /><figcaption>Image from Modern publication with Ghost and Gatsby</figcaption></figure><p>We all know that <a href="https://www.gatsbyjs.org/">Gatsby</a> is a powerful tool to build websites with React. In-fact, it’s how the <a href="https://medium.com/get-chip/chips-brand-new-website-7f07f390849f">Chip website was built</a>.</p><p>Gatsby allows us to pull data from anywhere and put it into components and allow us to use this data in our own way. This data pulling is powered by <a href="https://graphql.org/">GraphQL</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*FLpsZOoRddWaRkYBWBennQ.png" /><figcaption>Gatsby Flow</figcaption></figure><p><a href="https://ghost.org/">Ghost</a> is headless CMS that allows the users to maintain the content of the page and also allow creating the pages directly from its admin panel.</p><p>Ghost was tightly coupled with three things:-</p><ol><li>Ember.js</li><li>Node.js API</li><li>Handlebar.js</li></ol><p><a href="https://blog.ghost.org/jamstack/">Read more about the coupling here</a>. But recently Ghost has launched its open API so we can access the Ghost likely from anywhere.</p><h3>Setup Ghost with Gatsby</h3><p>I assume that Node is installed in your local machine, with a package manager, NPM, or Yarn.</p><p>There are three steps to set up a Gatsby project with Ghost:-</p><ol><li>Setting up Ghost in your local machine</li><li>Creating a Gatsby project</li><li>Connecting Ghost with your Gatsby project</li></ol><h4>1. Setting up Ghost in the local machine</h4><p>Ghost can be installed in the local machine by <strong>ghost-CLI</strong>. Use the following command to install this:</p><p>$ npm install ghost-cli@latest -g</p><p>Now to install <strong>ghost,</strong> create an empty directory and <strong>cd </strong>into it and run following command:-</p><p>$ ghost install local</p><p>Once the install is finished you’ll be able to access your new site on<a href="http://localhost:2368/"><strong><em>http://localhost:2368</em></strong></a> and <a href="http://localhost:2368/ghost"><strong><em>http://localhost:2368/ghost</em></strong></a> to access Ghost Admin. You can open the Ghost admin in your favorite browser.</p><h4>2. Creating a Gatsby project</h4><p>We will simply clone the <strong>gatsby-starter-ghost </strong>to create our Gatsby project. Run the following command in your terminal:</p><p>gatsby new gatsby-start-ghost <a href="https://github.com/TryGhost/gatsby-starter-ghost.git">https://github.com/TryGhost/gatsby-starter-ghost.git</a></p><p>Make sure you have installed the <strong>Gatsby-CLI </strong>before you run this command. After this, you can run <strong>yarn </strong>command to install the dependencies and <strong>gatsby develop </strong>to start your development server. You can see your website at <a href="http://localhost:8000/">http://localhost:8000</a></p><h4>3. Connecting Ghost with your Gatsby project</h4><p>By default, the content you see at <a href="http://localhost:8000/"><strong><em>http://localhost:8000</em></strong></a> is served by default Ghost install at <a href="https://gatsby.ghost.io/"><strong><em>https://gatsby.ghost.io/</em></strong></a>. But we want to connect our own local ghost so we can control the content of the site.</p><p>First of all open, the <strong>Ghost Admin</strong> located at<a href="http://locathost:2368/ghost"> <strong><em>http://locathost:2368/ghost</em></strong></a></p><p>Next, create an account and log in. Then you have to create a custom integration for your Gatsby project.</p><p>For this go to <a href="http://localhost:2370/ghost/#/settings/integrations"><strong><em>http://localhost:2368/ghost/#/settings/integrations</em></strong></a> and click the <strong>Add Custom Integration. </strong>Enter the name of your custom integration. After creating this you can see a page like this:-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YipYv5raxuq0-D1aaq8zBg.png" /><figcaption>Image after custom integration</figcaption></figure><p>Go to your project directory and replace the value of <strong>apiUrl </strong>and <strong>contentApi</strong> field with the value on you see on your page, in both <strong>development </strong>and <strong>production.</strong></p><p>Restart your development server and 🎉 😍 you have connected your project with Ghost.</p><p>Head into your Ghost Admin and create a new page by clicking at <strong>pages </strong>and publish it. Let’s say URL of this page is <strong>/about-me</strong>.</p><p>Then finally, restart your development server (again) and go to <a href="http://localhost:8000/about-me"><strong><em>http://localhost:8000/about-me</em></strong></a> . Your new page has been published!</p><p>Thanks for reading. Further resources and references:-</p><ol><li><a href="https://www.gatsbyjs.org/blog/2019-01-14-modern-publications-with-gatsby-ghost/">Gatsby+Ghost announcement post</a></li></ol><p>2. <a href="https://blog.ghost.org/jamstack/">Ghost on Jamstack</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=add924674873" width="1" height="1" alt=""><hr><p><a href="https://medium.com/get-chip/how-to-setup-ghost-with-gatsby-add924674873">How to setup Ghost with Gatsby</a> was originally published in <a href="https://medium.com/get-chip">Chip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chip’s brand new website]]></title>
            <link>https://medium.com/get-chip/chips-brand-new-website-7f07f390849f?source=rss----52f466a2d2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/7f07f390849f</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[sass]]></category>
            <category><![CDATA[static-site-generator]]></category>
            <dc:creator><![CDATA[Charlie Jennings]]></dc:creator>
            <pubDate>Thu, 04 Apr 2019 11:08:01 GMT</pubDate>
            <atom:updated>2019-04-10T09:22:58.766Z</atom:updated>
            <content:encoded><![CDATA[<h4>The tools we used to build a ultra fast website in 2019</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A1s-y7TTXj3Za__kfpi8bQ.png" /></figure><h3>The Brief</h3><p>I was tasked with rebuilding Chip’s website from the ground up.<br>The site had to be fast, content managed, and be easy to navigate and understand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5XG0ZTTGWwYjAvPMii1tRg.gif" /></figure><h4>Design</h4><p>Using our new look and brand colours, our designer Harry worked alongside Liam, our UX expert to put together some wireframes &amp; designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FOIZ6UsBr-EN3f2NuigfDw.jpeg" /><figcaption>Liam at work.</figcaption></figure><h4>Copy</h4><p>Tom, the guy behind the voice of Chip, provided the copy for the site and helped me with the layout to ensure our message was clear, no matter the device.</p><h3>Content Management</h3><p>The content management system we chose to use for this project is called <a href="http://ghost.org/">Ghost</a>. It’s simple, fast, has a great API and community of committed developers behind it. It’s actually built with <a href="https://nodejs.org/en/">Node</a>.</p><p>Ghost also provides a fantastic <a href="https://ghost.org/downloads/">Desktop UI</a> also.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*s0IhASlR_TiY8ytb" /><figcaption>Photo by <a href="https://unsplash.com/@impatrickt?utm_source=medium&amp;utm_medium=referral">Patrick Tomasso</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Familiar tooling</h4><p>Ghost sports a similarly feature-rich experience with features comparable to those on Medium. Anyone who is familiar with Medium can easily hit the ground running.</p><h4>Adaptable Codebase</h4><p>With Ghost being open source, we have the ability to build plugins to allow our copywriters to do more without requiring developer assistance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cdZo6Yf42rXxy2gSDckOvQ.png" /></figure><h4>Standalone CMS</h4><p>Ghost has it’s own templating ability and can offer a frontend but in this case, we want to use it as a stand-alone CMS service and let Gatsby get content from the API. I’ll get into why in the next section.</p><h3>Static Site Generation</h3><p>The reason we wanted to use Ghost as a stand-alone CMS is that we wanted to compile our website down to static files rather than having a dynamic site slowing things down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6ioTpirrwFQcVRNL" /><figcaption>Photo by <a href="https://unsplash.com/@lukebrugger?utm_source=medium&amp;utm_medium=referral">Luke Brugger</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Server delay</h4><p>Instead of the user relying on a CMS service being available (and fast) every time it is requested, the site is compiled down to HTML, CSS &amp; JS (static) files.</p><p>Static files are easier to serve quickly than complex programs, so if the use case allows it, static site generation is a great thing to do if you want a better performing website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QywCDN6JpMy-Nxhc" /><figcaption>Photo by <a href="https://unsplash.com/@guibolduc?utm_source=medium&amp;utm_medium=referral">Guillaume Bolduc</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Automatic regeneration</h4><p>A new site will be automatically recompiled whenever new source code is deployed, or content is updated via the CMS.</p><h4>Short publishing delay</h4><p>The small downside to static site generation is that authors may experience a small delay in seeing their content go live, this is usually a short time while the new version of the static site is being built.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mGLerkx7dMgd5ak0" /><figcaption>Photo by <a href="https://unsplash.com/@chuttersnap?utm_source=medium&amp;utm_medium=referral">chuttersnap</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Benefits of static sites</h4><ul><li>Performance— The end user doesn’t experience an initial delay when requesting a page</li><li>Improved security — CMS can be away from the public internet, making this much safer</li><li>Better efficiency — Less CPU &amp; disk usage allowing for a smaller, cheaper and more an eco-friendly hosting solution</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*rI7pl5rxynq9VEkdkHBSSg.png" /></figure><h3>Meet; Gatsby</h3><p>Gatsby is a static site generator for <a href="https://reactjs.org/">React</a>. It’s also great at pulling in data from various sources.</p><p>In our case, we use the `gatsby-source-ghost` package to get our content from Ghost into Gatsby. It uses <a href="http://grap/">Facebook’s GraphQL</a> to query data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0-dGbeSqbPLOGmbO" /><figcaption>SassPhoto by <a href="https://unsplash.com/@neonbrand?utm_source=medium&amp;utm_medium=referral">NeONBRAND</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Detecting devices</h4><p>As we show buttons linking to our iOS &amp; Andriod apps, we decided that hiding the Andriod button for iOS (and vice versa) would be a nice touch. To achieve this, a package called react-device-detect was used. It makes the process of reliably detecting devices very easy.</p><pre>if (isAndroid) {</pre><pre>    return &lt;AppButton store=&quot;android&quot; /&gt;</pre><pre>} else if (isIOS || isMobileSafari) {</pre><pre>    return &lt;AppButton store=&quot;ios&quot; /&gt;</pre><pre>} else {</pre><pre>return &lt;div&gt;</pre><pre>        &lt;AppButton store=&quot;android&quot; /&gt;</pre><pre>        &lt;AppButton store=&quot;ios&quot; /&gt;</pre><pre>    &lt;/div&gt;</pre><pre>}</pre><h4>Reusable Components</h4><p>I took the time to build beautiful and reliable UI components. These components may be useful for future Chip user interfaces, what’s to say the header should be written for every new project we do? Yes, we can copy and paste, but how do we maintain every instance and keep those consistent?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Djv1IDpuYkS2frQO" /><figcaption>Photo by <a href="https://unsplash.com/@der_maik_?utm_source=medium&amp;utm_medium=referral">Maik Jonietz</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Syntactically Awesome Style Sheets</h3><p>To style websites, we use a technology called CSS, this can get complex very quickly. The more features a site gets, the more complex the stylesheets generally get.</p><h4>Pre-compiler</h4><p>A solution to the mess that CSS can become is Sass, it’s a pre-compiler and is eventually compiled to raw CSS. Sass code is not understood by browsers and should be compiled and shipped to the users’ browser.</p><p>The Sass compiler is run as part of the static site generation process and reaches the user as plain-old CSS, essentially Sass just makes style-sheets easier to maintain.</p><h3>Summary</h3><ul><li><a href="https://ghost.org/">Ghost</a> provides an easy to use Web (and Desktop!) UI for managing content</li><li><a href="https://sass-lang.com/">Sass</a> helps us build maintainable style sheets</li><li><a href="https://webpack.js.org/">Webpack</a> bundles assets together</li><li><a href="https://gatsbyjs.org/">Gatsby</a> pulls content down from Ghost’s API</li><li>Hosting is made easier as the end result is just HTML, CSS &amp; JS.</li></ul><p><a href="https://github.com/TryGhost/gatsby-starter-ghost">https://github.com/TryGhost/gatsby-starter-ghost</a><br><a href="https://github.com/duskload/react-device-detect">https://github.com/duskload/react-device-detect</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f07f390849f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/get-chip/chips-brand-new-website-7f07f390849f">Chip’s brand new website</a> was originally published in <a href="https://medium.com/get-chip">Chip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chip’s growth |“A story of product and brand”]]></title>
            <link>https://medium.com/get-chip/chips-growth-a-story-of-product-and-brand-9b55268eda3c?source=rss----52f466a2d2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/9b55268eda3c</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Alex Latham]]></dc:creator>
            <pubDate>Thu, 04 Apr 2019 10:31:55 GMT</pubDate>
            <atom:updated>2019-04-04T10:34:34.188Z</atom:updated>
            <content:encoded><![CDATA[<h4>How focusing on customer experience is the key to rocketing growth</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EnjcSFKCEHi4yqHu-ufcFQ.jpeg" /></figure><p>At Chip, we believe in one central growth channel, and it means everything; our customers’ experience.</p><p>This may sound odd, fluffy, and completely unrelated to growth, but it’s central to how we grow our user base. We believe that by giving our customers a truly amazing experience, we will grow… and (not to blow our own trumpet) it seems to be working quite well.</p><p>There are two main factors that affect customers’ experience, but we’ll get into that in a bit. This article will fundamentally discuss how we use a customer’s experience to grow our user base, and grow it fast.</p><h3><strong>“Sounds like fluff to me”</strong></h3><p>Well, it is a bit, and that’s why we use a metric to measure our customer love.</p><p>We use something called <a href="https://www.medallia.com/net-promoter-score/">Net Promoter Score</a> (NPS) to measure how much our customers like our product. NPS asks customers a simple question “On a scale of 1–10 how likely are you to recommend Chip to a friend”.</p><p>If you’ve ever had a product ask you that, they’re trying to find out their NPS.</p><p>As an example of NPS, Tesla (reportedly) has a stupidly high NPS of 98. Monzo has an NPS of 68. Most British Banks have an NPS of <strong>-</strong>50.</p><h3><strong>Skip boring bit of how to calculate NPS if you want:</strong></h3><p>People who scored nine and ten are classed as promoters (very likely to tell their friends about your product), sevens and eights are neutral (they are discounted from the equation as they have indifference to the product), sixes and below are detractors (they actively have a negative experience and would not recommend the product).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mj3oLF5R_6bd4MbE_ICZ0Q.png" /><figcaption>If you’re too busy to read, this illustration explains NPS scores neatly.</figcaption></figure><p>NPS is calculated by a ratio of promoters to detractors. So Tesla have basically entirely tens (promoters), whereas Banks (not Monzo) have almost entirely detractors (sixes or less).</p><h3><strong>Stop skipping here:</strong></h3><p>So, now you’re an NPS pro what does it actually mean in relation to growth? Well it simply means we need to “make” nines and tens (Promoters).</p><p>Promoters love your product so much that they would recommend it to anyone. Their experience with your product is so great that they would 10/10 recommend it to a friend.</p><p>Now, the job ain’t done there (we need to actually get them telling people), but it’s 50% of the challenge.</p><h3><strong>“How do we make 9s &amp; 10s?”</strong></h3><p>Making a great NPS score comes down to two things:</p><ul><li>The Product</li><li>The Brand. (<em>Think back to Tesla whilst reading this section</em>):</li></ul><h3><strong>The Product</strong></h3><p>It’s really not easy to make an NPS groundbreaking product. A wise man (from Transferwise) once said “your product needs to be ten times better than the status quo to move NPS score” and that’s probably the easiest way of thinking about it.</p><p>Whatever your building needs to be ten times better than the other thing out there — and then you’ll rocket that NPS. Forget the colour of the buttons. Focus on what will make your product ten times better than what customers are using now.</p><p>We believe the status quo of ‘saving money’ is terrible. People have no way of doing it, returns are dreadful, banks have terrible UX… so that’s where we start.</p><p>How can we build the “best savings account in the world?”. A savings account that helps you save, gets you great returns &amp; has a good UX. We’re not their yet — but we’re on that journey. And that’s how we’re raising our <em>Product NPS.</em></p><h3><strong>The Brand</strong></h3><p>The second piece of the puzzle is the<strong><em> </em></strong>brand. This is generally easier than the product section (but I am a marketer 🤓). The brand is everything else around your product, the halo above it, the temple it sits in.</p><p>What tone do you want your customers to have when they think of your business? Is it exclusive? Lifestyle? Functional? (Think of Tesla). You need a brand that is clear, bold, and (most importantly) honest.</p><p>At Chip we have two main focuses with the brand. Firstly, we’re an “antibank”. We don’t talk like a bank, we don’t talk like we’re in finance. We are the polar opposite of that.</p><p>We use emojis, we use gifs/memes, and we generally don’t take ourselves too seriously. But, we have heart in what we do and we really care. I’ll do a separate article about Chip’s values but there are eight of them. We make sure they all shine through through the words we write, and the images we use.</p><p>The second element of our brand is the fact<strong> </strong>we’re a startup. We’re on a journey to “build the best savings account in the world” and we embrace that journey.</p><p>We want to take our users on that journey with us! This was amplified by our decision to run our two crowdfunds (in 2018 we ran <a href="https://www.bankingtech.com/2018/11/uk-savings-app-chip-notches-up-4m-funding/">the biggest crowdraise in UK history</a>).</p><p>At the end of the day we’re building Chip for you<em>, </em>it seems only fair that you build it with us too. The amplification of the startup life within our brand enables Chip to have a greater personality, greater character and greater passion. It enables us to talk to our customers on a human level and get them bought into our journey.</p><h3><strong>“So tangibly what the hell does this actually mean?”</strong></h3><p>Well, every decision we make centres around “Will this turn a customer into a 9 or 10?”.</p><ul><li>How can the app deliver an experience that will turn someone into a 10?</li><li>How does customer service deliver an experience turning someone into a 10?</li><li>How does that blog post turn someone into a 10?</li><li>How does that event we run turn someone into a 10?</li></ul><p>You get the picture, we’re pretty obsessed. But, that question is everything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*1fNh3rluYN7IkqsnWAbJsA.gif" /><figcaption>“This means EVERYTHING!!!!” — Ross Kemp</figcaption></figure><h3><strong>“So, you have a lot of 9&#39;s and 10’s. What now?”</strong></h3><p>Well centring on nines and tens lowers churn and encourages growth. So now what? Well remember above I said:</p><blockquote>“Now, the job ain’t done there (we need to actually get them telling people) but it’s 50% of the challenge.”</blockquote><p>Well, the other 50% is when we go ahead and “encourage”. I’ll write a follow-up article about how we do this — but… [spoiler]… it’s viral loops.</p><p>Stay tuned until next time where i’ll write about viral loops. Maybe I’ll do another article about specific things that move and shake NPS — comment if you want to see that!</p><p>But until then ✌. Alex</p><p>Email me at: <a href="/service/mailto: alex@getchip.uk">alex@getchip.uk</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b55268eda3c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/get-chip/chips-growth-a-story-of-product-and-brand-9b55268eda3c">Chip’s growth |“A story of product and brand”</a> was originally published in <a href="https://medium.com/get-chip">Chip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our first ever hackathon!]]></title>
            <link>https://medium.com/get-chip/our-first-ever-hackathon-aa2407ac8c1e?source=rss----52f466a2d2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/aa2407ac8c1e</guid>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[ifttt]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Tom Martin]]></dc:creator>
            <pubDate>Mon, 04 Mar 2019 10:39:28 GMT</pubDate>
            <atom:updated>2019-03-05T09:22:18.131Z</atom:updated>
            <content:encoded><![CDATA[<h4>Coming up with a feasible new product in a day… it’s easy when you try.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zcDrAria02Yxwv8l6Xu3cA.jpeg" /></figure><p>Hackathons are that great heady mixture of team-building, blueskies thinking (yes I used <em>that</em> word, I’m about to use ‘lean and agile’ below, so steel yourself) and frenetic hacking together products before the deadline.</p><p>Some great things have come out of hackathons, like the Facebook ‘like’ button and ‘timeline’.</p><p>And if done properly they can involve the skill sets of everyone in the company, and not just the tech and product teams. This makes them a great way to get everyone stuck in and thinking in lean and agile methodology terms.</p><h3><strong>Chip’s first ever hackathon task</strong></h3><p>Leveraging Chip’s customer’s bank transaction data, build a feature that customers would desire enough to pay for.</p><p>It must be commercially viable, technically feasible, and scalable for long term growth.</p><ul><li>MVP prototype within the Chip 2.0 ecosystem.</li><li>Landing page hosted on Squarespace asking for signups.</li><li>Fake press release to TechCrunch</li><li>Calculations showing commercial scalability &amp; feasibility.</li></ul><p>Each group was assigned an expert to cover tech, design, marketing, data, and commercial to try and build and market the product</p><p>We started at 2pm and powered through till 10pm, fuelled by pizza and beer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GkPqlOX0NLBMV49AwO4IRw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lv1bS8nn51JMyjYDL6Yfjw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9GmC4bVmeEoM8Tk2-6Hk9g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9grX2lZU2N3dFUQ4XMoHqA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XNn32-k6yE03RnQTyDy1vg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TAPsnXpJqrNOtD5FCjr8_w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GURbHfeHZc7tYwlPNHx2tg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YSk7VfeRe3FFiFIYrKEPrw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c03NUWCV_FrLBJhh9S2o5A.jpeg" /></figure><p>When the deadline bell tolled at the end of the day, we presented our ideas and demonstrated our prototypes back to everyone and voted on what was the best idea.</p><h3>Group one (Team Fish &amp; Chips)— ‘Winning Wednesdays’ quiz</h3><p>Group one decided that a quiz was the best way to hit the hackathon brief.</p><p>The new feature gives Chip users the chance to win back the value of one of their transactions made in the past month up to the value of £100. But there would be entrance fee of 50p.</p><p>The quiz would pop up via a push notification every Wednesday (hence the name).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*K5t0Oap-3akJvLGjjGq-NA.gif" /></figure><p>The rationale was to get people to think more about their budgeting in an engaging way.</p><p><strong>Creating the questions</strong></p><p>The first step was to draft up some questions using three parameters:</p><ul><li>What was spent</li><li>Where it was spent</li><li>When it was spent</li></ul><p>There was as much science as art involved. The balance had to be struck between making the questions difficult enough that the quiz could generate revenue, but also easy enough to be fun and ensure there were plenty of winners.</p><p><strong>Designing a UI</strong></p><p>A UI was knocked together on <a href="https://www.sketchapp.com/">Sketch</a> in record time.</p><p>It had four stages, some light animation work and was but into a prototype for viewing.</p><p><strong>Building the quiz</strong></p><p>Chip’s newest iOS dev (strictly speaking he still hadn’t started) then set about attempting to build the quiz with a very limited knowledge of Chip’s codebase.</p><p>The hack was built on the technologies consistent with Chip 2.0 front-end, that’s a server-driven UI written in Swift backed by a reactive MVVM architecture.</p><h3>Group two (Team Chip &amp; Pin)— IFTTT integration</h3><p>Group two looked at integrating with the <a href="https://ifttt.com/">‘If This Then That’ (IFTTT)</a> platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*SAOqeU5zR0f-X1jSJ_Lc0g.gif" /></figure><p>It would enable Chip users to create IFTTT Applets, which perform pre-defined actions based on specified triggers.</p><p>One use-case is encouraging users to save more money through personalised incentives. For example you could say, “Every time I walk to work, save my tube fare in Chip.”</p><p>Using location data, the method of travel to work would be recognised. Once this happens, and the data shows the user has walked, it would trigger the action. The £4.50 tube fare a user has not spent will be moved straight into their Chip savings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*MjCxU2O5DLuP8mIaXC97vg.gif" /></figure><p>Aside from incentivising a user to save more, the versatility of IFTTT means users can have fun with the triggers.</p><p>Depending on who a user supports, the trigger “every time my team scores, save £1 to celebrate” could help someone save lots of money, or not very much (depending on who they support).</p><p>Once the connection is set up, users can create their own Applets around their life. Once created, the Applet will be reviewed and confirmed by Chip and the magic behind the screen will activate the trigger.</p><h3>And the winner was…</h3><p>Despite the fact that Team Fish&amp;Chips had a much more complete prototype and commercial model, the votes came in and team Chip&amp;Pin’s IFTTT integration won the day.</p><p>The general consensus was whilst the Winning Wednesday quiz was fun and could theoretically generate more revenue, IFTTT integration just felt more like it aligned with our values.</p><p>We’ve even decided to take it forward and build it into a premium product (along with several other features) that we’ll be launching sometime in 2019.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*NNFV5kCAwJ9O52q5pXFK0w.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa2407ac8c1e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/get-chip/our-first-ever-hackathon-aa2407ac8c1e">Our first ever hackathon!</a> was originally published in <a href="https://medium.com/get-chip">Chip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[‘all Monitor]]></title>
            <link>https://medium.com/get-chip/all-monitor-8b6f7c6e1f9d?source=rss----52f466a2d2a---4</link>
            <guid isPermaLink="false">https://medium.com/p/8b6f7c6e1f9d</guid>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[data-monitoring]]></category>
            <dc:creator><![CDATA[Alan Cole]]></dc:creator>
            <pubDate>Mon, 04 Mar 2019 10:36:54 GMT</pubDate>
            <atom:updated>2019-03-04T17:20:19.489Z</atom:updated>
            <content:encoded><![CDATA[<h4>How we learned to stop worrying and love data monitoring.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4lpjtV3Hf0WpvvqJ_GxQkQ.jpeg" /></figure><p>“It is a capital mistake to theorise before one has data” or so said Sherlock Holmes in ‘a Study in Scarlet’, and who are we to disagree with a man in a deer stalker?</p><p>Here at Chip we collect a ton of the stuff, from the essential super secret, super secure, account information of our customers to the less sensitive and more mundane. Like how many changes we’ve made to the code that runs our site (a little over seven thousand, or about 40 times a week, because I know you were wondering) this data flows into our databases and is available at the touch of a button (apart from the secret stuff) to our developers.</p><p>Data on demand was great, it allowed us to build a service that helps tens of thousand of our customers save, but there was a problem, a big one. We had to know what we’re looking to find it, spotting mistakes was left to hunches or feelings, and whilst we’ve got pretty good instincts, that wasn’t good enough.</p><p>Enter monitoring.</p><p>Of course we had <em>some</em> monitoring, we knew generally what was happening at any given moment and we <strong>always</strong> knew what was happening with our customers’ money, but spotting problems for our customers needs more than that. So we switched to a new approach that can most readily be described as ‘it’s a number, so let’s make it a metric.’</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fl0HlW5vnelAWvmnO8%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fl0HlW5vnelAWvmnO8%2Fsource.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fl0HlW5vnelAWvmnO8%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="217" frameborder="0" scrolling="no"><a href="https://medium.com/media/adc059448697c0f987d6f5e1bf23bf40/href">https://medium.com/media/adc059448697c0f987d6f5e1bf23bf40/href</a></iframe><h3>Monitor All The Things</h3><p>So what did we actually change, and how is that helping us? Firstly, we decided to give the Chip community a little more information about the state and performance of our service by launching a status website <a href="https://status.getchip.tech/">status.getchip.tech</a> where our team can feedback to customers in real time, even if unexpected events disrupt things.</p><p>Our main change was a shift to a “Data Warehouse” (we chose Google BigQuery) which allows us to aggregate all of our data, from lots of sources. We can take it, secure it, anonymise it, and write queries on it for thousands of different data points:</p><ul><li><em>How many saves were there in the last hour?</em></li><li><em>How many customers have active bank connections?</em></li><li><em>How many have failed ones?</em></li><li><em>How many people opened the app in the last hour?</em></li><li><em>How many customers withdrew money in the last 24 hours?</em></li></ul><p>We collected a host of such questions from relevant people in the business then we built the queries for each, allowing us to display those numbers on a dashboard for all our staff (we’ve written our own internal tool, called Dashi to display all this data in a usable and relevant way). This gives every member of the team the opportunity to spot abnormalities.</p><p>We recently invested in a set of shiny new TVs to be placed around our office upon which we’ll have these realtime dashboards of core metrics. If someone in our marketing teams knows the answer to the question ‘How many app downloads were there in the last 24 hours?’ is normally ‘50’<em> </em>but spots that today it’s ‘30’ they can action a plan to find out why, without having to get all the devs involved.</p><p>The information passively gives everyone the power to ensure our customers experience of the app is the best it can be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cdaxb46UWI3G-5TkOqYRVg.png" /><figcaption>A look at our customer status website, keeping our customers informed.</figcaption></figure><h3>What’s Next?</h3><p>The new monitoring drive here at chip is just the start. As we grow these stats and metrics out, we’ll be well placed to start saying exactly what a ‘normal’ system looks like. This will allow us to extend our automatic monitoring and alerts, so not only can our team members spot problems before they happen but so can our systems themselves. Computers watching computers, ‘Statception’ if you will.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b6f7c6e1f9d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/get-chip/all-monitor-8b6f7c6e1f9d">‘all Monitor</a> was originally published in <a href="https://medium.com/get-chip">Chip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>