<?xml version="1.0" encoding="UTF-8"?>
<rss version='2.0' 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">
  <channel>
    <title>Daphne Cheung</title>
    <description>Tech and product enthusiast. Implementer. Always learning something new.</description>
    <link>https://daphnecheung.silvrback.com/feed</link>
    <atom:link href="https://daphnecheung.silvrback.com/feed" rel="self" type="application/rss+xml"/>
    <category domain="daphnecheung.silvrback.com">Content Management/Blog</category>
    <language>en-us</language>
      <pubDate>Sun, 10 Aug 2014 01:12:27 +0100</pubDate>
    <managingEditor>daphnec2002@gmail.com (Daphne Cheung)</managingEditor>
      <item>
        <guid>https://daphnecheung.silvrback.com/tools-product-shots#6555</guid>
          <pubDate>Sun, 10 Aug 2014 01:12:27 +0100</pubDate>
        <link>https://daphnecheung.silvrback.com/tools-product-shots</link>
        <title>Useful Tools For Product Shots</title>
        <description>Not a designer? No worries, these tools will help you put a screenshot on to a laptop or mobile image.</description>
        <content:encoded><![CDATA[<p>Fascinating tools I came across that are time savers. If you&#39;re not a designer or you don&#39;t have the tools available to you to create product images, these will help you get the job done quickly and easily.</p>

<h2 id="snapito"><a href="http://snapito.com/">Snapito</a></h2>

<p><img alt="Silvrback blog image" src="https://silvrback.s3.amazonaws.com/uploads/cd724692-bcbd-4df5-86a5-450f20607c7a/useful-tools-product-shots-snapito_large.jpg" /></p>

<p><a href="http://snapito.com/">Snapito</a> is a simple web tool created by Cazcade Ltd, a startup in Brighton, UK. This tool will create high quality screenshots. Simply enter the url of the site you want to screenshot and click the settings cog to reveal additional options. </p>

<p>You can choose the screenshot size (desktop, tablet, mobile) and the type of screenshot you want (full length, large cropped, medium cropped, small cropped, thumbnail).</p>

<p>Even if you have Photoshop and know how to create a full length screenshot, it&#39;s time consuming. This tool will create a screenshot while you switch browser tabs and work on something else. </p>

<p>One thing I did notice, if your site lazy loads images, any images below the fold will not show up. If you change the delay setting in Snapito, it will work. I found that setting the delay to 10 seconds seems to work well.</p>

<p>The tool is free to use. If you need to generate screenshots for more than 100 unique urls or want to use their API, check out <a href="http://snapito.io/">their site</a> for more info.</p>

<h2 id="frame"><a href="http://frame.lab25.co.uk/">Frame</a></h2>

<p><img alt="Silvrback blog image" src="https://silvrback.s3.amazonaws.com/uploads/a5e561f7-7e77-4a04-ac31-3aff546bf009/useful-tools-product-shots-frame_large.jpg" /></p>

<p><a href="http://frame.lab25.co.uk/">Frame</a> is a free tool created by <a href="https://twitter.com/FrameByLab25">Lab25</a>, which is built and run by <a href="https://twitter.com/paulaikd">Paul Aikman</a>, <a href="https://twitter.com/ArminSolecki">Armin Solecki</a> and <a href="https://twitter.com/i_am_grant">Grant MacLennan</a> from Glasgow, Scotland.</p>

<p>If you need a product shot of your site in the image, Frame will save you time and will generate the image in a matter of seconds.</p>

<p>As soon as you arrive on the site, click the &quot;Get Started&quot; button. You will be presented with an option to choose desktop, Android, iPhone, etc.</p>

<p><img alt="Silvrback blog image" src="https://silvrback.s3.amazonaws.com/uploads/42fc2d8b-c185-4d33-8301-9e6e0cdf4bb9/frame-product-shot-options_large.jpg" /></p>

<p>Choose the photo you want to use, then upload your image, resize and reposition your crop area. You can download the image or copy the and share the url on social networks.</p>

<p><img alt="Silvrback blog image" src="https://silvrback.s3.amazonaws.com/uploads/bd2e510a-36b9-4f27-9736-44d58f871ba1/product-shot-socksonanoctopus_large.png" /></p>
]]></content:encoded>
      </item>
      <item>
        <guid>https://daphnecheung.silvrback.com/100-tips-for-better-beta-tests#5056</guid>
          <pubDate>Wed, 11 Jun 2014 14:53:05 +0100</pubDate>
        <link>https://daphnecheung.silvrback.com/100-tips-for-better-beta-tests</link>
        <title>100 Tips For Better Beta Tests</title>
        <description></description>
        <content:encoded><![CDATA[<p>Years ago when I was taking my CIS courses, I remember my professors often said, <em>&quot;always beta test your software before launching it.&quot;</em></p>

<p>This couldn&#39;t be more true especially through social networks like Facebook and Twitter. Users will not hesitate to vocalize their opinions if you didn&#39;t test out your software and pushed out an alpha version as your beta (or beta as live). Opinions not only can be harsh and ruthless, but they can spread out there pretty fast.</p>

<p>If you&#39;re launching a product on your own or if you&#39;re a small company, you may wonder where to begin. This is a <a href="http://www.slideshare.net/centercode/100-tips-for-better-beta-tests">great ebook</a> in a SlideShare presentation by <a href="http://www.centercode.com">Centercode</a> containing 100 tips for beta testing that can help keep things organized.</p>

<p>The ebook outlines planning your test, recruiting and selecting testers, handling Non Disclosure Agreements (nothing worse than a tester tweeting about your secret killer product), communicating with testers, handling feedback, etc.</p>
<iframe width="100%" height="535" src="http://jsfiddle.net/daphnecheung/tpMrE/2/embedded/result" allowfullscreen="allowfullscreen" frameborder="0"></iframe>

]]></content:encoded>
      </item>
      <item>
        <guid>https://daphnecheung.silvrback.com/checking-out-silvrback#3819</guid>
          <pubDate>Thu, 15 May 2014 04:48:08 +0100</pubDate>
        <link>https://daphnecheung.silvrback.com/checking-out-silvrback</link>
        <title>Moved To Silvrback</title>
        <description></description>
        <content:encoded><![CDATA[<p>A few days ago, I came across this new blogging platform, Silvrback. I have moved some of my posts from my site that was self hosted on WordPress. </p>

<p>As much as I appreciate the features WordPress offers, I have been thinking of moving my portfolio site for a few reasons. </p>

<p>I already have a site that a friend and I update that&#39;s also a WordPress site (<a href="http://socksonanoctopus.com">socksonanoctopus.com</a>). For that site, it&#39;s updated daily with content in addition to updating plugins, cleaning out spam comments and other things that come with managing a WordPress site. And I planned on writing more on my portfolio site, but never really had enough time to do that between full-time work, updating the other site, brushing up and learning some new skills, blogging for this site just never happened. And if there&#39;s anything that I don&#39;t like most is having an item to do and not getting it done.</p>

<p>Instead of letting my site collect dust, I thought, <em>if I moved my site to a different blogging platform, then that would stop me from constantly changing the theme and tweaking it so much and actually write</em>. Not that I don&#39;t like taking a peek at how something was coded in a theme or how a layout was done in CSS. I certainly enjoy it, but a goal of mine was to write more in 2014 rather than tweaking themes all the time.</p>

<p>Another reason for moving to Silvrback is because it seemed to cover the basics of what I was looking in a replacement platform. The bio page is pretty nice. It&#39;s like a mini resume/LinkedIn so there&#39;s no need to write a lengthy bio page just so it doesn&#39;t look so empty and then a separate project/portfolio page.</p>

<p>The move wasn&#39;t too painful. Some of the items I had listed in my portfolio I didn&#39;t transfer over because it seemed similar to others I already listed in my portfolio or it was outdated/didn&#39;t exist anymore. Plus, I didn&#39;t have that much content to transfer over.</p>

<p>One thing I did have to get used to was writing in Markdown instead of writing in HTML. Sometimes I still catch myself typing HTML.</p>
]]></content:encoded>
      </item>
  </channel>
</rss>