AUG 18, 2014 6:04pm ET

Related Links

Big Data is More Than Just Hype
September 18, 2014
Conn. Attorney General Wants to Talk Privacy with Apple
September 17, 2014
More Than 75 Percent of Mobile Apps Will Fail Basic Security Tests
September 16, 2014

Web Seminars

Why Data Virtualization Can Save the Data Warehouse
Available On Demand
Essential Guide to Using Data Virtualization for Big Data Analytics
September 24, 2014

Mobile Apps Require New Development Methods

Print
Reprints
Email

The traditional methods used to define and develop desktop applications won’t work with mobile application development, according to research firm Gartner Inc. As demand from business units puts increasing pressure on IT organizations to deliver large numbers of mobile apps, development teams will need to employ practices that are different from traditional application development, the firm says.

Get access to this article and thousands more...

All Information Management articles are archived after 7 days. REGISTER NOW for unlimited access to all recently archived articles, as well as thousands of searchable stories. Registered Members also gain access to:

  • Full access to information-management.com including all searchable archived content
  • Exclusive E-Newsletters delivering the latest headlines to your inbox
  • Access to White Papers, Web Seminars, and Blog Discussions
  • Discounts to upcoming conferences & events
  • Uninterrupted access to all sponsored content, and MORE!

Already Registered?

Filed under:

Advertisement

Comments (1)
In some ways, I would say that the development approach for all applications needs to change. Especially applications that need to be delivered fast. Even with agile, relying solely on IT for developing apps has not overcome the backlog of app requests that most organizations have. We need to move to a model that more effectively integrates the business into app dev - whether that is using a cloud based solution that makes it possible for a technical business user to create apps, or more effectively involving the business into the application model definition.

From a mobile perspective, there are definitely differences in the UI presentation - as is there a need to consider differences between different mobile devices - tablet vs. phone, iOS vs. Android. One possibility to consider is an approach that will allow you to do rapid prototyping. But the completed prototype shouldn't be a disposable asset. With some aPaaS solutions, your prototype is actually a fully working solution.

For more thoughts on mobile - why mobile-first is potentially flawed, check out...http://bizappstoday.progress.com/2014/07/mobile-approach-short-sighted.html

Thanks,

Mark Troester Progress Software @mtroester

Posted by Mark T | Tuesday, August 19 2014 at 4:47PM ET
Add Your Comments:
You must be registered to post a comment.
Not Registered?
You must be registered to post a comment. Click here to register.
Already registered? Log in here
Please note you must now log in with your email address and password.
Twitter
Facebook
LinkedIn
Login  |  My Account  |  White Papers  |  Web Seminars  |  Events |  Newsletters |  eBooks
FOLLOW US
Please note you must now log in with your email address and password.