<?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>Form Designer - Converting your existing flat Forms to Dynamic, Interactive PDF Forms...</title>
	<atom:link href="http://formdesigner.org/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://formdesigner.org</link>
	<description>When You Want An Expert PDF Form Designer</description>
	<lastBuildDate>Mon, 18 Apr 2011 02:41:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Are You Looking For An Expert PDF Form Designer?</title>
		<link>http://formdesigner.org/?p=20</link>
		<comments>http://formdesigner.org/?p=20#comments</comments>
		<pubDate>Mon, 18 Apr 2011 02:41:16 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://formdesigner.org/?p=20</guid>
		<description><![CDATA[Intuitive &#8211; PDF Forms designed to flow logically from start to finish. Forms that only display relevant fields and hide those that aren&#8217;t relevant from the user filling the form. &#160; Cost Effective &#8211; PDF SwiftForms™ Forms that remove many of the inefficient and costly elements associated with traditional paper based forms. The need to [...]]]></description>
			<content:encoded><![CDATA[<div id="logo"></div>
<div>
<div><strong><br />
</strong></div>
<ul>
<li><strong>Intuitive &#8211; </strong>PDF Forms designed to flow logically from start to finish. Forms that only display relevant fields and hide those that aren&#8217;t relevant from the user filling the form.</li>
</ul>
<p>&nbsp;</p>
<ul>
<li><strong>Cost Effective &#8211; </strong>PDF SwiftForms™ Forms that remove many of the inefficient and costly elements associated with traditional paper based forms. The need to conduct large print runs no longer applies. The need to re-print if even a minor change is required along with disposal of out-of-date forms no longer applies. The need to pay staff to interpret near illegible hand written form entries and re-enter them into your systems no longer applies. The savings are many and the removal of significant problems associated with traditional forms are eliminated.</li>
</ul>
<p>&nbsp;</p>
</div>
<div>
<ul>
<li><strong>Accessible &#8211; </strong>PDF SwiftForms™ that are all developed with the goal of creating forms that are available to anyone who wants or needs to fill them in. Wherever practical within PDF Form development SwiftForms™ follow the United Nations G3ICT Accessibility guidelines and also develop to comply with any legislative requirements of the countries that SwiftForms™ will be hosted and used in.</li>
</ul>
<p>&nbsp;</p>
<ul>
<li><strong>Self Validating &#8211; </strong>PDF SwiftForms™ are smart forms because they are able to identify and alert the user filling them in when information is not what is expected. For example when someone enters a future date 01/01/2015 into a date field that requires their date of birth, a PDF SwiftForm will alert them to the error and return the user to the field so that they can immediately correct the mistake. This build in validation can check for correct formatting of email addresses, telephone numbers, check that required fields are not left blank and alert the user to a wide range of problems before the form is returned to your organisation.</li>
</ul>
<p>&nbsp;</p>
<ul>
<li><strong>Legible &#8211; </strong>Anyone who has received paper forms filled by hand understands the difficulty that is often experienced interpreting what has been written into the form. Every person has different handwriting and the process of deciphering what some handwritten text is meant to convey can be time consuming, fraught with error and costly inefficiency. Swiftforms™ return legible information that does not require re-keying by your staff improving quality and benefiting your bottom line.</li>
</ul>
<p>&nbsp;</p>
</div>
<div>
<ul>
<li><strong>Printable &#8211; </strong>At the root of PDF SwiftForms™ is fundamentally a PDF document. Although there is significant software based functionality embedded in the PDF document to enable the smart eform capabilities, at its basic level the document is still a PDF. This means that mo matter which operating system, device, screen resolution paper size or type, the printer you use or any other factor the document will appear and print the way it was intended to be seen.</li>
</ul>
<p>&nbsp;</p>
</div>
<div>
<ul>
<li><strong>Compatible &#8211; </strong>One of the several options for receiving your form data is as XML. Most modern systems are able to take a custom formatted XML document and import the data directly into existing databases or other systems. PDF SwiftForms™ provide other options for receiving your form data including as email messages, CSV files or or even the entire PDF document containing all of the saved entries.</li>
</ul>
<p>&nbsp;</p>
</div>
<div>
<ul>
<li><strong>Sign-able &#8211; </strong>If a hand-signed document is required a PDF SwiftForm™ will still provide an excellent solution that continues to provide many of the benefits listed above. Forms that require signature can be designed to validate prior to the print event being executed. This means that the form is forced to be as accurate as possible before the user prints, signs and post or faxes it back to your organisation.</li>
</ul>
<p>&nbsp;</p>
</div>
<div>
<ul>
<li><strong>Submittable &#8211; </strong>If a hand-signed document is not required and an electronic solution is suitable for your needs you also have the option with PDF SwiftForms™ to have data that is collected directly submitted to you as a custom formatted email, XML or directly into your database. Since the data is validated on the client (PDF Form) side of the process you can be confident that the correctly formatted information will be received no matter how you choose to receive it.</li>
</ul>
<p>&nbsp;</p>
</div>
<div>When establishing SwiftForms I wanted to have a very narrow focus. I wanted to do nothing other than specialise in the development of PDF Forms. I wanted to take great care with implementation of testing processes that would be continually refined ensuring delivery of the quality that our clients should be able to expect. I personally take the accesibility of your forms as seriously as the United Nations and many countries around the world do by following guidelines and ensuring legislative compliance.</div>
<div id="content">
<div id="post-1">
<p>I hope that this brief overview of SwiftForms provides your organisation with an insight into my philosophy and the product that you should expect to receive when you engage SwiftForms to develop new or convert your existing flat paper or PDF forms to dynamic PDF SwiftForms.</p>
<p>Rod Swift<br />
<a href="http://swiftforms.com.au/contact.php">Call, Fax, Skype or Email Me Today</a></p>
<p><a href="http://swiftforms.com.au/examples.php">See &amp; Test Out Example PDF SwiftForms</a>™</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://formdesigner.org/?feed=rss2&#038;p=20</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Form Designer &#8211; Things to be considered?</title>
		<link>http://formdesigner.org/?p=15</link>
		<comments>http://formdesigner.org/?p=15#comments</comments>
		<pubDate>Tue, 12 Apr 2011 02:17:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://formdesigner.org/?p=15</guid>
		<description><![CDATA[I am building up a list of items that I should consider or implement when developing electronic PDF Forms.  This post will function as a place where I&#8217;ll note down my ideas, what I find in online and offline study/research and a place where you can also contribute ideas to the list. To start with I&#8217;m thinking [...]]]></description>
			<content:encoded><![CDATA[<p>I am building up a list of items that I should consider or implement when developing electronic PDF Forms.  This post will function as a place where I&#8217;ll note down my ideas, what I find in online and offline study/research and a place where you can also contribute ideas to the list.</p>
<p>To start with I&#8217;m thinking about these high level topics:</p>
<ul>
<li>Context &#8211; computer, mobile devices, connected or not.</li>
</ul>
<ul>
<li>Accessibility &#8211; use with screen readers or other assistive technology.</li>
</ul>
<ul>
<li>Validation &#8211; message boxes, inline validation, how strict should you be.</li>
</ul>
<ul>
<li>Layout &#8211; sure to be a huge number of considerations.</li>
</ul>
<ul>
<li>Formatting data &#8211; what to do for different types.</li>
</ul>
<ul>
<li>Error messages &#8211; how informative should they be?</li>
</ul>
<p>It is likely many people have already done this so if I find a detailed list I will scrap this and post a link to the existing list. Feel free to add links to appropriate lists.</p>
<p>Rod</p>
]]></content:encoded>
			<wfw:commentRss>http://formdesigner.org/?feed=rss2&#038;p=15</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dynamic, Intuitive, Accessible PDF Form Designer</title>
		<link>http://formdesigner.org/?p=4</link>
		<comments>http://formdesigner.org/?p=4#comments</comments>
		<pubDate>Wed, 23 Mar 2011 03:33:29 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[LiveCycle PDF Forms]]></category>

		<guid isPermaLink="false">http://formdesigner.org/?p=4</guid>
		<description><![CDATA[Guidelines Topics Followed by SwiftForms™ Usability guidelines for online application forms Overall customer experience Make it easy for users to find the form Create a good first impression Encourage user trust Encourage user interest and feedback Create a flexible design which will support the needs of different users Moving around the form (navigation, workflow &#38; [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: left;"><a href="http://swiftforms.com.au/">Guidelines Topics Followed by SwiftForms™</a></p>
<ul>
<li style="text-align: left;">Usability guidelines for online application forms</li>
<li>Overall customer experience</li>
<li>Make it easy for users to find the form</li>
<li>Create a good first impression</li>
<li>Encourage user trust</li>
<li>Encourage user interest and feedback</li>
<li>Create a flexible design which will support the needs of different users</li>
<li>Moving around the form (navigation, workflow &amp; orientation)</li>
<li>Make it easy for users to understand the workflow and structure of the form</li>
<li>Make it easy for users to identify next steps (links and buttons)</li>
<li>Provide efficient navigation within the form</li>
<li>Provide users with a quick, efficient workflow</li>
<li>Reading the form (written content &amp; language)</li>
<li>Style of language</li>
<li>Grouping of information</li>
<li>Make it easy to complete the content</li>
<li>Viewing the form (layout &amp; presentation)</li>
<li>Page layout</li>
<li>Use of images</li>
<li>Readability</li>
<li>Accessibility</li>
<li>Appropriate use of colour</li>
<li>Interaction design</li>
<li>Error handling</li>
<li>Standards and other sources of information</li>
<li>Best Practice Checklists</li>
<li>Content</li>
<li>Form performance</li>
<li>Interaction design</li>
<li>Visual design</li>
</ul>
<p style="text-align: center;"><a href="http://swiftforms.com.au/">SwiftForms™</a></p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://formdesigner.org/?feed=rss2&#038;p=4</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

