Results 1 to 5 of 5

Thread: Mobile Apps - native, web-based or hybrid?

  1. #1
    Join Date
    Sep 2010
    Posts
    66

    Mobile Apps - native, web-based or hybrid?

    The hype about the apps for the iPhone, Google Android and other mobile platforms Smartphone-Web applications are almost forgotten. Basically, both approaches are suitable for the development of business applications. The native mobile applications have been born out of necessity, because the PC usual organizer functions on the road should be available on the mobile device. So the first simple PDAs simply had no mobile phone module in the resulting company, smartphones could not rely absolutely sure that mobile data services anywhere in sufficient bandwidth available (and affordable) were. As a consequence, were the fat-client applications on the device offline, in the office might the information then synchronize with the office PC. With the dramatically increasing processing power of smartphones , the increased storage capacity and other components such as GPS or megapixel camera applications, the then more mature. At the same time allowed the third generation mobile communications (UMTS) and mobile access / transmission of data without significant delays. Celebrated their victory, the "Apps" ultimately with the popularity of the Apple iPhone and iTunes App Store, where 250,000 mobile programs can now download. The Apps euphoria has since led to such an extent that even recycled content of websites are stored in applications. They should thus be especially present with the user, open up new business or are simply the prestige of the publisher.

  2. #2
    Join Date
    Apr 2009
    Posts
    67

    Re: Mobile Apps - native, web-based or hybrid?

    Both apps and for Web-based applications, there arguments for a native fat-client application is the fact that it is also available offline, and can directly access the hardware of the equipment, as GPS or camera (barcode scanner) access . Moreover, it is possible to hold important data locally, which is not to neglect the increasing storage capacity of current devices and the growing capacity of MicroSD cards. The storage capacity can be simultaneously but also seen as a disadvantage. the device is lost, there is a risk that critical information may fall into the wrong hands. Moreover, the timeliness of the data - unlike browser-based applications - not always guaranteed.

  3. #3
    Join Date
    Apr 2009
    Posts
    37

    Re: Mobile Apps - native, web-based or hybrid?

    The possibility of an application specially adapted to a device or platform, is a double-edged sword. The manufacturer paid for the usability advantages obtained with a complex and often costly development, in addition, the code for other platforms, especially the iPhone , only partially re-used. At least in this context mobile Web applications are clearly superior. These are mostly existing Web applications that have been adjusted for the change of use and screen size of different devices. Because they make it with different platforms and form factors to address devices, apps are web-based and a good opportunity to present trend of IT Computerization to respond to: Users can keep their devices, and any Web-based applications load. A further advantage is no more complicated rollout is necessary, a notice sent by e-mail or text link will suffice. With no local installation is taking place, changes can also be made and implemented without fuss. The freshness of the data is not a problem as they are taken directly from the central database.

  4. #4
    Join Date
    Nov 2008
    Posts
    73

    Re: Mobile Apps - native, web-based or hybrid?

    The freshness of the data is not a problem as they are taken directly from the central database.
    But there are also disadvantages: need for a proper use of a high-performance network connection. This is in rural areas are still not standard, abroad, it can also cause high roaming costs. In addition, a Web-based app only partially able, the device features (email, phone book) to be integrated. In addition to the Web-based programs and apps, there are hybrid forms that combine the advantages of both styles or mitigate their respective drawbacks: It is already common that native applications can retrieve information or forward when a network is available. If no Internet access possible, the rich-client solution are often used yet complete, the data is synchronized at a later date.

  5. #5
    Join Date
    Apr 2009
    Posts
    69

    Re: Mobile Apps - native, web-based or hybrid?

    If no Internet access possible, the rich-client solution are often used yet complete, the data is synchronized at a later date.
    On the other hand, there are thin client solutions, the major disadvantages of Web-based applications make up and benefits of native apps use. Thus, the user interface is implemented directly in the application, in addition, the hardware of the device used to integrate more than HTML. Because less data to transfer content to thin client solutions typically with lower bandwidth, including work in areas where only GPRS and Edge networks are available. Which variant is chosen, the user must decide case by case basis. Despite the many opportunities now, this will be always a compromise, which is at the expense of effort, data timeliness, power function, usability and other factors.

Similar Threads

  1. Does Mozilla Firefox for mobile support native Sync?
    By Gridharan in forum Technology & Internet
    Replies: 3
    Last Post: 02-02-2012, 04:45 AM
  2. Sharp introduced Solar Hybrid mobile phone
    By Lucjan in forum Portable Devices
    Replies: 1
    Last Post: 18-05-2011, 02:38 AM
  3. Mobile .net Native Exception Error 0xC0000005
    By Kanan in forum Software Development
    Replies: 2
    Last Post: 04-06-2009, 08:07 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,710,841,081.44244 seconds with 17 queries