Client and server development
These elements are seen as separate parts of the process but are obviously very complementary.
Some apps, like TripCase, have a server side to the development. You need to define this as part of the overall product definition.
This server side is a learning curve for every developer, even if they’re a master in another technology outside of mobile.
Most developers don’t have pre-set limitations on client or server side, but for mobile you need to think very differently.
Because of that, and the bugs that will arise, testing is very important in your development process.
Be strategic when you think about they type of app you’re building. How will it affect partnerships (api’s, data sharing etc) and the business model?
The Apple framework SDK that is provided can be used to build everything you want for a basic app.
The XCode coding base provides a visual tool but it might be limiting for what you want your app to be, so challenge yourself to think outside of those guidelines.
For example:
You will have more control over the UI if you don’t use the builder and it would be easier to contain
We might recommend coding the UI yourself because it will allow you the flexibility for custom components. More control allows you to change things easier.
Custom component design will force a developer to think differently to stretch the imagination of the components
Make your own components so that they don’t always look standard. Ie: our main screen is custom. TripCase is a functional application, not a game etc so again it goes back to product definition, but some developing is more intense.
Client and server development.
These elements are seen as separate parts of the process but are obviously very complementary.
Some apps, like TripCase, have a server side to the development. You need to define this as part of the overall product definition.
This server side is a learning curve for every developer, even if they’re a master in another technology outside of mobile.
Most developers don’t have pre-set limitations on client or server side, but for mobile you need to think very differently.
Because of that, and the bugs that will arise, testing is very important in your development process.
Be strategic when you think about they type of app you’re building. How will it affect partnerships (api’s, data sharing etc) and the business model?
The Apple framework SDK that is provided can be used to build everything you want for a basic app.
The XCode coding base provides a visual tool but it might be limiting for what you want your app to be, so challenge yourself to think outside of those guidelines.
For example:
- You will have more control over the UI if you don’t use the builder and it would be easier to contain
- We might recommend coding the UI yourself because it will allow you the flexibility for custom components. More control allows you to change things easier.
- Custom component design will force a developer to think differently to stretch the imagination of the components
- Make your own components so that they don’t always look standard. Ie: our main screen is custom. TripCase is a functional application, not a game etc so again it goes back to product definition, but some developing is more intense.
NB: This How To series is authored by Robyn Grassanovits, Amy Dillon, Brian Knorr, Dr Maher Ali, Shannon Mihalakos and Carmen Velazquez of
TripCase - an iPhone app to handle trip and itinerary management by
Sabre.