<?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>Wireframe Software - Free Website Wireframes - Create &#38; Share Wireframes - Wireframe Tools &#187; website prototype</title>
	<atom:link href="http://www.wireframe-software.com/tag/website-prototype/feed" rel="self" type="application/rss+xml" />
	<link>http://www.wireframe-software.com</link>
	<description>Wireframes - Design Wireframe - Wireframe Tools - Website Wireframes - Wireframe Software</description>
	<lastBuildDate>Mon, 12 Sep 2011 09:38:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Google VP8 Open-source Video Codec Part &#8211; 1</title>
		<link>http://www.wireframe-software.com/google-vp8-open-source-video-codec-part-1</link>
		<comments>http://www.wireframe-software.com/google-vp8-open-source-video-codec-part-1#comments</comments>
		<pubDate>Fri, 23 Jul 2010 06:39:09 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Clickable Wireframes]]></category>
		<category><![CDATA[Digital Interface Prototyping]]></category>
		<category><![CDATA[GUI Design Software]]></category>
		<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[Interface Prototyping]]></category>
		<category><![CDATA[Prototyping]]></category>
		<category><![CDATA[Prototyping Software]]></category>
		<category><![CDATA[Rapid Paper Prototyping]]></category>
		<category><![CDATA[create website wireframes]]></category>
		<category><![CDATA[website prototype]]></category>
		<category><![CDATA[website wireframe]]></category>
		<category><![CDATA[Website Wireframe Software]]></category>
		<category><![CDATA[website wireframe tools]]></category>

		<guid isPermaLink="false">http://www.wireframe-software.com/?p=259</guid>
		<description><![CDATA[Challenges preventing a universally accepted video codec standard
With HTML5 looming, video codec standards have recently become a hot issue popularized by the oh-so public feud between Apple and Adobe. Up until now Flash has been the preferred video format on the web due to Adobe&#8217;s Flash Player being installed in most web browsers. The HTML5 [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Challenges preventing a universally accepted video codec standard</strong></p>
<p>With HTML5 looming, video codec standards have recently become a hot issue popularized by the oh-so public feud between Apple and Adobe. Up until now Flash has been the preferred video format on the web due to Adobe&#8217;s Flash Player being installed in most web browsers. The HTML5 video tag is intended to become the new standard way to show video online. The question is which formats should be supported in the tag. Despite its tremendous popularity Flash remains the property of a single corporation, Adobe. Apple favors the H.264 codec and due to the success of the iPhone, iPod Touch and now the iPad (which don&#8217;t support Flash) many popular sites such as YouTube, Vimeo and CNN, to name but a few, now have all or a growing number of their videos available in the H.264 format in addition to Flash. Criticism of H.264 is centered on the patents leading to most users of the format to pay licensing fees leading to the software company Nero to sue the licensing authority of the codec. This is where VP8 comes in.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wireframe-software.com/google-vp8-open-source-video-codec-part-1/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bing vs. Google Part &#8211; 2</title>
		<link>http://www.wireframe-software.com/bing-vs-google-part-2</link>
		<comments>http://www.wireframe-software.com/bing-vs-google-part-2#comments</comments>
		<pubDate>Mon, 19 Jul 2010 06:03:31 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Clickable Wireframes]]></category>
		<category><![CDATA[Digital Interface Prototyping]]></category>
		<category><![CDATA[GUI Design Software]]></category>
		<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[Interface Prototyping]]></category>
		<category><![CDATA[Prototyping]]></category>
		<category><![CDATA[Prototyping Software]]></category>
		<category><![CDATA[Rapid Paper Prototyping]]></category>
		<category><![CDATA[create website wireframes]]></category>
		<category><![CDATA[website prototype]]></category>
		<category><![CDATA[website wireframe]]></category>
		<category><![CDATA[Website Wireframe Software]]></category>
		<category><![CDATA[website wireframe tools]]></category>

		<guid isPermaLink="false">http://www.wireframe-software.com/?p=255</guid>
		<description><![CDATA[In what ways does Bing have a better interface design?
Where I found Bing to be better was in displaying related searches on the left side whereas Google displayed them at the bottom. Another neat feature of Bing was when hovering over search results and having the option of activating a pop-up box on the right [...]]]></description>
			<content:encoded><![CDATA[<p><strong>In what ways does Bing have a better interface design?</strong></p>
<p>Where I found Bing to be better was in displaying related searches on the left side whereas Google displayed them at the bottom. Another neat feature of Bing was when hovering over search results and having the option of activating a pop-up box on the right of the link with more information from the website without leaving Bing. Clicking on an image in Bing revealed a better interface design. In Google a frame of the <a title="website wireframe, website wireframe tools, create website wireframes, website wireframe software, website prototype" href="https://pidoco.com/" target="_blank">interface design</a> reveals metadata about the image but only that image. Bing allows you to view the information contained within the website where the image comes from right within Bing but also shows all the image results on the left with a scrollbar. The start page of Bing offers a more compact setup for entering a search, while in Google the user has to move his mouse quite a distance to search for images, videos and others. The background image serves to unify the main parts of the page, while all peripheral options are faded back into the grey frame. Tooltips for search categories in Bing also enhance its usability. Finally, Bing does not distract the user by offering an equivalent to Google’s famous “I’m Feeling Lucky” button.</p>
<p><strong>What strategy is Bing adopting in order to one-up Google?</strong></p>
<p>Bing has also added a new &#8216;Entertainment&#8217; section dedicated to music, movies, TV and games. What this essentially means is that Bing once more incorporates a lot more into its interface design even allowing users to play videos, songs and online flash games right within Bing. Where Google seeks to be your transit point connecting you to your destination, Bing seems intent on being the destination.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wireframe-software.com/bing-vs-google-part-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wireframe Fidelity &#8211; High Fidelity Wireframes &amp; Other Kinds of Wireframes</title>
		<link>http://www.wireframe-software.com/wireframe-fidelity-high-fidelity-wireframes-other-kinds-of-wireframes</link>
		<comments>http://www.wireframe-software.com/wireframe-fidelity-high-fidelity-wireframes-other-kinds-of-wireframes#comments</comments>
		<pubDate>Thu, 08 Apr 2010 11:01:37 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Clickable Wireframes]]></category>
		<category><![CDATA[Digital Interface Prototyping]]></category>
		<category><![CDATA[GUI Design Software]]></category>
		<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[Interface Prototyping]]></category>
		<category><![CDATA[Prototyping]]></category>
		<category><![CDATA[create website wireframes]]></category>
		<category><![CDATA[website prototype]]></category>
		<category><![CDATA[website wireframe]]></category>
		<category><![CDATA[Website Wireframe Software]]></category>
		<category><![CDATA[website wireframe tools]]></category>

		<guid isPermaLink="false">http://www.wireframe-software.com/?p=153</guid>
		<description><![CDATA[What are high fidelity wireframes?
In part two of this blog we shall have a closer look at high fidelity and other kinds of wireframes. Although sharing many of the same advantages with low-fidelity wireframes, a distinction between the two is that a high-fidelity wireframe is closer in design to the true representation of the final [...]]]></description>
			<content:encoded><![CDATA[<p><strong>What are high fidelity wireframes?</strong></p>
<p>In part two of this blog we shall have a closer look at high fidelity and other kinds of wireframes. Although sharing many of the same advantages with low-fidelity wireframes, a distinction between the two is that a high-fidelity wireframe is closer in design to the true representation of the final user interface. This is because high fidelity wireframes usually have slick and polished design features, even going as far as simulating an application&#8217;s work flow. Despite this high fidelity wireframes remain prototypes and usually require a lot of time investment to create which can be costly.</p>
<p><strong>What are the benefits of high fidelity wireframes?</strong></p>
<p>High fidelity wireframes usually are used in addition to and after low fidelity wireframes have been used to resolve the most impactful and fundamental usability or interface design problems of an application. Being eye-catching, high fidelity wireframes can be used to impress clients who have to sign off on a concept quickly. A high fidelity wireframe in this case would intuitively be faster for users to understand simply by glancing at them, leaving less room for misinterpretation. This is advantageous when designing complex user interfaces with lots of interactivity. In terms of your development team, high-fidelity wireframes allow you to collectively bring an interface to life. This helps in keeping a project&#8217;s budget manageable further satisfying clients.</p>
<p><strong>What are medium fidelity wireframes?</strong></p>
<p>It is worth noting that some people make the distinction of adding a third category; medium-fidelity wireframes which lie somewhere in between high and low fidelity wireframes. These are especially useful in larger projects when interface design fundamentals have been worked out, but more optically detailed representations are needed for pitches, presentations etc&#8230;</p>
<p><span id="more-153"></span></p>
<p><strong>What are annotated wireframes?</strong></p>
<p>Annotated wireframes are used to describe functional elements of an interface&#8217;s design. Small descriptive paragraphs are added to elements on the prototype for the benefit of stakeholders, thereby circumventing the need for verbal explanations just to make it understandable. Done correctly, they are easier to understand for non-technical stakeholders in the development process.</p>
<p><strong>What are clickable wireframes?</strong></p>
<p>Clickable wireframes blend the dynamic interactivity of hyperlinks with static visualizations of interfaces. This allows one to link multiple pages and &#8217;surf&#8217; wireframes as if they were a website or software. Clickable wireframe tools, such as pidoco°, use drag and drop functionality and dynamic menus to create WYSIWYG interface wireframes that are clickable, collaborative and can be annotated. This makes them effective in conveying and testing ideas in realtime.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wireframe-software.com/wireframe-fidelity-high-fidelity-wireframes-other-kinds-of-wireframes/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

