<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Sybase iAnywhere for iPhone Creates Security Challenges</title>
	<atom:link href="http://iphonecto.com/2009/03/12/sybase-ianywhere-for-iphone-creates-security-challenges/feed/" rel="self" type="application/rss+xml" />
	<link>http://iphonecto.com/2009/03/12/sybase-ianywhere-for-iphone-creates-security-challenges/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=sybase-ianywhere-for-iphone-creates-security-challenges</link>
	<description>iPhoneCTO is the authority on iPhone in the enterprise.  You will find enterprise &#38; business application reviews, news, editorial and best practices for deploying and administering iPhones in corporate and small business environments.</description>
	<lastBuildDate>Sat, 07 Apr 2012 17:41:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Jóhannes Kristinsson</title>
		<link>http://iphonecto.com/2009/03/12/sybase-ianywhere-for-iphone-creates-security-challenges/comment-page-1/#comment-971</link>
		<dc:creator>Jóhannes Kristinsson</dc:creator>
		<pubDate>Wed, 19 Jan 2011 14:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://iphonecto.com/?p=863#comment-971</guid>
		<description>While the initiative to bring the iAnywhere functionality to the iPhone is greatly appreciated - the implementation could not have been much worse. Sybase, a company which should have enough resources to create high quality products, might have put efforts into the server side of the solution, but at the same time left a disaster for the iPhone clients.

The software does not follow standard guidelines for iOS HMI which means that the application in many ways behave much differently from other applications. For example – the recommendation is that when a user right-swipes on an item in a list (such as an email) it is an indication to delete the item. iAnywhere interprets this as &quot;open item&quot;.
There are also logical &quot;quirks&quot; in the application such as showing the local phonebook before a search is done, but when the search is committed, only show corporate results, without explaining the difference for the user.

Moreover, the synchronization experience is frustrating at least, if not to say horrible. When the application is started it updates the email and calendar in the background, but shows no indication that synchronization is currently being performed, when it was last done, or if the email list is currently up to date. When synchronization between the corporate email server and the iAnywhere solution is down (which happens quite a lot at the very large multinational company I&#039;m working at) there is no indication to tell that the list of emails you see is up to date. More likely than not, this is not the case.

Finally, the program is full of bugs. It is slow, crashes, shows error messages more often than expected for a program of this sort. Not to mention that the program is capable, and actually have, erased peoples personal contact books (the iPhone built-in one), which is one thing the so praised &quot;sandboxed&quot; approach should have prevented.

To summarize – the idea to bring a sandboxed enterprise Mail/Calendar/Contact management application to mobile devices is great, but it feels like the iPhone application was developed as a homegrown summer intern project by some manager&#039;s nephew. It is buggy, has logical errors, doesn&#039;t follow iPhone development guidelines, and judging from the kind of errors and catastrophes it has created among our users, lacks a good underlying architecture. Sybase need to put in some adequate resources to release something that is not most closely described as an iPhone App disaster.
</description>
		<content:encoded><![CDATA[<p>While the initiative to bring the iAnywhere functionality to the iPhone is greatly appreciated &#8211; the implementation could not have been much worse. Sybase, a company which should have enough resources to create high quality products, might have put efforts into the server side of the solution, but at the same time left a disaster for the iPhone clients.</p>
<p>The software does not follow standard guidelines for iOS HMI which means that the application in many ways behave much differently from other applications. For example – the recommendation is that when a user right-swipes on an item in a list (such as an email) it is an indication to delete the item. iAnywhere interprets this as &#8220;open item&#8221;.<br />
There are also logical &#8220;quirks&#8221; in the application such as showing the local phonebook before a search is done, but when the search is committed, only show corporate results, without explaining the difference for the user.</p>
<p>Moreover, the synchronization experience is frustrating at least, if not to say horrible. When the application is started it updates the email and calendar in the background, but shows no indication that synchronization is currently being performed, when it was last done, or if the email list is currently up to date. When synchronization between the corporate email server and the iAnywhere solution is down (which happens quite a lot at the very large multinational company I&#8217;m working at) there is no indication to tell that the list of emails you see is up to date. More likely than not, this is not the case.</p>
<p>Finally, the program is full of bugs. It is slow, crashes, shows error messages more often than expected for a program of this sort. Not to mention that the program is capable, and actually have, erased peoples personal contact books (the iPhone built-in one), which is one thing the so praised &#8220;sandboxed&#8221; approach should have prevented.</p>
<p>To summarize – the idea to bring a sandboxed enterprise Mail/Calendar/Contact management application to mobile devices is great, but it feels like the iPhone application was developed as a homegrown summer intern project by some manager&#8217;s nephew. It is buggy, has logical errors, doesn&#8217;t follow iPhone development guidelines, and judging from the kind of errors and catastrophes it has created among our users, lacks a good underlying architecture. Sybase need to put in some adequate resources to release something that is not most closely described as an iPhone App disaster.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

