<?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>Stoy Solutions blog &#187; Development</title>
	<atom:link href="http://blog.stoysolutions.com/category/development/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.stoysolutions.com</link>
	<description>Sharing thoughts on new ideas in the world of software and web media</description>
	<lastBuildDate>Thu, 21 Jan 2010 14:26:13 +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>What is it like to redesign a cinema site?</title>
		<link>http://blog.stoysolutions.com/what-is-it-like-to-redesign-a-cinema-site-2/</link>
		<comments>http://blog.stoysolutions.com/what-is-it-like-to-redesign-a-cinema-site-2/#comments</comments>
		<pubDate>Tue, 19 Jan 2010 13:38:38 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Development]]></category>

		<guid isPermaLink="false">http://blog.stoysolutions.com/?p=21</guid>
		<description><![CDATA[It’s relatively easy to point out the disadvantages of an old design, when you’re about to do the new one. But how to develop a completely new design, especially when it comes to a site of a cinema?
It has to be dynamic, but not heavy – easy to load in the browser. It has to [...]]]></description>
			<content:encoded><![CDATA[<p>It’s relatively easy to point out the disadvantages of an old design, when you’re about to do the new one. But how to develop a completely new design, especially when it comes to a site of a cinema?</p>
<p>It has to be dynamic, but not heavy – easy to load in the browser. It has to be informative, but not a movie site. It should represent the cinema brand, to emphasize the unique movie experience in this cinema.</p>
<p>We went through all these considerations while we were working on the website of <a href="http://kinoarena.com/" target="_blank">Arena cinemas</a> – the biggest cinema chain in Bulgaria with over 60 cinema halls in 6 Bulgarian cities.</p>
<p>In September 2009 we took up Arena’s website, which development was far behind the business development of the cinema. The website was completely static, heavy info update procedure and old fashioned design.</p>
<p>We changed the whole design – the menu has been restructured for better navigation; the current information has started being pointed out on the homepage, where it should be; the content has been enriched with different formats &#8211; .avi files, images, text. We put flash banner positions.</p>
<p>We updated the CMS with the functionalities of the redesign.</p>
<p>The new site stats show that the visitor’s loyalty grows and the site has regular visitors – an evidence for the positive user’s experience. The site has over 30 000 visits per week and we are currently exploring some exciting advertising models.<br />
Have we missed the point? If there is a cinema website that you are in love &#8211; please let us know which feature does it for you and why.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.stoysolutions.com/what-is-it-like-to-redesign-a-cinema-site-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mobile design guidelines</title>
		<link>http://blog.stoysolutions.com/mobile-design-guidelines/</link>
		<comments>http://blog.stoysolutions.com/mobile-design-guidelines/#comments</comments>
		<pubDate>Wed, 22 Apr 2009 09:49:16 +0000</pubDate>
		<dc:creator>Ilian</dc:creator>
				<category><![CDATA[Development]]></category>

		<guid isPermaLink="false">http://www.stoysolutions.com/blog/?p=15</guid>
		<description><![CDATA[With the number of people using the web through their mobiles continuously rising, also increases the need of good sites which are optimized and built specifically for mobile devices. In this post you will find valuable information about ways to design your web site for the mobile audience and ensure that users receive a satisfactory [...]]]></description>
			<content:encoded><![CDATA[<p><!-- st1\:*{behavior:url(#ieooui) } --><span lang="EN-GB">With the number of people using the web through their mobiles continuously rising, also increases the need of good sites which are optimized and built specifically for mobile devices. In this post you will find valuable information about ways to design your web site for the mobile audience and ensure that users receive a satisfactory experience while browsing.</span> <span lang="EN-GB">The basic guidelines that should be followed are provided below:</span></p>
<p><strong>1. Find out the right screen size</strong> <span lang="EN-GB">The common phones available can be roughly categorized in several categories based on their screen size:</span></p>
<ul type="disc">
<li class="MsoNormal"><span lang="EN-GB">128 x 160 pixels</span></li>
<li class="MsoNormal"><span lang="EN-GB">176 x 220 pixels</span></li>
<li class="MsoNormal"><span lang="EN-GB">240 x 320 pixels</span></li>
<li class="MsoNormal" style="margin-bottom: 12pt;"><span lang="EN-GB">320 x 480 pixels</span></li>
</ul>
<p><span lang="EN-GB">If you stick to these screen sizes you can guarantee that many people will be able to view your site. Maybe the most important thing here is to make sure the content is organized vertically, as the viewport has very limited space. Another good point to mention – just use compliant xHTML and not WML, unless your target group is the old rigid Nokia 1100 <img src='http://blog.stoysolutions.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> .</span></p>
<p><span lang="EN-GB"><strong>2. Choose your markup language </strong></span><span lang="EN-GB">Continuing with the latter, you have to make a decision on what markup you’ll be using. So is it going to be WML or xHTML? WML(Wireless Markup Language) was used primarily in the early days of mobile web devices and is now considered old and obsolete. Hand by hand with the WAP protocol it was the only way to access the Internet through mobile devices. Conversely xHTML is a modern “language” accepted everywhere and being approved as a standard. Most new devices understand it and can render xHTML pages similarly to your favourite desktop browser.</span></p>
<p><span lang="EN-GB"><strong>3. Validate your web site</strong></span> <span lang="EN-GB">Why is web site validation necessary? Firstly, because erroneous markup is removed and this guarantees user agents won’t receive input they won’t understand. For example if you miss to provide a valid mobile document type definition like this one -</span></p>
<pre><span lang="EN-GB">&lt;!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN"
"http://www.wapforum.org/DTD/xhtml-mobile10.dtd"&gt;

</span></pre>
<p><span lang="EN-GB">, many browsers will fail to process the document properly and produce unexpected results. You might provide a valid DTD, but you need to write your markup according to the definition. Basically there are subtle differences between the various DTD’s, here’s a list for the interested, of the most popular ones to choose from:</span></p>
<ul type="disc">
<li class="MsoNormal"><span lang="EN-GB">XHTML Mobile Profile 1.0</span></li>
<li class="MsoNormal"><span lang="EN-GB">XHTML Mobile Profile 1.1</span></li>
<li class="MsoNormal"><span lang="EN-GB">XHTML Mobile Profile 1.2</span></li>
<li class="MsoNormal"><span lang="EN-GB">XHTML Basic 1.0</span></li>
<li class="MsoNormal"><span lang="EN-GB">XHTML Basic 1.1</span></li>
</ul>
<p><span lang="EN-GB">As for the validation locations, there are two places, the first one is of course w3c –</span> <a href="http://validator.w3.org/mobile/"><cite><span lang="EN-GB">http://</span></cite>validator.w3.org/mobile/</a> <span lang="EN-GB">, with their mobile validation checker and the second one –</span> <a href="http://www.ready.mobi"><cite><span lang="EN-GB">http://www.ready.mobi</span></cite></a> <span lang="EN-GB">, they have built a really nice validation engine which provides detailed reports on areas which seem to be problematic or cause errors.</span></p>
<p><strong><span lang="EN-GB">4. Use short domain names.</span></strong> <span lang="EN-GB">As we all know typing is not as easy on mobiles as it is on a desktop machine. Less typing for the user actually means less frustration here. Wouldn’t it be easier to write mysite.mobi instead of mygorgeousmobilewebsite.mobi ? Of course yes, and a good thing to do to avoid the inconsistencies in names between the normal version and the mobile version Is to use a subdomain – <a href="http://example.com/" target="_blank">example.com</a> and <a href="http://mobi.example.com/" target="_blank">mobi.example.com</a> suits our purpose just fine.</span></p>
<p><strong><span lang="EN-GB">5. Keep your page size small</span></strong> <span lang="EN-GB">Limited bandwidth and processor power is something that distinguishes mobile computers from regular ones. If you make a request for a heavy spiced up web page and the packet sizes that you receive by the mobile operator are small ones – the only thing that you’ll guarantee for the visitor is the slow browsing and annoying, painful interactions. Do not use too much images, prefer repeated backgrounds where necessary or just plain colours – this could greatly reduce the overall size and increase download time by the client.</span> <span lang="EN-GB">In conclusion we can say that if you pay proper attention to the guidelines provided above during your development, you’ll know your visitors won’t run away from your mobile site disappointed.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.stoysolutions.com/mobile-design-guidelines/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

