Besides the fact that I will not attend to the conference (for several reasons, mainly because it is too expensive) I am excited about the WWDC.

What are my plans for this year?

I definitely want to be in company while watching the keynote. In my opinion, it would be great if a "public viewing" would happen anywhere near me. Sadly, this is not the case and therefore I will watch with some friends and kind-of-coworkers.

My special interest lies in the session videos.
We have already heard that some are streamed live whereas others are released as soon as the decoded it.
So my WWDC will consist of watching videos in good company.

For the case that anyone is still interested in watching WWDC '14 videos, the next passage is for you.
If you stumbled over the fact that there is an iOS app but only a website for the Mac you will be delighted:
WWDC for Mac

Some great sessions I recommend (and have watched in the last month as well):

• 236: Building Interruptible and Responsive Interactions (great view into UIView animation and Core Animation)
• 404: Advanced Swift (with great power comes great responsibility, swift is more powerful than we (I) thought (held my Andy Matuschak who I am a fan of)
• 419: Advanced Graphics and Animations for iOS Apps (more Core Animation and what it takes to render a pixel, also interesting performance tipps and in-depth UIVisualEffectView)
• 235: Advanced Scrollviews and Touch Handling Techniques (very good structured and held talk, excellent to lean back and enjoy)

Your time is definitively not wasted at all if you watch the mentioned videos ahead of the upcoming conference!

However, I would love to have the opportunity to watch the videos at 2x (or at least ~1.7x) playback speed.
Due to the fact that I listen to podcasts at this speed, I became conformable with hearing and "parsing" the english language.
My workaround: download the files and play them using VLC Player (it can adjust the playback speed) and mirror the screen onto my  TV.
I would love to have an iPad app so my Mac can go to sleep but I haven't found any.
Please contact me if you have further information.

At the end of this entry I would like to point out the fact that I bite back from spreading my predictions about future products 😉

The article I talk about is this one.

The message (or at least what I took away from it):

Apples API is tempting to use but will most likely produce unrealistic and unnatural behaviors of you animation.

The main problem lies in the fact that you have to specify a duration and values like the initial velocity or the spring damping.

If you imagine a spring, you will find out that it has parameters (specified by geometry and the material) that you can't influence (damping) and others that you can affect (like the initial velocity).

However, the key is: You can not influence the duration, whilst the API requires you to specify it.

This will result in an over- or underdamping as you can see in the picture above.
You will most likely agree that it looks kind of wired.

Mike Rundle (the author of the mentioned article) suggests

If your element is moving 100px across the screen, and you choose a damping of .3, the only way to figure out the true duration of the movement is to do math on your own. If you just plug in a random duration, the feel of the entire animation will be off.

So we have two ways to solve our misery:

• We could calculate (well or just trial-and-error) the duration value
• We use UIKitDynamics which takes a little more effort to set up but will give us a lot more natural spring animation (by using the UISnapBehavior).

I would love to hear at WWDC 2015 that Apple has updated their API to not require the duration value at all.
But until then we have to be contented to use one of the above suggested solutions.

Actually it is my first article if you don't count the Lorem Ipsums.

What will I write about?
Well I have to admit that I am not quite sure. I started this project just because I wanted to implement a concept of a blog design.
Of course I am aware of the fact that nobody is attracted by this kind of opening post but that's how it started.

What will come next?
I am going to write about what comes in mind about iOS and design (well I said this already).

Now there it goes, finding out in which direction this project will go to.