I find "X does Y, why don't you?" As a means to keep vendors from becoming complacent. As customers, we don't know what the tools limits are. Sometimes, vendors will not invest in improving their tools/results without a credible threat. The results from competing vendors is the closest you can get to impartial results that create pressure to perform.
Sorry for the grim outlook - I think you will get shutdown by the app store once they see this as a way to install unapproved apps (or more importantly, hurt their 30% tax)
Signed up - saved my first page - and viewed my dash within 5 mins. Good stuff. Now, all you need is not to go out of business (or open source before you do). Seriously though, good luck on the business side.
1. Chrome will aggressively throttle background tabs
I am worry about apps like soundcloud or spotify (web versions) that will die and stop playing or making big pauses between songs. Will make sense to show a pop up (requested manually by the app) to ask for "run on background" permission?
keywords: requested, manually, big, make, sense, making
Summary is somewhat ok but the keywords are way off. Am I missing something?
You should consider having a version that does not print the email in the invocation - it may get picked up and be spammed. one might not want to publicize the backend email recipient of the support/feedback. Another reason is that if someone figures out the fig api, they can send emails to arbitrary recipients thus blacklisting the fig domain.
One thought is that it ought to be a service that works with a hash/UUID and that value maps to a recipient email on your database. so the only people who know my email is fig itself. Still - one can in theory spam every fig user by scraping for fig js. that brings me to some sort of recaptcha, i'm not a robot support.
Added bonus: backend can route the message via any channel not just email.
It's really hard to gain traction remotely so you need to be able expand your markets by sending folks over establishing beach-heads in new territories. Going from US to India is a visa on arrival. Going to the US (or pretty much any place with money) from India is a ordeal and a gamble.
It would be a useful if one could use this in conjunction with cheerio to process the whole thing in nodejs instead of requiring to inject the alasql js into the page.
I find this strange as turmeric's been used as topical antibiotic in India since ancient times - https://en.wikipedia.org/wiki/Turmeric#Traditional_uses - highly unlikely they were thrown off by false positives in protein binding tests.