Mail.Ru Agent for iPhone - first experience
Our attempts to penetrate the iPhone, finally, were crowned with success: today, Apple has started Mail.Ru Agent for placement on the App Store (after two rejects).
I would like to say a few words about our first experience. In general, the idea of ​​Apple to control software for its device is quite understandable and reasonable from a business point of view. But in embodiment, it seems to me, there are two noticeable shortcomings.
1. Applications are considered very long. In total, the procedure of the device took us exactly 7 weeks (almost 2.5 weeks for each build). And the fix of those small “jambs” that became the cause of the reject, in each case, took only a couple of hours along with testing. The rest of the time, we just waited for the reaction of Apple. As a result, iPhone users got the product they needed almost 2 months later than they could.
')
At the same time, even minor changes require the passage of a full revision from scratch. In other words, if we find some critical problem in the application, if we want to add some small feature to it, satisfying the massive feedback of users, we will not be able to do it “right tomorrow”. Willy-nilly, developers are forced to "consolidate" releases instead of more frequent release of new versions as they implement features.
2. All applications are reviewed on a general basis. This is rather strange, but services such as Facebook, Skype, Yahoo, Gameloft, or Mail.Ru are in the same queue with an avalanche of thrash applications, such as an emulator of pimply packing tape on the iPhone’s display (namely, the App Store consists of my, a little less than full).
I understand that the criteria for separating the “majors” from the “non-majors” are quite vague, but in the interests of Apple itself, to do something about it - it is clear that first of all you need to deliver to the market (sorry for the pun) the applications used millions, not a couple of people in the world. In general, it seems to me that this is not exactly the case where “equality” is needed - as a user, I’m interested in the opposite.
Both of these problems in aggregate rather significantly slow down the development and deployment cycle, and I think that in the future (especially if the iPhone software market continues to grow) this can become a rather serious competitive disadvantage compared to, for example, the Android Market (although the latter of course, it’s still pretty dry, and its prospects are foggy).
Let's hope that over time, Apple somehow change this situation.
I would like to say a few words about our first experience. In general, the idea of ​​Apple to control software for its device is quite understandable and reasonable from a business point of view. But in embodiment, it seems to me, there are two noticeable shortcomings.
1. Applications are considered very long. In total, the procedure of the device took us exactly 7 weeks (almost 2.5 weeks for each build). And the fix of those small “jambs” that became the cause of the reject, in each case, took only a couple of hours along with testing. The rest of the time, we just waited for the reaction of Apple. As a result, iPhone users got the product they needed almost 2 months later than they could.
')
At the same time, even minor changes require the passage of a full revision from scratch. In other words, if we find some critical problem in the application, if we want to add some small feature to it, satisfying the massive feedback of users, we will not be able to do it “right tomorrow”. Willy-nilly, developers are forced to "consolidate" releases instead of more frequent release of new versions as they implement features.
2. All applications are reviewed on a general basis. This is rather strange, but services such as Facebook, Skype, Yahoo, Gameloft, or Mail.Ru are in the same queue with an avalanche of thrash applications, such as an emulator of pimply packing tape on the iPhone’s display (namely, the App Store consists of my, a little less than full).
I understand that the criteria for separating the “majors” from the “non-majors” are quite vague, but in the interests of Apple itself, to do something about it - it is clear that first of all you need to deliver to the market (sorry for the pun) the applications used millions, not a couple of people in the world. In general, it seems to me that this is not exactly the case where “equality” is needed - as a user, I’m interested in the opposite.
Both of these problems in aggregate rather significantly slow down the development and deployment cycle, and I think that in the future (especially if the iPhone software market continues to grow) this can become a rather serious competitive disadvantage compared to, for example, the Android Market (although the latter of course, it’s still pretty dry, and its prospects are foggy).
Let's hope that over time, Apple somehow change this situation.
Source: https://habr.com/ru/post/76490/
All Articles