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.
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...
Wild card SSL certs are cheap these days, there is no excuse to why someone wouldn't be rocking an SSL cert on their site these days. The excuse of "extra load on the processors" was dead 10+ years ago.
well if they were to put the API on api.snapzu.com, have a developer portal and so on they might branch into a few different subdomains, so rather than pay $35 odd per domain variation, I thought that I'd throw out the wildcard info since it's $150 I think I bought my last one for.
If they go with Cloudflare, they basically get free SSL as well.
okay. 150 is a lot less than when I looked at them last. They originally were going for 1500 bucks a pop. Did a quick check and the cheapest I found were 500 bucks. But, I don't shop for a whole lot of SSL certs- whenever I need one, I normally just get one from startssl, or use whatever company's cert I'm working with.
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.
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.
[This comment was removed]
[This comment was removed]
+1 to this swagger. There are several tools built around it.
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.
I think that gets a big, fat "duh!" these days.