<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Product on Ionic, Capacitor, Web Native Expert</title>
    <link>https://www.netkow.com/categories/product/</link>
    <description>Recent content in Product on Ionic, Capacitor, Web Native Expert</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 28 Jun 2019 05:23:55 -0700</lastBuildDate>
    <atom:link href="https://www.netkow.com/categories/product/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Always Read the Comments</title>
      <link>https://www.netkow.com/always-read-the-comments/</link>
      <pubDate>Fri, 28 Jun 2019 05:23:55 -0700</pubDate>
      <guid>https://www.netkow.com/always-read-the-comments/</guid>
      <description>&lt;p&gt;&amp;ldquo;Never read the comments&amp;rdquo; is a familiar maxim told to technologists building products.&lt;/p&gt;&#xA;&lt;p&gt;It makes sense, right? Users typically only leave feedback after they&amp;rsquo;ve either had an extremely poor experience or a positive one.&lt;/p&gt;&#xA;&lt;p&gt;However, there is value in reading online comments if you frame them correctly.&lt;/p&gt;&#xA;&lt;h2 id=&#34;identify-new-product-champions&#34;&gt;Identify New Product Champions&lt;/h2&gt;&#xA;&lt;p&gt;Building a strong relationship with individuals who are passionate promoters of your products is a crucial strategy for growing a business. You can often find them in the comments! Look beyond traditional &amp;ldquo;comment boxes&amp;rdquo; to social media, forums, Slack groups - any online space where communities gather. They&amp;rsquo;re the ones answering questions about your products, sharing your content, and seeking you out at conferences.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Easiest Way to Keep Product Documentation Up to Date</title>
      <link>https://www.netkow.com/easiest-way-keep-documentation-up-to-date/</link>
      <pubDate>Fri, 07 Jun 2019 05:23:55 -0700</pubDate>
      <guid>https://www.netkow.com/easiest-way-keep-documentation-up-to-date/</guid>
      <description>&lt;p&gt;Documentation.&lt;/p&gt;&#xA;&lt;p&gt;The backbone of successful and beloved products, but difficult to keep up to date given how quickly products evolve. Not to mention dreaded by software developers, who would instead write code.&lt;/p&gt;&#xA;&lt;p&gt;Given these challenges, I’ve found that the easiest way to keep product documentation up to date is:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;While working on a product, update its documentation simultaneously.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;At face value, this appears simple enough, but often isn&amp;rsquo;t.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-this-approach&#34;&gt;Why This Approach?&lt;/h2&gt;&#xA;&lt;p&gt;When building your product or creating a demo, chances are you’re focused on a specific area or “theme.” This includes installation/setup, hosting, interacting with the CLI, debugging, UI theming, backend API integration, etc. Updating documentation simultaneously is much faster when the related product concepts are fresh in your mind. This is often the reason why developers shy away from documentation updates - it’s left to the end of the current task or sprint, making it easy to fall to the wayside. Or worse: “when we get to it” which, spoiler alert, is often never.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
