LOUNGE all new asksnapzu ideasforsnapzu newtribes interesting pics videos funny technology science technews gaming health history worldnews business web research entertainment food living internet socialmedia mobile space sports photography nature animals movies culture travel television finance music celebrities gadgets environment usa crime politics law money justice psychology security cars wtf art google books lifetips bigbrother women apple kids recipes whoa military privacy education facebook medicine computing wildlife design war drugs middleeast diet toplists economy fail violence humor africa microsoft parenting dogs canada neuroscience architecture religion advertising infographics sex journalism disaster software aviation relationships energy booze life japan ukraine newmovies nsa cannabis name Name of the tribe humanrights nasa cute weather gifs discoveries cops futurism football earth dataviz pets guns entrepreneurship fitness android extremeweather fashion insects india northamerica
  • cyansmoker

    As others have already said, a REST API would be the proper way to go. Not only is it "pure" enough to allow the API to evolve over time, you can find libraries to consume REST APIs on every platform (desktops and mobile devices)

    I would also suggest a more "Agile" approach: rather than "initial release" v. "the rest" I think you should try to release early, a very focused set of features, and have sprints to allow you and us to sync. on the best direction for the API. If that's OK, obviously :)