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
parent
Conversation 12 comments by 6 users
  • idlethreat
    +23

    Good artists copy. Great artists steal

    I think it might be worth the time and effort to check out Reddit's own API. You can probably come up with a list of core function ideas pretty quickly. You're doing a lot of the same stuff.

    Would probably recommend separate milestones for the api. milestone 1 will get a user logged in, read sort and post snaps. aim for 80% of site usability. Low hanging fruit. I think for milestone 1, the list will look like:

    * user auth

    * Ability to vote on all comments / snaps / text posts

    * Ability to comment on snaps / text posts

    * Ability to create text posts

    milestone 2 will get profile editing and tribe management, searching, etc, milestone 3 will get more goodies (the rest of the 20%).

    Document, document, document. Use something like Swagger to hold the docs. It's lovely.

    REST not SOAP. JSON not XML

    Sorry. sort of a brain dump. hope some of that's useful to ye.

    • typesprite
      +14

      That's a good brain dump imho!

      REST not SOAP. JSON not XML

      Was about to mention that, too. Can't be stated enough.

      • idlethreat
        +8

        Some people, when confronted with a problem, think “I know, I'll use XML.” Now they have two problems.

        I say that a little too much at work ;)

        • Kysol
          +4

          The XML implementation that was used where I work is a complete CF! The tools they wrote do "use" XML break because the people writing the tools don't understand XML. Not to mention how bloated it is, but it's a "standard" other people use it like Microsoft... blah blah...

    • [Deleted Profile]

      [This comment was removed]

    • jmcs
      +4

      Use something like Swagger to hold the docs. It's lovely.

      +1 to this swagger. There are several tools built around it.

      REST not SOAP. JSON not XML

      Just to add to this do proper REST. This is not proper REST, think resources/nouns not verbs, if you think your resources right the API will be easier to future proof. Consider using HATEOAS (with JSON) because it may make well implemented clients more resilient to changes.

    • hallucigenia
      +3

      JSON not XML

      I think that gets a big, fat "duh!" these days.