It started once when I used my iPod Touch: it would not be great to have the XXX function (from our internal desktop application) available on the iPhone as a native application.
I had this idea because (A) I think that our current bulky desktop with an internal 6+ year old desktop needs a major facelift and (B) instead of continuing with our waterfall development methodology, which usually led to the completion of the project after dozens of people spend months on what no user cares about. Hope we can use a lot of tiny projects with 2-week iteration cycles using the Agile methodology.
Oh, I also want to find an excuse for using Xcode in the office.
After researching, I found out that to a large extent, NO COMPANY makes apps for the iPhone’s intranet, because no company wants Apple’s internal development to kill interesting apps like Google Talk. Since our company is extremely concerned about safety and security, the phrase "using a jailbroken iPhone / iPod Touch" is similar to the phrase "please fire me."
So, I came up with plan B: using ComponentOne iPhone Studio to create a web application optimized for iPhone. I spent 2+ weeks and it was all over. My manager seemed to be very worried about this, so I hope we can turn it into a long-term project.
My question is: did you ask any of you to write an iPhone application (your own application or a web application) for internal use of your company and what are the technical and political problems?
source
share