<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>nick has a blog! &#187; webapps</title>
	<atom:link href="http://www.nickpeters.net/category/webapps/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nickpeters.net</link>
	<description></description>
	<lastBuildDate>Thu, 16 Dec 2010 07:07:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
		<item>
		<title>Jott</title>
		<link>http://www.nickpeters.net/2008/01/14/jott/</link>
		<comments>http://www.nickpeters.net/2008/01/14/jott/#comments</comments>
		<pubDate>Mon, 14 Jan 2008 22:04:12 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[jott]]></category>
		<category><![CDATA[lifehacks]]></category>
		<category><![CDATA[webapps]]></category>
		<category><![CDATA[lifehack]]></category>
		<category><![CDATA[notes]]></category>
		<category><![CDATA[reminders]]></category>
		<category><![CDATA[text]]></category>
		<category><![CDATA[todo]]></category>
		<category><![CDATA[transcribe]]></category>
		<category><![CDATA[voice]]></category>
		<category><![CDATA[webapp]]></category>

		<guid isPermaLink="false">http://www.nickpeters.net/2008/01/14/jott/</guid>
		<description><![CDATA[Jott is my new favorite web app. I took notice of it when I noticed a few people using it on twitter. I would see a message with a link to a voice recording of the same message. This is a pretty neat use for it, but I have another use for it. Before I [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.jott.com">Jott</a> is my new favorite web app.  I took notice of it when I noticed a few people using it on twitter.  I would see a message with a link to a voice recording of the same message.  This is a pretty neat use for it, but I have another use for it.  Before I get ahead of myself, let&#8217;s look at what Jott is.</p>
<p>Jott is a service that allows you to leave voice mails for yourself, or other people, and have it transcribed into text.  From the phone number you choose to use, it will ask you who you want to Jott and then allow you to leave a message up to 30 seconds in length.</p>
<p>I haven&#8217;t used it to send messages to anyone or to any service, but rather, I use it to take notes for later use.  Before I would usually take a picture of something or record video as reminders to myself.  Instead I call Jott, leave a message telling myself to add a movie to my Netflix queue or to check out a new band.  When I get home, I have a transcribed version of my message waiting for me in my inbox.  The neat thing about having a transcribed version of my message is that I just have to glance at it to remind myself.  There is no need to listen to what I said which takes a slightly longer time.</p>
<p>The transcription process is fairly accurate; Just make sure you speak clearly into your phone.  If Jott can&#8217;t properly transcribe your message, and you don&#8217;t remember what you wanted to remind yourself of, you can always listen to the original voice mail.</p>
<p>The added benefit of using voice is that it&#8217;s quicker than texting.  I find cell phone keypads to be slow, and distracting.  With this service I can quickly leave my message and go back to my normal routine.</p>
<p>I can definitely see the service becoming big since it has a lot of potential.  I recommend everyone to check it out and maybe write about how it has streamlined some task for you.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.nickpeters.net/2008/01/14/jott/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting Real</title>
		<link>http://www.nickpeters.net/2007/06/28/getting-real/</link>
		<comments>http://www.nickpeters.net/2007/06/28/getting-real/#comments</comments>
		<pubDate>Fri, 29 Jun 2007 05:46:59 +0000</pubDate>
		<dc:creator>Nick</dc:creator>
				<category><![CDATA[37signals]]></category>
		<category><![CDATA[Getting Real]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[startups]]></category>
		<category><![CDATA[webapps]]></category>

		<guid isPermaLink="false">http://www.nickpeters.net/2007/06/28/getting-real/</guid>
		<description><![CDATA[I just got done with the book â€œGetting Realâ€ by 37Signals. This book is a bible for anyone looking to start a web app using minimal resources without sacrificing quality.Â  &#8220;Getting Real&#8221; is divided into 16 chapters and covers planning your application up to launching and supporting your application. Each chapter consists of sections that [...]]]></description>
			<content:encoded><![CDATA[<p style="margin-bottom: 0in">I just got done with the book â€œ<a href="http://gettingreal.37signals.com/" title="Getting Real: The Book by 37signals" target="_blank">Getting Real</a>â€ by <a href="http://www.37signals.com/" title="37Signals Homepage" target="_blank">37Signals</a>.  This book is a bible for anyone looking to start a web app using minimal resources without sacrificing quality.Â  &#8220;Getting Real&#8221; is divided into 16 chapters and covers planning your application up to launching and supporting your application.  Each chapter consists of sections that talk about a certain aspect of the chapter.  For example, the chapter on supporting your application has a section on setting up forums, a section on why the developers should be on the support frontline, and how to prioritize bug fixes.  Each section is backed up by essays and quotes from various people who have been through the web app process .  I strongly recommend anyone who is thinking about or is in the middle of developing a web app to check out this book.  If anything, it lets you know where they&#8217;re coming from when they developed applications such as <a href="http://www.basecamphq.com/" title="Basecamp - Project collaboration, management and task software." target="_blank">Basecamp</a>.Â  Let&#8217;s check out some of the important concepts that we&#8217;re presented with.</p>
<ol>
<li>
<p style="margin-bottom: 0in"><strong>Don&#8217;t worry about the details; 	just make a decision.</strong>  Don&#8217;t waste time arguing about the small 	details of your web app.  The type font type used, border size, all 	don&#8217;t matter when it comes to the core of your application.  Learn 	to make a quick decision and move on.  Your users will give you 	feedback to let you know whether or not you&#8217;re on the right trail or 	not.</p>
</li>
<li>
<p style="margin-bottom: 0in"><strong>Include only the most necessary 	features in â€œ1.0â€</strong>  Don&#8217;t add any unnecessary features; in 	fact a lot of the features that you think are necessary may really 	not be.  Cut these features out and include them in a future 	release.  An example they gave was a billing system when they 	deployed Basecamp.  The feature wasn&#8217;t necessary until 1 month after 	their initial release because that&#8217;s when their users got billed.  	Instead they released Basecamp and then worked on it.  This was 	plenty of time to create the feature and everything worked out.</p>
</li>
<li>
<p style="margin-bottom: 0in"><strong>Iterate as you go.</strong>  The 	nice thing about web apps is that you can instantly deploy bug fixes 	and new features to your users.  This allows you to be competitive 	since you are able to easily adapt to change and rapidly make fixes. 	 You&#8217;re also able to receive instant feedback from your users as you 	make fixes and/or deploy bug fixes.</p>
</li>
<li>
<p style="margin-bottom: 0in"><strong>Create your interface first.</strong> 	 Start off with some sketches on a piece of paper and then maybe 	convert it into HTML/CSS.  The reason to do this is because the 	interface is easier to modify as opposed to re-writing code.  As you 	create your mock-ups questions will be brought up and decisions will 	be made.  It&#8217;s better to make those decisions at this stage rather 	than after you&#8217;re into hardcore coding.</p>
</li>
<li>
<p style="margin-bottom: 0in"><strong>Learn to market your site from 	day one.</strong>  Include a teaser on your front page, screenshots of previews, blog about the development process and features 	that will be included in the initial release, use invite codes.  All 	of this will create a buzz about your product. When it comes to 	invite codes, have users submit their email addresses to be notified 	when more invites will be available.  You&#8217;ll at least now have a list of 	people who have expressed interest in your app and they can be 	notified when your initial release comes out.</p>
</li>
<li>
<p style="margin-bottom: 0in"><strong>Become your own support 	department.</strong>  Dealing with your users on a direct basis allows 	you to get into their mind and get instant feedback.  The people who 	are developing the application should be answering questions, 	defending their choices and taking criticism.  Be sure to consider a 	FAQ page and forums so that users can help themselves and other users.</p>
</li>
</ol>
<p style="margin-bottom: 0in">I&#8217;ve really only scratched the surface of what this book has to offer.  Check out the rest <a href="http://gettingreal.37signals.com/toc.php" title="Getting Real">here</a>!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.nickpeters.net/2007/06/28/getting-real/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

