Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 5972047
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T20:36:10+00:00 2026-05-22T20:36:10+00:00

I still don’t get it why Apple discourages the old method of doing animations

  • 0

I still don’t get it why Apple discourages the old method of doing animations and instead says to use blocks.

I mean, how does one realistically stop using the old way? Aren’t blocks iOS > 4.0 only? Is one supposed to fill the code with ifs and make two different implementations based on the current device’s system version? And why do so since the old method works just fine? Plus the underlying implementation should be the same, right? Is there any reasoning behind this aside from the fact that begin/commit produces ugly code?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-22T20:36:11+00:00Added an answer on May 22, 2026 at 8:36 pm

    I still don’t get it why Apple
    discourages the old method of doing
    animations and instead says to use
    blocks.

    Apple wants you to use the latest and greatest techniques. Apple will optimize all it’s new iOS releases for the block based animations and probably will add new possibilities only to the blocks based animations. So thats why Apple is pushing you to the block based animations.

    I mean, how does one realistically stop using the old way? Aren’t blocks iOS > 4.0 only?

    Yes, blocks are iOS > 4.0 only. So if your App is designed for iOS 4.0+ only you can use block based animations. Or you could check for the availability of blocks and add the specific animation only for the iOS 4.0+ devices.

    Completely stop animating the old way is only realistic if you drop support for iOS 3.

    Is one supposed to fill the code with ifs and make two different implementations based on the current device’s system version? And why do so since the old method works just fine? Plus the underlying implementation should be the same, right? Is there any reasoning behind this aside from the fact that begin/commit produces ugly code?

    Well, if the old method is okay for you and you want to support older (iOS 3) devices. Just use the old way of animating. There’s nothing wrong with it, don’t put unnecessary if-statements in your code. It only makes things complicated and you win nothing by doing it.

    If your App is iOS 4 go with blocks, it’s shorter and somewhat cleaned. It also should be easier to maintain, because Apple will not keep updating the old way of animating.

    (You always can add the if-statements somewhere in the future if there will be animations you only can do with blocks, and then fallback to another less complex animation with the old methods. But thats something for the future.)

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Something I still don't understand when performing an http-get request to the server is
It seems I still don't get generics ... I want a general function to
I've seen many Tutorials about the MVVM-Patern but I still don't get why I
I want to run tcpdump with some parameters (still don't know what to use),
I still don't quite get it, where to put images in rails 3.1, in
I guess I still don't get git as I'd hoped... I was creating a
After reading : this I still don't get it. in console: puts Category.joins(:posts) It
there is something i still don't get. for every class i declare there is
I've been reading for an hour now and still don't get what is going
I've read all the other threads but I still don't get why my apps

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.