Android developers could respond to user reviews on Play Store for years now. They could even share their contact information to provide additional support. iOS developers have been asking for a similar, if not better, option for apps on the App Store too. Our prayers seem have answered with iOS10.3, which is in beta currently. However, in typical Apple style, the problem has been tackled differently.
Parse’s announcement that it will be winding down has surely come down as an unfortunate surprise to a lot of app developers especially indie developers who found the holy grail in Parse. Lot of well known apps have been written with Parse as a backend and there are still quite a few apps with millions of installations that are using Parse as the backend. It appears that Facebook has mercilessly pulled the rug from under these app developers.
Why was a Swift developer arrested on the beach?
Because he thought clothing was optional.
Traditionally, we have all dealt with variables as having some value at any point in time during the execution of the program and use them assuming they will contain some value.
Error handling is one of the fundamental concepts of programming. A program without error handling is like a country without a justice system. Your app will behave in an unruly manner with no one to bring order to the program.Any programmer worth his salt should handle errors in his/her code.
Often times we find ourselves in a situation wherein the project has to be configured to make use of different provisioning profile and signing certificates and also with different bundle identifiers. The source code is maintained in a distributed and the vendor and the client make their own builds using their respective profiles, certificates and app ids.
This article explains the strategy that an app developer can adopt for working with different server configurations, without having to create multiple builds of the app pointing to different servers.