<?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 Chris Sloey on Medium]]></title>
        <description><![CDATA[Stories by Chris Sloey on Medium]]></description>
        <link>https://medium.com/@chrisasaur?source=rss-2938b0ac6262------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*scWsO8QnPb_-NAh4.png</url>
            <title>Stories by Chris Sloey on Medium</title>
            <link>https://medium.com/@chrisasaur?source=rss-2938b0ac6262------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:39:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chrisasaur/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[Testing React Native: Working with Dependencies]]></title>
            <link>https://medium.com/add-jam/testing-react-native-working-with-dependencies-2e9e3e0c959b?source=rss-2938b0ac6262------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e9e3e0c959b</guid>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Chris Sloey]]></dc:creator>
            <pubDate>Fri, 15 Apr 2016 13:42:49 GMT</pubDate>
            <atom:updated>2016-04-15T14:23:51.950Z</atom:updated>
            <content:encoded><![CDATA[<p>After <a href="https://medium.com/add-jam/testing-react-native-with-mocha-and-enzyme-6b77cd9e52a1">setting up testing</a> for the React Native project we’re working on, the first problem I faced was testing my code that interacts with dependencies. In a lot of cases I don’t want those dependencies to be called (e.g. to avoid network calls or other side effects) but I also want to verify they would be called correctly.</p><p>This ended up being pretty straightforward to do.</p><blockquote>If you don’t have testing set up already with React Native, <a href="https://medium.com/add-jam/testing-react-native-with-mocha-and-enzyme-6b77cd9e52a1">my previous post</a> on getting this working should be useful.</blockquote><h4>Overriding Dependencies</h4><p>My testing setup uses Mocha and Chai, with Enzyme for testing my components. For testing code which interacts with dependencies, I settled on using proxyquire and sinon.</p><p>Proxyquire allows us to override our dependencies with anything we want. If our dependency exports a function <em>foo</em>, we can tell it to replace that dependency with an object that has it’s own function <em>foo</em>. This is where sinon comes in useful — sinon allows us to create <em>mocks</em>, <em>stubs</em> and <em>spies</em>. Using these, we can easily replace dependencies with <em>stubs</em> that could return the data we expect or use <em>spies</em> to check not only that those functions are called, but that they are called with the correct set of arguments or invoked the right amount of times.</p><h4>An Example</h4><p>I started looking into all of this for a piece of my code which uses Google Analytics, via <a href="https://github.com/idehub/react-native-google-analytics-bridge">react-native-google-analytics-bridge</a>. I sometimes wrap dependencies like this so that they can be easily switched out — here’s a very simplified example that we can write some tests for.</p><p><em>Analytics.js</em></p><pre>import GA from &#39;react-native-google-analytics-bridge&#39;;<br><br>export default class Analytics {<br>  constructor(trackerId) {<br>    GA.setTrackerId(trackerId);<br>  }<br>  <br>  trackScreenView(pageName) {<br>    GA.trackScreenView(pageName);<br>  }<br>}</pre><p>There’s not much going on here. All I want to do is verify that we’re setting things up with the correct tracker ID and that <em>trackScreenView</em> correctly calls the dependency.</p><p>To write these tests we’ll use <em>proxyquire</em> to modify the Google Analytics import, replacing each of the functions we use with a <em>sinon</em> spy that we can inspect later.</p><p>We’ll set up these spies before each test.</p><p><em>Analytics.spec.js</em></p><pre>import React from &#39;react-native&#39;;<br>import sinon from &#39;sinon&#39;;<br>import proxyquire from &#39;proxyquire&#39;;<br><br>describe(&#39;Analytics&#39;, () =&gt; {<br>  let Analytics, trackerId, screenViewSpy;<br><br>  beforeEach(() =&gt; {<br>    trackerIdSpy = sinon.spy();<br>    screenViewSpy = sinon.spy();<br>    <br>    Analytics = proxyquire<br>                  .noCallThru()<br>                  .load(&#39;../Analytics&#39;, {<br>                    &#39;react-native-google-analytics-bridge&#39;: {<br>                      setTrackerId: trackIdSpy,<br>                      trackScreenView: pageViewSpy<br>                    }<br>                  }).default;<br>  });<br>  <br>  // Tests here<br>  <br>});</pre><p>The spies are being initialised before each test is run so that we have some fresh state to work with. I don’t want <em>any</em> calls to go to the dependency, so I’ve used proxyquire’s <em>noCallThru</em> to prevent anything that’s not been overridden from getting called.</p><p>The most important part is the second argument to <em>load</em>, where I pass in an object specifying the imports I want to override — this is where we can inject our spies.</p><blockquote><em>The </em>.default<em> on the require is because the Analytics class is exported with </em>export default class Analytics<em>. If I was using </em>module.exports = class Analytics <em>then I wouldn’t have to do this. It feels messy but I’m not sure if there’s a way around it while still using </em>export default<em>.</em></blockquote><p>With that set up, we can get to the good part — some tests!</p><pre>it(&#39;should set up GoogleAnalytics with the correct ID&#39;, () =&gt; {<br>  const trackerId = &quot;UA-12345678-9&quot;;<br>  const instance = new Analytics(trackerId);<br>  expect(trackIdSpy.calledOnce).to.be.true;<br>  expect(trackIdSpy.calledWith(trackerId)).to.be.true;<br>});<br>  <br>it(&#39;should track screen views&#39;, () =&gt; {<br>  const screenName = &quot;Just Add Jam&quot;;<br>  const instance = new Analytics(trackerId);<br>  expect(screenViewSpy.calledOnce).to.be.true;<br>  expect(screenViewSpy.calledWith(screenName)).to.be.true;<br>});</pre><p>Easy!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*kaYAbfY-p_y9l4uCRmIR1A.gif" /></figure><p><em>We’re working on a React Native eBook — want a copy? sign up for updates on </em><a href="https://addjam.com/"><em>our website</em></a><em>.</em></p><p><a href="https://addjam.com/">Add Jam</a> are creating useful software products in the heart of Glasgow. If you’re ever nearby, feel free to pop into our office for a coffee or a game of pool. If you’re looking for a team to build your product, <a href="https://addjam.com/contact">get in touch</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e9e3e0c959b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/add-jam/testing-react-native-working-with-dependencies-2e9e3e0c959b">Testing React Native: Working with Dependencies</a> was originally published in <a href="https://medium.com/add-jam">Add Jam.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing React Native with Mocha and Enzyme]]></title>
            <link>https://medium.com/add-jam/testing-react-native-with-mocha-and-enzyme-6b77cd9e52a1?source=rss-2938b0ac6262------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b77cd9e52a1</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Chris Sloey]]></dc:creator>
            <pubDate>Fri, 01 Apr 2016 14:54:11 GMT</pubDate>
            <atom:updated>2016-06-16T09:01:02.559Z</atom:updated>
            <content:encoded><![CDATA[<p>I spent some time yesterday setting up testing in a React Native app and it was surprisingly tricky.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*r3XzMnjRWH0Cvtf408Ahsg.gif" /></figure><p>I wanted to use <a href="http://airbnb.io/enzyme/">Enzyme</a> with it’s really simple API for testing my components and Mocha for running the tests. This setup seems to be fairly popular but none of the guides I found worked well with the latest version of React Native (0.25 as of last edit). In the end what worked for me was cobbled together from some blog posts and a whole bunch of GitHub issues.</p><blockquote>Already got testing set up? I’ve wrote another post on how to test code which has dependencies <a href="https://blog.addjam.com/testing-react-native-working-with-dependencies-2e9e3e0c959b#.u075m1frc">here</a></blockquote><h4>The packages we need</h4><p>To get this set up, these are the packages we’ll install.</p><ul><li><a href="https://babeljs.io/">Babel</a> for transpiling our javascript</li><li><a href="https://mochajs.org/">Mocha</a> for running the tests</li><li><a href="http://chaijs.com/">Chai</a> for our assertions</li><li><a href="http://sinonjs.org/">Sinon</a> for spies, stubs and mocks</li><li><a href="http://airbnb.io/enzyme/">Enzyme</a> for nice component tests</li></ul><p>To get enzyme to work, we also need react-dom as well as <a href="https://github.com/lelandrichardson/react-native-mock">react-native-mock</a>, which gives us an almost fully mocked version of React Native.</p><pre>npm i --save-dev babel-core babel-preset-react-native babel-preset-airbnb mocha chai chai-enzyme enzyme@2.2 react-native-mock react-dom sinon</pre><p>There are plenty of other useful packages too, but this is a good foundation.</p><blockquote>Edited to set enzyme version to 2.2. I was getting errors on React Native 0.25 using the RN mocks after enzyme 2.3 was released. YMMV.</blockquote><h4>The tricky bit</h4><p>Great! We have the packages we need. It doesn’t work yet though.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/345/1*MxEKZTKKL4lZkSev_zgvDQ.gif" /></figure><p>There’s ES6 code that isn’t being transpiled and we need to make sure the react-native mocks are being used.</p><p>To get that working, we can create a simple setup script that will run before the tests. This will ensure babel transpiles our code, the react-native module, and some of our other dependencies. You’ll also need a <em>.babelrc</em> file in the root of the project, like this:</p><pre>{<br>  &quot;presets&quot;: [<br>    &quot;react-native&quot;<br>  ]<br>}</pre><p>Next, create the setup file. I put this at <em>test/setup.js</em></p><pre>import fs from &#39;fs&#39;;<br>import path from &#39;path&#39;;<br>import register from &#39;babel-core/register&#39;;<br>import chai from &#39;chai&#39;;<br>import chaiEnzyme from &#39;chai-enzyme&#39;;</pre><pre>// Ignore all node_modules except these<br>const modulesToCompile = [<br>  &#39;react-native&#39;,<br>  &#39;apsl-react-native-button&#39;,<br>  &#39;react-native-router-flux&#39;,<br>  &#39;react-native-tabs&#39;,<br>  &#39;react-native-vector-icons&#39;,<br>  &#39;react-native-mock&#39;,<br>  &#39;react-native-parallax-scroll-view&#39;,<br>  &#39;react-native-simple-store&#39;<br>].map((moduleName) =&gt; new RegExp(`/node_modules/${moduleName}`));</pre><pre>const rcPath = path.join(__dirname, &#39;..&#39;, &#39;.babelrc&#39;);<br>const source = fs.readFileSync(rcPath).toString();<br>const config = JSON.parse(source);<br>config.ignore = function(filename) {<br>  if (!(/\/node_modules\//).test(filename)) {<br>    return false;<br>  } else {<br>    const matches = modulesToCompile.filter((regex) =&gt; regex.test(filename));<br>    const shouldIgnore = matches.length === 0;<br>    return shouldIgnore;<br>  }<br>}</pre><pre>register(config);</pre><pre>// Setup globals / chai<br>global.__DEV__ = true;<br>global.expect = chai.expect;<br>chai.use(chaiEnzyme());</pre><pre>// Setup mocks<br>require(&#39;react-native-mock/mock&#39;);<br>const React = require(&#39;react-native&#39;)<br>React.NavigationExperimental = {<br>  AnimatedView: React.View<br>};</pre><p>There’s pretty much 3 parts to this</p><ul><li>Make sure babel doesn’t ignore anything outside of node_modules or any of the modules specified in modulesToCompile.</li><li>Set up some globals like ‘expect’ so that it doesn’t have to be imported everywhere</li><li>Enable react-native-mock (I also mocked a small part of NavigationExperimental here as it’s <a href="https://github.com/lelandrichardson/react-native-mock/issues/22">missing from</a> react-native-mock right now)</li></ul><p>You’ll probably need to play around with the modules that are specified in <em>modulesToCompile</em> so that it matches your own needs. If you start getting errors like “unrecognised token”, chances are you’re not transpiling something.</p><h4>Writing some tests</h4><p>Finally, we can get to the good stuff. Let’s write some tests! We’ll use this really basic AngryButton component as an example.</p><blockquote><em>NB I’ve put a project with this component in a GitHub repo, if you want to see everything together then check it out </em><a href="https://github.com/AddJam/react-native-mocha-enzyme-example"><em>here</em></a><em>.</em></blockquote><pre>class AngryButton extends Component {<br>  render() {<br>    const { text, onPress } = this.props;<br>    return (<br>      &lt;TouchableHighlight style={styles.button} onPress={onPress}&gt;<br>        &lt;Text style={styles.text}&gt;{text.toUpperCase()}&lt;/Text&gt;<br>      &lt;/TouchableHighlight&gt;<br>    );<br>  }<br>}</pre><p>The AngryButton component takes two props; some text that it will make ANGRY, and a function to call when the button is pressed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*hBjhDmYNWa12QcuazxkH2w.gif" /><figcaption>Inspiration for our button</figcaption></figure><p>To start we’ll just test that it actually renders — if this works then we know we’ve got things set up ok.</p><pre>import React, { Text, TouchableHighlight } from &quot;react-native&quot;;<br>import { shallow } from &quot;enzyme&quot;;<br>import AngryButton from &quot;../AngryButton&quot;;</pre><pre>describe(&quot;&lt;AngryButton/&gt;&quot;, () =&gt; {<br>  it(&quot;should render&quot;, () =&gt; {<br>    const button = shallow(&lt;AngryButton text=&quot;bananas&quot; /&gt;);<br>    expect(button.contains(TouchableHighlight)).to.equal(true);<br>    expect(button.contains(Text)).to.equal(true);<br>  });<br>})</pre><p>Although this is basic stuff, it also shows how simple enzyme is — it makes what the test is doing obvious.</p><p>I like my tests to live near what they’re testing, so I have them in a <em>__specs__</em> folder next to the component but you can put them wherever you want. For this example, it’s at <em>src/components/__specs__/AngryButton.spec.js</em>.</p><p>To run the test with mocha, we need to tell it to use babel and to require our setup file before the test is run. After that we just need to tell it where the tests are.</p><pre>mocha --require test/setup.js --compilers js:babel-core/register src/**/__specs__/*.spec.js</pre><p>If that worked, you should see the passing test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/322/1*xCQmTzYQ7Swb5exzCzsEEg.png" /></figure><p>Now that we have it working, we can add a couple more test cases — let’s import sinon so that we can test button presses work.</p><pre>import sinon from &quot;sinon&quot;;</pre><p>and then add the test cases</p><pre>  it(&quot;should capitalise text&quot;, () =&gt; {<br>    const button = shallow(&lt;AngryButton text=&quot;bananas&quot; /&gt;);<br>    expect(button.find(Text).props().children).to.equal(&quot;BANANAS&quot;);<br>  });</pre><pre>  it(&quot;should handle button presses&quot;, () =&gt; {<br>    const onPress = sinon.spy();<br>    const button = shallow(&lt;AngryButton text=&quot;yo&quot; onPress={onPress}/&gt;);<br>    button.simulate(&#39;press&#39;);<br>    expect(onPress.calledOnce).to.equal(true);<br>  });</pre><p>Now we’ve validated the text is being uppercased and that the onPress event gets fired when the button is pressed. Again, really simple and readable.</p><h4>Tidying up</h4><p>We could leave it there, but let’s tidy things up a little. Mocha lets us take the options we always pass to it and put them in an options file. I’ve put these in <em>test/mocha.opts</em></p><pre>--require test/setup.js<br>--compilers js:babel-core/register</pre><p>Let’s add a test script to our <em>package.json</em> too</p><pre>...<br>&quot;scripts&quot;: {<br>  &quot;test&quot;: &quot;mocha --opts test/mocha.opts src/**/__specs__/*.spec.js&quot;<br>}<br>...</pre><p>Now to run our tests we just run “<em>npm test</em>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/331/1*ZZFtKUx4rvKCNh5QUxDeOQ.gif" /></figure><p>You can check out all of this together at the example <a href="https://github.com/AddJam/react-native-mocha-enzyme-example">Github repo</a>. It’s worth looking into each of the packages to get more of a feel for what they can do. It’s also really useful to have a look at how open source React Native packages do their testing — react-native-simple-auth is a <a href="https://github.com/adamjmcgrath/react-native-simple-auth/blob/917a06ff450bfff4adce772af72d29332aa1e1d9/test/simpleauthclient.test.js">good example</a>.</p><p>Have fun testing 😄.</p><p><em>We’re working on a React Native eBook — want a copy? </em><a href="https://addjam.com/resources/react/"><em>sign up</em></a><em> for updates on our website.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b77cd9e52a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/add-jam/testing-react-native-with-mocha-and-enzyme-6b77cd9e52a1">Testing React Native with Mocha and Enzyme</a> was originally published in <a href="https://medium.com/add-jam">Add Jam.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gems that Rock]]></title>
            <link>https://medium.com/add-jam/gems-that-rock-8f7ac8a51d4e?source=rss-2938b0ac6262------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f7ac8a51d4e</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[ruby]]></category>
            <dc:creator><![CDATA[Chris Sloey]]></dc:creator>
            <pubDate>Sat, 31 Jan 2015 00:00:00 GMT</pubDate>
            <atom:updated>2016-02-03T16:20:53.568Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the past year we’ve started many new rails projects. Each time we would experiment with different testing frameworks or gems to improve our development workflow, eventually settling on a core set that we use 90% of the time.</p><p>We recently decided to build on this by creating a Rails template tailored to our needs (cleverly named the ‘Jam Jar’). Using this template means that new rails projects will start tailored to our workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*jytctNgbz2u2ggDF.png" /></figure><p>The Jam Jar is still very much a work in progress and we’ll be talking about it more in a future post. Below are some of the gems we love the most. I skipped out the more obvious ones like rspec or factory_girls but you can have a look at the full list on <a href="https://github.com/AddJam/jamjar">Github</a>. It would be really interesting to hear which gems you think we missed or disagree with, we’re <a href="https://twitter.com/add_jam">@add_jam</a> on Twitter.</p><h4>Annotate</h4><p><a href="https://github.com/ctran/annotate_models">Github</a></p><p>Annotate has become a must in all of our Rails projects. Running annotate in your rails project will add a summary of the schema at the top of the file. It can also be used to annotate routes, factory_girl factories, fixtures and a bunch more.</p><p>The example below from the github readme demonstrates it’s usefulness.</p><pre># == Schema Info<br>#<br># Table name: line_items<br>#<br># id :integer(11) not null, primary key<br># quantity :integer(11) not null<br># product_id :integer(11) not null <br># unit_price :float <br># order_id :integer(11) <br># class LineItem &lt; ActiveRecord::Base</pre><h4>Quiet Assets</h4><p><a href="https://github.com/evrone/quiet_assets">Github</a></p><p>Another nice gem for development, quiet_assets mutes all of the log messages produced by the Rails asset pipeline so that you can see the ones that matter most.</p><h4>Byebug</h4><p><a href="https://github.com/deivid-rodriguez/byebug">Github</a></p><p>This one is indispensable! Just put byebug anywhere in your code and you’ll get access to the REPL when execution reaches that line. Byebug is super easy to start using and supports all of the commands you’d expect like stepping over lines and into functions.</p><h4>Forgery</h4><p><a href="https://github.com/sevenwire/forgery">Github</a></p><p>I only came across this gem recently but it’s definitely one that should be useful to most projects. Forgery allows you to generate anything from placeholder lorem ipsum text to addresses information, locations and personal information. We’ve been combining it with factory_girls to generate test models and for seeding our development database with reasonable values.</p><h4>Timecop</h4><p><a href="https://github.com/travisjeffery/timecop">Github</a></p><p>This gem is great for easily testing areas of your code that are dependent on the time or date. Timecop allows you to move through time, accelerate time or freeze time by overriding the responses from Date, Time, and DateTime.</p><h4>Active Model Serializers</h4><p><a href="https://github.com/rails-api/active_model_serializers">Github</a></p><p>This is probably the most well known gem on the list but it’s worth pointing out anyway. AMS allows you to create serializers that specify which attributes and relations will be serialized. Say we have a model Person(name: string, email:string, age:integer) and the person has many Comments, our serializer could look like this:</p><pre>class PersonSerializer &lt; ActiveModel::Serializer<br>  attributes :name, :age<br>  has_many :comments<br>end</pre><p>Then in our controller when we do</p><pre>render json: @person</pre><p>The returned json would only have the specified fields, skipping others like created_at, updated_at, and email.</p><p>This is the simplest solution we’ve come across for serialization. It’s especially great if you’re working with Ember, which has built in support for the json output of AMS through the ActiveModelAdapter.</p><h4>What else should we use?</h4><p>What gems do you love that aren’t in the Jam Jar? Drop me <a href="/service/mailto:chris@addjam.com">an email</a> or <a href="http://twitter.com/chrisasaur">tweet me</a>.</p><p><em>Originally published at </em><a href="https://addjam.com/2015/01/31/gems-that-rock"><em>addjam.com</em></a><em> on January 31, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f7ac8a51d4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/add-jam/gems-that-rock-8f7ac8a51d4e">Gems that Rock</a> was originally published in <a href="https://medium.com/add-jam">Add Jam.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Year of Add Jam]]></title>
            <link>https://medium.com/add-jam/a-year-of-add-jam-1dd9e393a57b?source=rss-2938b0ac6262------2</link>
            <guid isPermaLink="false">https://medium.com/p/1dd9e393a57b</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[coworking]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Chris Sloey]]></dc:creator>
            <pubDate>Fri, 23 Jan 2015 00:00:00 GMT</pubDate>
            <atom:updated>2016-02-03T16:13:12.719Z</atom:updated>
            <content:encoded><![CDATA[<p>Going from full time employment to founding Add Jam, the past year has been amazing for Michael and I. This is our story.</p><h4>Starting Out</h4><p>At the end of 2013 and beginning of 2014, Michael and I were spending more and more of our time working on our own projects. We were both in full time employment; Michael at Strathclyde University and me at Kana. Our days became more and more of 9 to 5 at our jobs, 6:30 to late working on our own projects. Our own projects were what drove us, and while our jobs weren’t bad ones, they were getting in the way. We couldn’t spend enough time on our projects or on learning things relevant to what we love — creating mobile products.</p><p>We wanted to get to a point where we could be working on our own products full time, but we couldn’t just stop earning money. We didn’t want to look for investment or grants for a product, so the clear solution for us was in client work. Working on client projects creating mobile apps would let us spend our days on relevant learning, and wouldn’t tie us down to a full-time permanent job.</p><p>With this in mind, we started talking to Scott Sherwood about joining Glasgow’s Future City Project. They needed developers to work on Active Travel apps, and our project at the time was an intelligent travel guide for iOS we were calling Scout. The idea behind Scout was that you’d tell it where you’re travelling to and it would tell you what you need to know to prepare. We showed off Scout in our pitch to the Future City Project, and ultimately earned our first contract.</p><h4>Executing</h4><p>The Future City Project became our biggest project of 2014 and our main source of income. We created two products there; Glasgow Walking and Glasgow Cycling (you can read more about these on our <a href="https://addjam.com/client-case-studies/">Client Case Studies section</a>). These products each had a Ruby on Rails backend and native iOS and Android apps, but were more than just six code bases. We crafted the entire UX of the products as well as most of the UI. We learned a ton from this project, and applied that to everything else we worked on.</p><p>Throughout that project and the other client projects we picked up in 2014, we continued our drive towards earning money from our own products. We both strongly believe the products we create should be something we’re passioante about and something we need. If we create a product neither of us would use, how can we know it’s good? Our target niche became esports — an area I’m passionate about. I love to follow the League of Legends professional scene, so we started there.</p><p>We created the <a href="http://lolnewsletter.com/">League of Legends Newsletter</a> as an easy way to keep up with the game — we love newsletters like <a href="http://hackernewsletter.com/">Hacker Newsletter</a> and <a href="http://iosdevweekly.com/">iOS Dev Weekly</a> and I seen a need for something similar. The newsletter is growing consistently and is now at nearly 2000 subscribers.</p><p>We also created <a href="http://lol2048.com/">LoL2048</a>, a themed version of the open source 2048 game by Gabriele Cirulli that took up everyones time in March and April. LoL2048 quickly seen amazing success — we spent 30 minutes theming 2048 and were sitting on the edge of our seats for the rest of the day, peaking at over 7000 concurrent users within hours of posting on the League of Legends subreddit. The game has now been played 17.6 million times by 1.3 million people, and we’ve used it to feed the growth of our newsletter. One of the coolest parts of this was seeing pro players and hosts tweeting about it.</p><p>We’ve experimented with a number of other ways to grow the newsletter, some of which were successful and others not. This is representative of the whole year for Add Jam — we had successes, we made mistakes, we applied what we learned from those to the next product and improved drastically over the year. We weren’t perfect, but progressing was far more important than being afraid of failure.</p><h3>Another Year</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Pvk4olV4HI-q5XyN.jpg" /></figure><p>This year we move into our offices — Michael has been working on establishing a better tech community in Glasgow for years and the next step is the <a href="http://rookieoven.com/">RookieOven</a> co-working space pictured above. We’ll be moving there in just a couple of weeks with some amazing startups around us. Being surrounded by these startups will be a driving force to creating better products and learning more than ever.</p><p>Add Jam will keep working on client products, and keep moving towards earning more from our own products. Going forward we want to work with clients on products that excite us and give us the freedom we need to really show off our product development skills. We’d love to talk with you if you have a product we can work with you on.</p><p>Lastly, we’re keen to help others. We know how tough it is to get started and some of the challenges people face in their first year. If there’s any way we can help or anything you would like us to expand on in our blog then <a href="/service/mailto:yo@addjam.com">get in touch</a>.</p><p><em>Originally published at </em><a href="https://addjam.com/2015/01/23/a-year-of-addjam"><em>addjam.com</em></a><em> on January 23, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1dd9e393a57b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/add-jam/a-year-of-add-jam-1dd9e393a57b">A Year of Add Jam</a> was originally published in <a href="https://medium.com/add-jam">Add Jam.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>