Today’s demo is something I started working on Sunday “for fun”, but when it turned into an unholy mess (see Recording and saving audio in Cordova applications), it took me a bit longer to wrap than I expected. The idea was simple. “Sound Boards” are apps that contain a collection of sounds, typically related to a movie or TV show. My coworker Andy built a cool sound board themed around Halloween a few years back: Halloween Fun with PhoneGap. I wanted to build a sound board too, but instead of shipping it with a set of sounds, I wanted it to be completely customized. The idea being you could record your own sounds. In a fit of extreme creativity, I called it – “My Sound Board”.
Welcome to another post on my ongoing series exploring building an Ionic hybrid mobile app making use of Node.js running on IBM Bluemix. Today I’m going to talk about writing data back to the server. Spoiler – this won’t be quite as cool as bringing sexy back. In my last post, I described a few minor updates to help flesh out the views of the mobile app. This included building the “Sauce view” (sauce plus reviews) for the application. Today I built another major aspect of the application – actual review writing.
Ah, looking at that title there you probably think, “Surely this is a simple matter in Cordova and surely this is Raymond, once again, blogging something is incredibly obvious and simple just to drive people to his Amazon Wishlist.” Yep, that’s what I thought too. This weekend I began work on a simple little Cordova app for my son. I thought it would be a great blog post too. But while working on it, I ran into an issue with audio recordings that drove me bat-shit crazy for a few hours, so I thought I’d better share so others don’t have to bang their heads against the wall too.
“Handling the Sauce view” – how immature would I sound if I said that title made me laugh? Today’s post isn’t terribly exciting. I’m basically going to cover how I got one more screen in my app working. But I’m ok with this being kind of boring. As I document this process, somethings will be complex and some will simple. This is one of the simple items that I think is still useful to cover.
Earlier this week I was working with a desktop app (which I can’t talk about… yet) that had an Ionic-look to it. On a whim, I opened up the package contents and discovered it was an Electron app. If you’ve never heard of it, Electron is an open source project that lets you build desktop apps (for Mac, Windows, and Linux) using web technologies. The last time I did anything in this space was with Adobe AIR, which was years ago. I’ve played with Electron a tiny bit, but I had not tried to use Ionic with it so I thought I’d give it a shot. Before digging in, I want to bring up two very important points.
Almost a year ago I blogged about using the EventBrite API with ColdFusion. At that time, I was under the impression that all uses of the EventBrite API required a private OAuth token. This means it would not be possible to use the data on the client-side. (Unless you used a server to proxy the API calls for you of course.) But after speaking to Mitch Colleran from EventBrite, I was happy to discover I was wrong.
Welcome to another post detailing my efforts to build an Ionic-based mobile app backed by Node.js and Cloudant on IBM Bluemix. In my last post, I focused on the front end of the application. I talked about the various screens I built and how my service layer used mock data to generate data. In today’s post, I’m going to setup, design, and connect a back end server to start replacing some of that mock data with real information. As a reminder, you can find the initial post in this series here,
I’ve said on more than one occasion that it was gaming that initially got me into programming. Initially just cheating at games (I hacked my Bard’s Tale save and I modified the source code in Lemonade Stand), but what I really wanted to do was create my own games. That dream pretty much went away when I left the computer science program in college and discovered the web, but I’ve toyed with the idea of building my own web-based games from time to time. A while back, I was lucky enough to get a copy of “Build an HTML5 Game” by Karl Bunyan.
Warning – what follows is a complete waste of time. Do not spend time reading this blog post. Still here? Of course you are. For the past few days I’ve been addicted to a cool little game called WordBrain. It is a simple idea. You’re presented with a grid of letters and must find two words within it by drawing a ‘path’ from one letter to the next. I like word games, but oddly have never really played any on my mobile devices before. Now I know why – they’re incredibly addictive. While playing a few days ago I found myself stuck on one particular puzzle.
Well, this was a weird one. Yesterday I was working on a project where I made multiple requests to the Random User API. It worked perfectly in Chrome, and Android, but in Safari, I noticed something odd. Even though I made multiple requests, every result was the same, not unique. Here is a simplified version of what I built.