September 2005
Intermediate to advanced
328 pages
7h 7m
English
book
Symbian for Software Leaders: Principles of Successful Smartphone Development Projects
by David Wood
Content preview from Symbian for Software Leaders: Principles of Successful Smartphone Development ProjectsBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Part 3. Symbian's design philosophy
Design goals for Symbian OS
The birth of EPOC32
Defining the EPOC RISC architecture
Software goals from 1995
Separating the engine
Nine passions
16 Designing for efficiency
The original electronic organizers
Limits of Moore's Law thinking
Causes of code bloat
Designing algorithms
Understanding the compiler
Adopting OO
Selecting C++
Text descriptors
17 Designing for robustness
Alloc heaven
Expecting the unexpected
The perils of multitasking
Exception handling
Common mistakes in destructors
Seeking out failure cases
Attitudes towards defects
Protecting the smartphone vital assets
18 Designing for usability
"The operation was a success, but the patient died"
Enchantment
Designing the user interface
Multimedia performance
Understanding the real competition
Customer orientation for developers
Designing panics
19 Designing for longevity
Preparing for variants
Be ready to fail fast
Prepare your own SDK
The value of codevelopment
Basic principles for reusable solutions
The value of architecture
The value of ignorance
20 Designing for smartphones
The licensing question
Focus on strategy
Smartphone heritage
Active objects
Power management
Beware stray signals
Final comments on asynchronous events
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.