<?xml version="1.0" encoding="utf-8" ?>

<rss version="0.91" >
<channel>
<title>Feelin' Fine</title>
<link>http://blog.proculo.de/</link>
<description>Macs &amp; more</description>
<language>en</language>
<image>
        <url>http://blog.proculo.de/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: Feelin' Fine - Macs &amp; more</title>
        <link>http://blog.proculo.de/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>On Folio Case, Competition and Sales</title>
    <link>http://blog.proculo.de/archives/181-On-Folio-Case,-Competition-and-Sales.html</link>

    <description>
        When I released my iPad PDF reader &lt;a href=&quot;http://foliocaseapp.com/&quot;&gt;Folio Case&lt;/a&gt; &lt;a href=&quot;http://www.foliocaseapp.com/blog/files/folio_case_released.php&quot;&gt;on Thursday&lt;/a&gt;, I received a lot of praise for it. People found it to be beautiful, easy to use, even calling it the &lt;a href=&quot;http://www.macstories.net/ipad/folio-case-review/&quot;&gt;most elegant solution currently available on the iPad&lt;/a&gt;. Since Folio Case was focusing on a very pleasant reading experience, I never regarded the most downloaded PDF readers as my main competition - the differences were just too big, since those apps usually focus on a huge amount of features and lagged behind in user experience.&lt;br /&gt;
&lt;br /&gt;
However, Apple today released an update to &lt;a href=&quot;http://www.apple.com/ipad/features/ibooks.html&quot;&gt;iBooks&lt;/a&gt;, their fantastic eBook reader software from which Folio Case takes quite a bit of inspiration. iBooks is a direct competitor because it plays in the same league as Folio Case, if not actually higher. It has a reduced feature set, but a beautiful reading experience. The biggest problem here for me is, obviously, that iBooks is free while &lt;a href=&quot;http://bit.ly/getfoliocase&quot;&gt;Folio Case is priced at $5.99&lt;/a&gt; - and they say you just cannot compete with free. I cannot say I planned for this to happen, but I&#039;ll likely find out soon if it is possible to sustain a competitor to iBooks. The least I can do is try to keep my app from finding its untimely death at the bottom of the App Store charts.&lt;br /&gt;
&lt;br /&gt;
So what&#039;s my plan of action here? Fortunately, Folio Case had its origin as a fun little project on the side which just started because I didn&#039;t like any of the available PDF readers out there, &lt;a href=&quot;http://twitter.com/gruber/status/13334452692&quot;&gt;and it seems others didn&#039;t either&lt;/a&gt;. That means that it&#039;s easier for me to keep this app going than it would be for someone who depends on the income from their App Store sales. Speaking of sales, I thought I&#039;d share some sales numbers here to illustrate my point:&lt;br /&gt;
&lt;br /&gt;
Thursday, June 18 2010: 85 sales&lt;br /&gt;
Friday, June 19 2010: 100 sales&lt;br /&gt;
Saturday, June 20 2010: 123 sales&lt;br /&gt;
Sunday, June 21 2010: 76 sales&lt;br /&gt;
&lt;br /&gt;
That&#039;s 384 sales in total since Folio Case was approved for sale in the App Store, or about  1,180 in revenue for me after Apple&#039;s cut and before taxes. Not bad for four days of sales, but I don&#039;t expect these to stay at this level at all, for two reasons. First, there&#039;s now pretty good competition which is free. Second, this was the launch, which had &lt;a href=&quot;http://favstar.fm/users/arepty/status/16412146412&quot;&gt;quite a bit of buzz on Twitter&lt;/a&gt; and was bound to have higher sales numbers than what an app like this would get a few weeks after its release. I&#039;m pretty happy about selling 20 copies of Folio Case per day in the long run, but even that is going to require some effort on my part.&lt;br /&gt;
&lt;br /&gt;
So what am I going to do in the future? While Apple has several advantages over me, especially in the resources department, I believe I can be more flexible and deliver more quickly. I can have direct connections to customers, which helps both me and all of them. For example, on Saturday I had a pissed off customer who was complaining about crashes in Folio Case and demanded his money back. We wrote back and forth, I got help from him and identified the issue and submitted a fix, which is currently in review. The same customer just wrote to me, saying that iBooks behaves worse than Folio Case in his case, crashing more and not recovering at all. Suffice to say, thanks to me being able to help him out and taking a real interest in his problem, the customer is now rather happy.&lt;br /&gt;
&lt;br /&gt;
Cases like this will be my chance to keep Folio Case a viable product in the future. Right now, I am working on Folio Case 1.1 which will, among other features which I have yet to reveal, hopefully contain &lt;a href=&quot;https://www.dropbox.com/&quot;&gt;Dropbox&lt;/a&gt; support (Dropbox has yet to accept my application). Folio Case already allows downloading documents from the web, which iBooks doesn&#039;t, and this feature will help to allow users even more flexibility in managing their documents. Also, people seem to just love the page turning effect, and iBooks for some reason doesn&#039;t use that for PDF documents. Users who want a PDF reader which does exactly what they want it to do and offers a great reading experience at the same time will find it in Folio Case. In the future, I see Folio Case as the app iPad users should get when they have outgrown iBooks.&lt;br /&gt;
&lt;br /&gt;
In the end, I cannot say whether it&#039;s a smart idea to put more effort into Folio Case from a return-on-investment perspective. All I know is that it&#039;s what I love to do, and it&#039;s what those existing 384+ customers deserve, so I&#039;ll just push forward now. If I didn&#039;t have a day job and were living off the money from my App Store sales, I might see things differently. But even if I only get 10 sales per day in the next few months, it was all worth it because it&#039;s just been incredible so far. 
    </description>
</item>
<item>
    <title>Attaching a UIToolbar to the iPhone's Keyboard</title>
    <link>http://blog.proculo.de/archives/178-Attaching-a-UIToolbar-to-the-iPhones-Keyboard.html</link>

    <description>
        One nifty little &lt;a href=&quot;http://www.apple.com/iphone/&quot;&gt;iPhone&lt;/a&gt; feature that left an impression with me is the way that the keyboard in the &quot;&lt;a href=&quot;http://www.apple.com/iphone/iphone-3gs/messages.html&quot;&gt;Messages&lt;/a&gt;&quot; application slides in and out with the keyboard, as if it were attached to it - but it isn&#039;t. I needed a similar feature for an app that I&#039;m currently working on for a client, so I decided to investigate how to implement this feature in my own stuff.&lt;br /&gt;
&lt;br /&gt;
&lt;p&gt;&lt;div class=&quot;serendipity_imageComment_left&quot; style=&quot;width: 142px&quot;&gt;&lt;div class=&quot;serendipity_imageComment_img&quot;&gt;&lt;a  class=&#039;serendipity_image_link&#039;  rel=&#039;lightbox&#039; href=&#039;http://blog.proculo.de/uploads/Messages_NoKeyboard.png&#039;&gt;&lt;!-- s9ymdb:168 --&gt;&lt;img width=&quot;71&quot; height=&quot;110&quot; src=&quot;http://blog.proculo.de/uploads/Messages_NoKeyboard.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;serendipity_imageComment_txt&quot;&gt;Viewing messages, keyboard not shown.&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;serendipity_imageComment_left&quot; style=&quot;width: 142px&quot;&gt;&lt;div class=&quot;serendipity_imageComment_img&quot;&gt;&lt;a  class=&#039;serendipity_image_link&#039;  rel=&#039;lightbox&#039; href=&#039;http://blog.proculo.de/uploads/Messages_WithKeyboard.png&#039;&gt;&lt;!-- s9ymdb:169 --&gt;&lt;img width=&quot;71&quot; height=&quot;110&quot; src=&quot;http://blog.proculo.de/uploads/Messages_WithKeyboard.serendipityThumb.png&quot; alt=&quot;&quot;  /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;serendipity_imageComment_txt&quot;&gt;Keyboard displayed. The toolbar moves up, attached to the keyboard.&lt;/div&gt;&lt;/div&gt;&lt;/p&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;
&lt;br /&gt;
Although my first instinct was to simply use an implicit animation using &lt;code&gt;&lt;a href=&quot;http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIView_Class/UIView/UIView.html&quot;&gt;UIView&lt;/a&gt;&lt;/code&gt;&#039;s &lt;code&gt;&lt;a href=&quot;http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIView_Class/UIView/UIView.html#//apple_ref/occ/clm/UIView/beginAnimations:context:&quot;&gt;+beginAnimations:context:&lt;/a&gt;&lt;/code&gt; method, I decided to quickly search the web for some information on how other developers approached this problem.&lt;br /&gt;
&lt;br /&gt;
The results were a little surprising, possibly because the proper way to do it wasn&#039;t as easily available before iPhone OS 3.0 - various people on different message boards and mailing lists suggested a hack that involved looping through all instances of &lt;code&gt;&lt;a href=&quot;http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIWindow_Class/UIWindowClassReference/UIWindowClassReference.html&quot;&gt;UIWindow&lt;/a&gt;&lt;/code&gt; to find the one containing an instance of &lt;code&gt;UIKeyboard&lt;/code&gt;, a private class that isn&#039;t even documented in the iPhone SDK. Those hacks then proceeded to modify the dimensions of the view that contains the keyboard and adding the &lt;code&gt;&lt;a href=&quot;http://developer.apple.com/iphone/library/documentation/UIKit/Reference/UIToolbar_Class/Reference/Reference.html&quot;&gt;UIToolbar&lt;/a&gt;&lt;/code&gt; instance as a subview, so it would animate into the key window right along with the keyboard.&lt;br /&gt;
&lt;br /&gt;
Needless to say, these hacks are not exactly future-proof or what I would consider a proper implementation of this feature. The &lt;a href=&quot;http://en.wikipedia.org/wiki/Core_Animation&quot;&gt;Core Animation&lt;/a&gt; route was the one to go, so I proceeded in that direction.&lt;br /&gt;
&lt;br /&gt;
More about this after the jump. &lt;br /&gt;&lt;a href=&quot;http://blog.proculo.de/archives/178-Attaching-a-UIToolbar-to-the-iPhones-Keyboard.html#extended&quot;&gt;Continue reading &quot;Attaching a UIToolbar to the iPhone&#039;s Keyboard&quot;&lt;/a&gt;
    </description>
</item>

</channel>
</rss>
