Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Web services are good, but is it necessary?

Web services are good, but is it necessary?

Scheduled Pinned Locked Moved The Lounge
questionmobilewcfbusinessdiscussion
7 Posts 6 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V Offline
    V Offline
    Vijay Rajanna
    wrote on last edited by
    #1

    Hi, Recently I was having a discussion with my colleague, to provide a mobile app to access a remote device which we frequently work with at office. and hence to provide basic functionalitues within the app. For this we need to implement a web service. Now the real question !! For the above idea, we need to implement a web service. However now the user is already able to access device over web portal within any web browser. So, the natural question.. WHY DO I NEED A MOBILE APP ? WHY SHOULD I IMPLEMENT A WEB SERVICE ? That's very much right. IF this is the question, then why do Facebook, twitter have web services.. ( there is always a browser to access ) Please provide me your inputs, which are those "MUST" requirements for web service ? Thanks.

    Regards, Vijay Blog : Amusement of a speculative mind...[^] Projects : Amusement of a dilettante mind...[^]

    P J V L M 5 Replies Last reply
    0
    • V Vijay Rajanna

      Hi, Recently I was having a discussion with my colleague, to provide a mobile app to access a remote device which we frequently work with at office. and hence to provide basic functionalitues within the app. For this we need to implement a web service. Now the real question !! For the above idea, we need to implement a web service. However now the user is already able to access device over web portal within any web browser. So, the natural question.. WHY DO I NEED A MOBILE APP ? WHY SHOULD I IMPLEMENT A WEB SERVICE ? That's very much right. IF this is the question, then why do Facebook, twitter have web services.. ( there is always a browser to access ) Please provide me your inputs, which are those "MUST" requirements for web service ? Thanks.

      Regards, Vijay Blog : Amusement of a speculative mind...[^] Projects : Amusement of a dilettante mind...[^]

      P Offline
      P Offline
      Pete OHanlon
      wrote on last edited by
      #2

      There are any number of reasons, but the most basic reason they offer them is so you can use their services in your applications. This isn't them being altruistic, there are cold hard business drivers in place such as building brand loyalty.

      *pre-emptive celebratory nipple tassle jiggle* - Sean Ewington

      "Mind bleach! Send me mind bleach!" - Nagy Vilmos

      CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

      1 Reply Last reply
      0
      • V Vijay Rajanna

        Hi, Recently I was having a discussion with my colleague, to provide a mobile app to access a remote device which we frequently work with at office. and hence to provide basic functionalitues within the app. For this we need to implement a web service. Now the real question !! For the above idea, we need to implement a web service. However now the user is already able to access device over web portal within any web browser. So, the natural question.. WHY DO I NEED A MOBILE APP ? WHY SHOULD I IMPLEMENT A WEB SERVICE ? That's very much right. IF this is the question, then why do Facebook, twitter have web services.. ( there is always a browser to access ) Please provide me your inputs, which are those "MUST" requirements for web service ? Thanks.

        Regards, Vijay Blog : Amusement of a speculative mind...[^] Projects : Amusement of a dilettante mind...[^]

        J Offline
        J Offline
        Jarek Kruza
        wrote on last edited by
        #3

        Do some counting. Lest have package tracking application - user enters package number and application displays date sent, current status and expected arrival date. Data sent: let's say 20 bytes for number and 200 bytes of status/dates. Now try to count the overhead of html/images/etc and compare it to overhead of WebService envelope (if you will use JSON service it will be minimal...) If it's used frequently this sums up to quite big numbers. And it will be probably more user friendly as native app than web page (unless you will design mobile-oriented web UI). Convinced? ;)

        V 1 Reply Last reply
        0
        • V Vijay Rajanna

          Hi, Recently I was having a discussion with my colleague, to provide a mobile app to access a remote device which we frequently work with at office. and hence to provide basic functionalitues within the app. For this we need to implement a web service. Now the real question !! For the above idea, we need to implement a web service. However now the user is already able to access device over web portal within any web browser. So, the natural question.. WHY DO I NEED A MOBILE APP ? WHY SHOULD I IMPLEMENT A WEB SERVICE ? That's very much right. IF this is the question, then why do Facebook, twitter have web services.. ( there is always a browser to access ) Please provide me your inputs, which are those "MUST" requirements for web service ? Thanks.

          Regards, Vijay Blog : Amusement of a speculative mind...[^] Projects : Amusement of a dilettante mind...[^]

          V Offline
          V Offline
          V 0
          wrote on last edited by
          #4

          IMHO the big difference is your audience. Web site Anonymous users, you have no clue who will access your site and when. The goal of a web site is to allow users free access. You as the builder can change the contents whenever you like and how you like. In short:

          * for humans
          * many clients
          * free access
          * no guarantee on content

          Web Service The interaction with a web service is via a "contract." It is expected that you keep some backward compatibility when upgrading the services. In addition, most web services have a limited number of users and access is more tightly controlled (IOW less open). Web services are also more easily used by machines instead of humans (as were web sites are more human readable) in short:

          * for machines
          * fewer clients
          * limited access
          * content guaranteed

          There are more differences and the above is not the "law", but rather rule of the thumb, but I think it gives you an idea. hope this helps.

          V.
          (MQOTD Rules )

          1 Reply Last reply
          0
          • V Vijay Rajanna

            Hi, Recently I was having a discussion with my colleague, to provide a mobile app to access a remote device which we frequently work with at office. and hence to provide basic functionalitues within the app. For this we need to implement a web service. Now the real question !! For the above idea, we need to implement a web service. However now the user is already able to access device over web portal within any web browser. So, the natural question.. WHY DO I NEED A MOBILE APP ? WHY SHOULD I IMPLEMENT A WEB SERVICE ? That's very much right. IF this is the question, then why do Facebook, twitter have web services.. ( there is always a browser to access ) Please provide me your inputs, which are those "MUST" requirements for web service ? Thanks.

            Regards, Vijay Blog : Amusement of a speculative mind...[^] Projects : Amusement of a dilettante mind...[^]

            L Offline
            L Offline
            Lost User
            wrote on last edited by
            #5

            Well, if your users want an app, you should provide it. End of that discussion as the customer is always right. IF an app can look better / be more responsive /be seen as better by the users, then again, you need to do it. If you set up your web site to use the same web services then it's also a reasonably inexpensive route. Finally, depending on circumstances, having a web service means other devs can always add the functionality to their applications - so you can get more users that way too.

            MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')

            1 Reply Last reply
            0
            • V Vijay Rajanna

              Hi, Recently I was having a discussion with my colleague, to provide a mobile app to access a remote device which we frequently work with at office. and hence to provide basic functionalitues within the app. For this we need to implement a web service. Now the real question !! For the above idea, we need to implement a web service. However now the user is already able to access device over web portal within any web browser. So, the natural question.. WHY DO I NEED A MOBILE APP ? WHY SHOULD I IMPLEMENT A WEB SERVICE ? That's very much right. IF this is the question, then why do Facebook, twitter have web services.. ( there is always a browser to access ) Please provide me your inputs, which are those "MUST" requirements for web service ? Thanks.

              Regards, Vijay Blog : Amusement of a speculative mind...[^] Projects : Amusement of a dilettante mind...[^]

              M Offline
              M Offline
              Mark_Wallace
              wrote on last edited by
              #6

              Because there's no pissing about with waiting for customers to test updates on their systems (which always seem to be ****ed up). You just update the (fully tested) app on your server, and Bob's your system administrator.

              I wanna be a eunuchs developer! Pass me a bread knife!

              1 Reply Last reply
              0
              • J Jarek Kruza

                Do some counting. Lest have package tracking application - user enters package number and application displays date sent, current status and expected arrival date. Data sent: let's say 20 bytes for number and 200 bytes of status/dates. Now try to count the overhead of html/images/etc and compare it to overhead of WebService envelope (if you will use JSON service it will be minimal...) If it's used frequently this sums up to quite big numbers. And it will be probably more user friendly as native app than web page (unless you will design mobile-oriented web UI). Convinced? ;)

                V Offline
                V Offline
                Vijay Rajanna
                wrote on last edited by
                #7

                Hi, That is very convincing. Thanks.

                Regards, Vijay Blog : Amusement of a speculative mind...[^] Projects : Amusement of a dilettante mind...[^]

                1 Reply Last reply
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • World
                • Users
                • Groups