Idea: Glitch for services


#1

Perhaps team up with PostMan or something and have another site - only this is for all the cool (faceless) services that folks are creating on Glitch! Right now you have to have some kind of base page which is cool, but it would be awesome to be able to browse and try out all the cool services / json emitters that are here.


#2

I agree. One of the things I loved about Glitch was the free instance, pre-installed tools, the editor, etc.

But I do not code things that have a visual thing (like animations, 3d, etc). Instead I use Glitch for system tooling, prototyping, bots, HTTP services, etc.

I’m aware of the impact of 3d or floating stuff has on newcomers, but I think there’s also a big community of people using Glitch just for these kind of services.


#3

that makes sense,

historically we put stuff like that into categories like https://glitch.com/building-blocks, or https://glitch.com/tools-for-work , but it’s kinda clunky to find. I’d love to hear any ideas in terms of what you’d like to see/find things. Are there other sites that do discovery of service based apps well?

thx


#4

Here’s a place where you could be innovative like you were with version control. Come up with a really easy to use and play with API browser and even throw in some IFTTT style connections . I’ve always had a dream where I could see a website, flip it over like a piece of paper and see 1) sourcecode 2) images 3) services. Here’s an article about some API documentation sites https://opencredo.com/rest-api-tooling-review/

YQL had an amazing “YQL console” that let you browse and build data driven sites really fast – it was way ahead of it’s time and is lost now… This could be a killer app for Glitch… http://www.yqlblog.net/blog/2013/08/28/unified-yql-console-2/


#5

Here’s a tutorial that is using “Swagger” to help set up the API – looks like a promising approach https://docs.microsoft.com/en-us/windows/uwp/get-started/get-started-tutorial-fullstack-web-app


#6

Cool suggestions,

To get at your paper metaphor, one of the things we’ve talked about is add data about the packages a project uses to the api, and thinking about neat ways to expose that info in a way that’s feels relevant and not overwhelming – and from that, expose other ‘related’ applications that use the same packages/services.

Generally, making more project metadata data accessible via the api will enable other people to build unique discovery tools/dataviz things too