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
  • drunkenninja
    +30

    I think you're on to something, definitely more phases / iterations would be beneficial in speeding up the creation of the API so that devs can get started with the basics and then adding functionality as we fine tune and release updated versions. Anyone else agree with this? or not agree for that matter?

    • DesiDrifter395
      +11

      I'm not a developer, but I really like the phases setup like this. I think the first priority should definitely be to get something in place that'll allow users to login and read posts from tribes they are subscribed to. I'm okay with this phase layout, but I think the optimal first phase would be a combo of 1 and 2.

    • redalastor
      +6

      Taking into account that phase 1 should enable the creation of a decent mobile viewer, I'd add one thing : requesting an authentication nonce. That way the app could link the user to the right web page ready to comment or do whatever, pre-authenticated.

    • caelreth
      +6

      Yes, I think short iterations so that devs who want to use the API can get started sooner is the way to go.

    • Vind
      +5

      I agree with this. Although I would personally prefer the original post way of doing it, but this could be a good start.

    • DunkEgg

      This comment has been removed

    • skully (edited 3 years ago)
      +4

      I think /u/jrmy's list is a good one, with one caveat: I think creating text posts should be part of the same phase as creating snaps. From a (non-programmer) user's perspective it would be weird and frustrating if I could post text posts but not snaps.

      • jrmy
        +4

        The only reason I left out posting snaps was due to my perceived level of effort needed to support a snap vs a text post. With snaps having modules, etc, I could foresee that being an issue. But, now that I think about it, there is no reason you couldn't provide a limited snap posting release that doesn't include most of the modules.

    • brahle
      +3

      Yeah, I agree with that.

      Facebook did it with their Platform and it seems like it's what made the whole thing work.

    • imnotgoats
      +3

      I think this makes sense, although I'd add the ability to create snaps somewhere in there (possibly just an oversight). Also, I'd give tribe management it's own later phase as I don't think it should hold up 'profile overview' and PMs. It's a social community after all.