Jekyll2022-03-15T07:56:49+00:00https://nanoreddit.com/blogg/feed.xmlNanoThis is the home of the Nano Blog. This is where new updates will be posted, technical explanations and more!Chirp Privacy Policy2018-09-01T06:39:00+00:002018-09-01T06:39:00+00:00https://nanoreddit.com/blogg/blogg/chirp/support/2018/09/01/chirp-support<p><strong>Chirp does not collect any information about you</strong>, it’s really that simple.</p>
<p>If anything, you should care more about <a href="https://twitter.com/privacy">Twitter’s Privacy Policy</a>, because that’s probaby more relevant.</p>
<p>Not only do I not care about how you use Chirp (aside from if you want a new feature or find a bug), but I simply wouldn’t have the resources to store your data even if I wanted to.</p>
<p>The End.</p>Chirp does not collect any information about you, it’s really that simple.Chirp Support2018-06-16T02:29:59+00:002018-06-16T02:29:59+00:00https://nanoreddit.com/blogg/blogg/chirp/support/2018/06/16/chirp-support<p>Sorry to hear Chirp isn’t working as you’d expect!</p>
<p>In order to get help, contact with me with (or all) of the following:</p>
<ul>
<li><a href="https://twitter.com/WillRBishop">Tweet at me</a></li>
<li><a href="https://www.reddit.com/message/compose?to=willrb&subject=Chirp%20Support">Message me on Reddit</a></li>
<li><a href="mailto:nano@willbish.com?subject=Chirp%20Support">Email me</a></li>
</ul>
<p>I’ve made many options available so no matter what service you use, you’ll be able to contact me!</p>Sorry to hear Chirp isn’t working as you’d expect!Welcome to Nano!⌚2018-04-18T02:30:00+00:002018-04-18T02:30:00+00:00https://nanoreddit.com/blogg/blogg/nano/release/2018/04/18/welcome-to-nano<p>Wow, what a <em>loooonnnnggg</em> time coming.</p>
<p>I’ve been working on Nano since before I even had an Apple Watch. Well… that’s not <em>that</em> long, I got my Apple Watch on December 25th, <a href="https://www.reddit.com/r/AppleWatch/comments/7m0zbt/got_an_s3_for_christmas_i_already_know_strapping/">the same day I teased Nano for the first time.</a>.</p>
<p>Nano has not been an easy journey and it hasn’t come without its dissapointing times. But throughtout the development of Nano, I’ve learnt so much and met so many amazing people, and I’d like to talk about some of that today.</p>
<h1 id="the-people">The People</h1>
<p>Wow, I did not expect to meet so many amazing people while developing Nano. As much as I’d like to list them all by name, I cannot do that on here (though, they are listed in the iOS app!). I would feel bad mentioning some people but not all, so I’ll keep this pseudo-anonymous. Without all these people, Nano would not be what it is today.</p>
<h3 id="the-discord-helper">The Discord Helper</h3>
<p>This person helped me to transform my Discord server from a boring ol’ chatroom to a server with lots of chat rooms, ranks, permissions, and more. But they did more than just help me on Discord, they were always willing to test bugs and put fourth new ideas. For that, I thank you.</p>
<h3 id="the-translators">The Translators</h3>
<p>At launch, Nano will be available in three languages, English, Turkish, and Danish. I want Nano to be able to be used by as many people as possible, and the testers using their own time to help translate Nano truly shows the quality of people I had to help me all along the way.</p>
<h3 id="the-reporters">The Reporters</h3>
<p>I have a bit of a love-hate relationship with these guys (many of which are also part of the translators or Discord groups). On the one hand, getting bug reports is great; It helps me make Nano as stable and feature-rich as can be. On the other hand, however, gee it’s annoying! Now don’t take me the wrong way, <strong>I am not annoyed at the reporters</strong>, I am annoyed at myself. Bugs are a testament to a developers skill, and no program is without bugs. But I spent countless nights (or very early mornings) fixing these bugs and neglecting my school work, 🤞🏻it pays off!.</p>
<h1 id="development">Development</h1>
<p>Well Apple sure didn’t make this easy, but why should they? I come from an iOS development background (despite never releasing an app), but WatchKit does <em>some</em> things better, and <em>some</em> things worse.</p>
<h2 id="the-good">The Good</h2>
<ul>
<li>Tables on WatchKit make a bit more sense for newcomers, but coming from an iOS background, they can be tough to start with. For example, on iOS you can set the number of rows a table has using the <code class="language-plaintext highlighter-rouge">numberOfRowsInSection</code> delegate method like so
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code> func tableView(_ tableView: UITableView, numberOfRowsInSection section: Int) -> Int {
return something.count
}
</code></pre></div> </div>
<p>However, on WatchKit, the number of rows is set like this</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code> table.setNumberOfRows(something.count, withRowType: "rowType")
</code></pre></div> </div>
<p>I actually prefer the second method, as it can be called from anywhere, but the consistency between iOS and watchOS is almost non-existant.</p>
</li>
</ul>
<h2 id="the-bad">The Bad</h2>
<p>Unfortunately, it’s a lot easier to find bad things than it is to find good things.</p>
<ul>
<li>
<p>Storyboard <strong>only</strong>; When you’re developing for iOS you have a couple of options to build your User Interface, the two most common are <em>Storyboards</em>, and <em>Programatic-UI</em>.</p>
<p>The difference there is simple, with a <em>Storyboard</em> you can design your UI with a drag-and-drop interface, and connect your code to it. This method is incredible useful for beginners (or even experienced devs), but it has its own problems (such as working in a team, <em>Storyboards</em> can become bloated and prone to merge errors). A <em>Programatic-UI</em> works by building the entire UI in code, a favorite amongst iOS veterans.</p>
<p>But here’s the problem, there is <strong>no</strong> option when developing for watchOS, Apple forced you to use <em>Storyboards</em>. Which means that as a developer, if I want to make my Reddit client look good, some trickery has to be at play.</p>
</li>
<li>
<p>Poor image-support; Now this is an odd one, and one that I’ve been working on for months now with little success. On Reddit, images are a <strong>huge</strong> part of what makes up the site. Some pictures are too big or too high-resolution to be viewed on the Apple Watch’s small screen. Throughout testing Nano, I had an email I could be reached by (nano@willbish.com), and one of the most common feature requests was image-zoom. Image-zoom is something that <em>is</em> a part of WatchKit, just not to us developers. An example of this is <code class="language-plaintext highlighter-rouge">Photos.app</code> on the Apple Watch, in which you can zoom with the crown and pan around with your finger. I’ve been trying to replicate this functionality, <a href="https://gyazo.com/3a92fb72b96795bd2338ede6c0e44ee7">but this is the closest I got</a>.</p>
</li>
</ul>
<p>I’m hoping WWDC 2018 brings some more updates to WatchKit so I can further improve Nano.</p>Wow, what a loooonnnnggg time coming.Support2018-04-18T02:29:59+00:002018-04-18T02:29:59+00:00https://nanoreddit.com/blogg/blogg/nano/support/2018/04/18/support<p>Sorry to hear Nano isn’t working as you’d expect!</p>
<p>Before contacting me, try these suggestions</p>
<h1 id="faq">FAQ</h1>
<ul>
<li>“I purchased Pro, but it isn’t showing on the Watch”</li>
<li>
<ul>
<li>Sorry to hear your Pro purchase didn’t go to plan, but I believe I can help you! On the iOS app with the watchOS app open, go to the Pro section. If you see confetti fall, this confirms that <strong>you have purchased pro</strong>. Now tap out of the Pro section and go to your subscriptions to confirm all your subscriptions and favorites etc have loaded. Now things should be in order, on the Watch force touch and click “Change Subreddit” and see if your subscriptions show up. NOTE: If you were already in the “Change Subreddit” section, you’ll need to back out and go back in.</li>
</ul>
</li>
<li>“I can’t log connect to Reddit”</li>
<li>
<ul>
<li>“It works on the Watch but not on the iPhone”</li>
</ul>
</li>
<li>
<ul>
<li>
<ul>
<li>This is one of those bugs that has been troublesome to deal with. In my own testing, I’ve found reinstalling the app can fix it. Alternatively, disable WiFi and connect to your Watch over Bluetooh.</li>
</ul>
</li>
</ul>
</li>
<li>
<ul>
<li>“It is looping on the setup page”</li>
</ul>
</li>
<li>
<ul>
<li>
<ul>
<li>Again, a troublesome issue. The potential solutions above may help.</li>
</ul>
</li>
</ul>
</li>
</ul>
<h1 id="if-the-above-didnt-work">If the above didn’t work:</h1>
<p>If you have an issue listed above but the solutions didn’t work, or you’d like to report another bug, here’s how you can do so:</p>
<ul>
<li><a href="https://twitter.com/NanoReddit">Tweet at me</a></li>
<li><a href="https://discord.io/nano">Join the Discord</a></li>
<li><a href="https://www.reddit.com/message/compose?to=willrb&subject=Nano%20Support">Message me on Reddit</a></li>
<li><a href="mailto:nano@willbish.com?subject=Nano%20Support">Email me</a></li>
<li><a href="https://reddit.com/r/Nanoapp">Post on the subreddit</a></li>
</ul>
<p>I’ve made so many options available so no matter what service you use, you’ll be able to contact me!</p>Sorry to hear Nano isn’t working as you’d expect!