Captain Danko’s JavaScript Lab — Code Smarter with Tutorials, Frameworks & Dev Insights

As evident from the evolution of my first iOS app: My Day Todos ; it started off as being a pure Html5 app until it turned into a native iOS app with Html5 powered UI. The app has a very significant text to speech component and before using native iOS API for it i.e. AvSpeechSynthesizer , the text to speech component was powered by the Web Speech API . I will not be talking  about why I switched the AvSpeechSynthesizer but rather a little problem that I had to solve while working with the web speech API. Problem: Show a stop button only when an utterance is being spoken So firstly, I think the Web Speech API is a lot of fun to play with and if you like to know more about it, you can either have a read of the spec  or do this tutorial  to get a feel of how it all works. Also when I talk about the web speech API, I am only talking about speech synthesis. All right, so what I wanted in my app was to show a stop button when the app is speaking i.e. reading out so...

So I came across a data-mining product that presents very useful information via a web-app. What gets delivered to the users of the product is new information  in the form of reports at regular intervals. So the process is, new data is acquired  all the reports are run again on newer data a manager overseeing the product sends an email to the users that notify them that the reports have been updated. Motivation So this process is great and it requires very little effort on part of the manager emailing the users. So the question is "why make that manager use even little effort, when the manager's time could be better utilized?". While the manager can add some more personalized info in the email, the entire process can potentially have the following disadvantages human error: the manager may get busy and may forget to notify the users of the updated reports distractions: if the user has to navigate away from the web app and check their email, this could potent...