I tweeted using my app (sort of) for the first time today! I say sort of, because I didn't actually do it from my app, but I did use my my app's credentials and my test user's credentials. I used a wonderful API testing app called Paw to do my testing today. It's a really nice tool, and I plan to continue using it for this project.

I also implemented FastClick, a JavaScript library to remove the 300ms lag when tapping items on the screen on touch-screen devices. It was very easy to implement, just a short piece of code in my client-side JavaScript after importing the library itself in the index.html.

// instantiates FastClick
if ('addEventListener' in document) {
  document.addEventListener('DOMContentLoaded', function() {
    FastClick.attach(document.body);
  }, false);
}

Lastly, I began building functionality for the client-side code to send a created tweet to the server for the server to then post to Twitter.

I've been hearing good things about JetBrain's WebStorm JavaScript IDE, so I'm going to try using that for development for a while. One of my instructors really likes it, so hopefully I'll be able to get support from him if I decide to do it.

Today's Research

• Twitter's API Documentation:
  • POST statuses/update - General information on how to POST statuses to Twitter. It turns out it's much easier than I'd expected. If the user is already logged in, you simply URL encode the text, and then send it to Twitter in the request URL.
  • Counting Characters - This article describes in depth how a character is counted by Twitter. It turns out, it's not quite as simple as you'd imagine. Certain types of characters take up different amounts of bytes, and are therefor couted differently. The article says that 'character normalization' is necessary, and it turns out JavaScript has a character normalization function built in.
  • t.co links - Twitter's built in URL shortener — called t.co after the URLs it generates — works relatively automatically, with some caveats. When sending a tweet to Twitter, if it detects a URL in the text, it will automatically convert it to a t.co link, unless it is less than the current maximum t.co URL length. As time goes on, the length of shortened URLs grows as more and more unique links are used up. This means it's important to check with Twitter what the current maximum t.co link length is. This is done by periodically performing a GET request to Twitter's help/configureation URL.
  • GET help/configuration - Information on how to get configuration data from Twitter's API.
• JavaScript Character Normalization (MDN) - The Mozilla Developer Network's documentation on JavaScripts .normalize() method.
• Angular $routeProvider - Once again looking into how to route a user to different pages based on their logged in status using $routeProvider's resolve functionality.
• Unirest - NodeJS REST API library for doing API calls from the server.