Show HN: InboxSDK by Streak (YC S11) – Build Apps inside Gmail
inboxsdk.com
inboxsdk.com
This is a total game-changer. Very excited to see what the inbox will become thanks to the Streak team.
Cheers!
And of course you can check out the DocSend extension here to get insight into page-by-page engagement with your document attachments :) https://chrome.google.com/webstore/detail/docsend-extension-...
What I am really dying/desperate for is a group chat feature within Gmail where the chat rooms are permanent. I thought it was the biggest opportunity for years. Slack built a billion $ plus business of group chat outside of gmail. I am sure there is a reasonable sized opportunity for group chat within Gmail!
Besides not having to keep up with breaking changes in Gmail, another really nice benefit of using InboxSDK is that you don't have to keep updating your extension to make sure that it plays nice with other extensions. This was an unexpected and on-going source of development work for us previously.
Looking forward to the Google Calendar integration :)
File: https://www.inboxsdk.com/build/inboxsdk.js
Then I see the github page: https://github.com/InboxSDK/
There is no InboxSDK project but, just two example chrome plugins using the inboxSDK.
All the trappings and mechanics of open source without the actual source and an actual open source license. Are you guys just testing this to see if you can productize it? Or are you going to go all the way and open source this?
We're adding licenses to our examples that we have on GitHub and we're also adding a pointer from our inboxsdk.js file to our terms of service.
Over a longer time horizon, we plan on open sourcing the entire implementation of the InboxSDK but just not yet.
(I don't know what you're talking about.)
Therefore it is, essentially, open source.
Happy to answer any questions about the SDK.
Google will need to do something really intrusive to break their SDK
We think you can trust the platform because we're fundamentally making Gmail better and more valuable to Google's users. There are a handful of successful businesses (like Streak and others) already built on top of gmail and have been for years. These venture backed companies already trust their business to be on top of Gmail. We're just making the process of building these apps waaaay easier.
We take security and performance really really seriously. Because our SDK helps you build Chrome extensions for Gmail, Google can (and has) shut down shady apps from the Chrome Webstore, so they don't have to shutdown the entire platform to get rid of a bad actors.
I absolutely commend you for what you are doing, I just wouldn't be willing as a developer to dip my toes in that particular water to spend the time developing something they could rip apart and break.
As a side note, the documentation page is broken on Mac Safari 8 on OSX Javascript error:
TypeError: undefined is not a function (evaluating 'reference.endsWith('()')')
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
Do you have any notion of how fragile things are when dom-hacking? Do you have to constantly keep up with google's updates or are things fairly stable? i.e. how often will I need to update and/or patch an extension to maintain support (in your experience so far)?
In the last 6 months we've seen 0 breaking changes, 1 in the 6 months before that (it was fixed before the change even reached users), and 2 in the prior 12 months (where our fix reached product in sub 10 minutes).
Wow. Nicely done!
i) Are you planning to make the whole implementation Open Source?
ii) Say I wish to adopt and use your SDK in my current Gmail/Inbox extensions (>100K daily users), may I expect the implementation of a fixed upper limit on the number of transmissions in the coming months (which could endanger the reliability of my service for my users)?
iii) While the SDK currently only focuses on the UI, are you planning to add more "complex" interactions, such as Gmail filters/Gmail preferences ? If yes, feel free to get in touch. I will be happy to help.
Congrats, again.
ii) The SDK loads a static JS file so we aren't really worried about having a lot of users requesting that. We're hosting the SDK on appengine so I wouldn't expect any caps on users or anything like that. Dropbox has a ~500K weekly actives (as you can see from the chrome webstore: https://chrome.google.com/webstore/detail/dropbox-for-gmail-...) using it and I expect that to grow.
iii) can you describe the use case a bit more? Specifically are you looking to get the set of filters or add new ones or both? On the preferences side, are you looking to add your own? We have this functionality in Streak but haven't yet ported it over to the SDK (but will soon)
InboxSDK was obviously a ton of work. What is your business model for it?
As for business model, we aren't really thinking about that too much, we just knew how much pain ppl went through making gmail apps and just knew that the SDK needed to exist. We don't plan on charging for it.
We've talked a lot about doing an appstore inside gmail. The idea being that apps could opt in to be in the appstore. If you opt-in then your app automatically adds the appstore to your users gmail experience. That would help drive traffic to apps. Once a user installs any one of the apps, they have access to all the other apps in the appstore.
Definitely a lot better than using gmail.js
We're trying to take a slightly more higher level approach but there's def still a few things we're missing that gmail.js does have.
Lost interest halfway through, I think (there are no controls).
We used InboxSDK to create part of our DocSend Chrome extension. Our power users who are in gmail 24/7 can't live without it. Thanks to Streak for helping us enable our user base and keep happy customers happy! :)
I'm looking to build a plugin that can automatically send a mail back under specific conditions and allows follow-ups, but I'm not sure what tech I should use.
Even for our simple use case, which is essentially a button that makes an HTTP request to a web service with the email fields, it felt limited.
It also suffers from poor debugging tools. They made some changes that broke our gadget (I think it was the deactivation of OAuth 1.0) and there's no way of knowing why it isn't loading, it just doesn't.
If I remember correctly they are building a base email application that can be extended with plugins (like the atom editor). This does require people to adopt their email client.
The InboxSDK takes a different approach in that it lets you extend Gmails functionality and write apps for Gmail. End users don't have to switch their email client (assuming their using the gmail web client)
Build on top, reuse, don't copy-paste!
What's going to happen with the rumored update? I've been hearing rumors for over a year now that gmail, calendar, contacts and even tasks are being majorly overhauled; is there any collaboration with Google to make sure when (or if) these rumors come true that it won't simply break everything day one?
Trying not to be a nay sayer; this is a great idea if you want to quickly add something to Gmail without messing with the Gmail DOM yourself but it doesn't seem to be a good long term bet to me.
Google is the platform owner and may change it without prior notice. My interest is in understanding how would someone using this sdk would be impacted.
Thanks for making this.
If you try to make the top html tag as your root you'll probably run into a bad time particularly if other extensions make the same assumption. One major difference between writing an app for Gmail vs your own app is that multiple apps can and usually are running at the same time. This was one of the main motivations behind the SDK since many of our bug reports were a result from extension compatibility issues.
We do e2e testing with selenium/webdriver - so it's definitely doable. Tip for e2e testing is to pay for some extra Google Apps accounts so you can run your tests in parallel.
Also innovation isn't the idea. Innovation is actually implementing it.
Perhaps "revolutionary" is just marketing fluff, but why get hung up on subjective semantics?