Geek Answers Handbook

Writing Clean, Perfect Code for iPhone

I have been developing on the iPhone using Objective-C for several months, and I am applying the best practices learned and improved when developing Java applications. These include: designing classes that have a single responsibility, applying design patterns where necessary, and writing short methods that do only one thing. For me, these methods are useful from the point of view of clean-code and to a large extent are domain agnostics.

I was pleased with the results. However, some iPhone developers have advised me to abandon this because they say that I write too many classes and too many methods. At different times they warned me:

  • Stack will hit
  • Too many classes will slow the iPhone down (i.e. a noticeable user)
  • Nested method calls will degrade performance (e.g. user)

In practice, I did not encounter these problems. If you look superficially at some iPhone performance indicators , it seems to me that additional method calls and object life cycle overhead are necessary to implement common templates and short methods is unlikely to create any noticeable delay for the user. However, the advice of other iPhone developers scared me a bit.

I would like to continue studying and improving the methods of agnostic domain programming that have served me well in the past, but when developing on the iPhone I don’t want to go the route that will end in pain!

, , ? :

- (, , )

+5
4

. .

, , , , . !!!

, opebGL, . . , , , . .

, / ( , , , , ) , , .

+1

OO - , - , . -, , , ( ) .

, , , , , ( , , OO!). , (LOTS) .

- . , , , ( ), , , . ( , , !)

"" , , , .

+1

Blackberry. , .. , , . OO (, , ..). "" . , . - , , , . , - , . , . , , , , - ...

+1

: . , , - , , . Obj-C 3D- .

, , , .

0

More articles:


All Articles