Intested in generic "push service"?

Discussion in 'iOS Programming' started by mamcx, Apr 17, 2009.

  1. mamcx macrumors regular

    Mar 13, 2008
    After discover that devs will need to provide their own serves so push will work, I wonder if exist interest in build a kind of generic push service.

    I have some experience in this arena and have the rigth tech already, with compression, encryption, very fast binary transfer, support for several decoders like json/xml and so on.

    I'm exploring provide this service for a small fee, and take care of the developing & hosting of this.

    However, I want some input about this:

    - How much reliable must be (ie: expect 99,9...%?)
    - User cases
    - How much expect to pay for this kind of service
    - Any other input welcome!
  2. ravenvii macrumors 604


    Mar 17, 2004
    Melenkurion Skyweir
    I bet developers will come up with a open iPhone Notifications Service of some kind. Like OpenFeint or something.
  3. fishkorp macrumors 68020


    Apr 10, 2006
    Ellicott City, MD
    Each developer needs their own certificates and setup. It's not as easy as just saying "here you go, here's a push server." Many devs are having problems getting the provider working on their own, I can imagine it would be an even bigger nightmare trying to have someone else do it for you, or rely on something where you don't have control.

    However, I honestly believe that any app that will have a need for push already has a good enough server where the data is coming from anyway. It'll just get taxed a little more. I took push into consideration when I got my server package, so I've been ready for months now. I'm guessing most devs that need it have done something similar.

    Do you honestly have the resources to resell push servers where there are potentially millions of transactions being processed every x amount of time (app dependent of course)? Could be seconds, could be minutes, could be hours.
  4. mamcx thread starter macrumors regular

    Mar 13, 2008
    And which are that problems? If dev are havving problems with their provider (because?) how will be worst use aa provider that have the solution?

    I'm not pretending to be sarcatic, but understand this issue to know if is worth continue with the idea...

Share This Page