1,419 karma · joined August 1, 2013
Additionally, if you're a backend engineer looking to build incredible developer experiences - DM me twitter.com/pavtalk
But it wasn't exactly the business we signed up for when we started - see here https://www.blockspring.com/blog/blockspring-team-is-joining....
Joining Coinbase was no-brainer. Huge mission, excellent team, and high impact API + dev experience work.
Btw - we're hiring :)
POST requests with Google Sheets is generally a bad idea since you can't explicitly control when they're sent.
- Manually specifying layers in the image by depth.
- Manually specifying all the objects you'd want to animate.
- Providing an animation direction and type.
Then it generates an animation?
A common usecase on Blockspring for Google Sheets [1] is to pull data from various APIs to build lead lists for sales and recruiting.
However, combining lists is actually time consuming in spreadsheets. Lots of importing CSVs or VLookups.
So since we built a knowledge graph around what types of information APIs return, and are now able to help you collect the data you want (eg company names, locations, etc), as well as suggest enrichments based on what you have (eg go from companies -> profiles -> interests, etc).
This is great if you're a startup founder, freelancer, or starting up a new sales/recruiting process and need to quickly build your own lead lists! Let us know what you think.
You're right -- since these apps don't (yet) embed our SDK in to their site, we need to get the current state (eg current page, selected table, etc) from the Chrome Extension. But our goal is to provide entire entire extensibility platform in an embeddable JS snippet, so hopefully that won't be the case long.
- Build a Mail Merge add-on for Airtable in 2 Minutes: https://www.youtube.com/watch?v=ahG935eGnb4
- Build a Sheets Importer/Exporter for Trello in 60 Seconds: https://www.youtube.com/watch?v=mqcD6Qrc3Ck
UPDATE: changed a bit of content on page to reflect this.
https://community.blockspring.com/t/starlet-collector-create...
Click to update all the repo star counts in a README.md, and push a new commit.
The primary features are meant to make API development much better:
- Sign in with X instead of setting up OAuth flows or auth.
- Webhooks are built in, so you don't need a server to catch.
- API docs autocomplete. No need to dig through them.
- It's Serverless. Deploy your add-on on save.
It's inspired by Google Apps Script, the platform that powers all Google Docs add-ons. Hence less like Greasemonkey in that it uses real APIs under the hood, and less like Zapier in that it's for building add-ons instead of event pipelines.
a) UX for "hold while talking"
b) Known quality of the headset
From the outside, it looks a bit shady, and a bit un-Googlelike just to compete with Apple.
I imagine a more Google-like approach would've been to release Translate as a local model (eg like https://developers.google.com/vision/). It's easy to imagine the community would quickly figure out a way to solve a) and make the experience work for most headsets.
The "translate conversations in real-time" part seems to have nothing to do with the Google Pixel Buds - it's already live in the Google Translate app.
In fact, you can try it right now. Open the Google Translate app on android, put on a pair of headphones with a mic, and tap the audio translation. As you hear spoken word in another language, it'll translate in realtime back to your non-google headphones.
*note - The trick is you need to press the button so it enables translation across both languages, as that seems to be the only way to keep translation on even after the first phrase.
In fact, you can try it right now. Open the Google Translate app on android, put on a pair of headphones with a mic, and tap the audio translation. As you hear spoken word in another language, it'll translate in realtime back to your non-google headphones.
*note - The trick is you need to press the button so it enables translation across both languages, as that seems to be the only way to keep translation on even after the first phrase.