Text

Just wanted to give an update on the progress with Wooden Rows.

As you may remember, because of Amazon’s Terms of Service, I could not use their data in a mobile application. As a result, I needed to find new data sources. I’ve managed to find a way to get info for everything.

I’ll be using TheGamesDB for video game data. It’s free to use, has very little restrictions, and covers things from the Amiga to the Wii U. For books, we’ll be using OpenLibrary.org, a great project that also has very little restrictions on its use. For movies, we’ll be using Best Buy’s open platform, and for music we’re using Discogs, with a fallback to BestBuy when no results are returned.

So far, these services have been working out well. 

The next version will require some migration from you though. Upon launching the app, you’ll have to use the Migration Assistant I’m building to move your data from Amazon-sourced data to data from one of the new sources. This will be painless and you can start and stop the process at your leisure, so you don’t have to sit through it for thousands of items if you’ve done that. You’ll be able to do a few at a time.

My goal is to eventually have a Wooden Rows database of products that we search instead, and the first step towards that is coming. In the next version, you’ll be able to manually add an item to your library, including uploading an image for it. Eventually, once the database grows, the app will search out database first.

These changes will launch in webOS first to make sure existing users move to the new data sources. Android and iOS development are coming along nicely, but stalled because of the Amazon issue.

Just wanted to fill you in. I’ll be scarce until about Tuesday on account of the peak of Mardi Gras is happening, pretty much now. 

Text

Wooden Rows saw a really nice launch! In about 8 hours from the time it was launched, over 53,000 items were added to users’ libraries, averaging about 547 items per user. This is a great response!

However, I may have jumped the gun and launched a day early.

Apparently, Amazon’s Terms of Service for their API state that their API cannot be used with applications intended to be used on mobile or handheld devices. That means Wooden Rows.

This means that I must abandon Amazon as my data provider as soon as possible. This sucks a lot as Amazon provided the best user experience. So, what are the alternatives?

Surprisingly, eBay has a nice and less restrictive API for getting product information. Unfortunately, it has less data about each item. As Amazon gives you track listings and aspect ratios for your items, eBay does not (well, not consistently). However, it’s the best, most legal method for obtaining data.

I did some thinking and honestly, the main thing you want in your library are the titles, the format, the image, year, and the creator (artist, author, etc). This is the most important info. And eBay gives me this much.

What I’m in the process of doing is moving the app over to using eBay instead of Amazon for data. However, what I’m doing is, the app will query my server first. My server will then search the libraries of every existing Wooden Rows user and see if they have the item. If so, we’ll reference that data and save an API call to eBay. If there are no results for that item in the Wooden Rows database, we’ll then query eBay and return results from there.

The cool thing is, all of that is handled on the Wooden Rows server. This means that, in the future, I can change the data provider, add more data providers, etc. and you guys will never know the difference. It won’t take me issuing an app update. And, as Wooden Rows is poised to go cross-platform, this is a big deal.

There is one downside for you early adopters — once I make the change to support eBay, you’ll have to run a little migration tool built into the next version of the app to convert your Amazon data to eBay data. 

In addition, because eBay may not have the item you want, I will be adding in the ability to manually add items, including uploading a photo for it, and the ability to edit items in your library. This well help alleviate any weird info eBay gives you, or if the photo sucks, or the meta data is incomplete.

I’m doing everything I can to make this as painless as possible. 

So, keep a watch here and on my Twitter to find out more info. I need to get this done ASAP, so, hopefully Thursday or Friday I’ll have this completed.

I thank you for buying Wooden Rows and thank you for understanding. The alternative is to pull the app and give up, but screw that!

Ladies and Gentlemen -- I give you my first webservice

Wooden Rows has been released on the webOS TouchPad, with an Android and iOS version coming this month.

Text

I’ve always been a big fan of open source. It’s how I’ve learned how to do most of what I do. I’m also a fan of getting some income from my app sales. I’ve struggled to find a balance between the two.

While I know open sourcing doesn’t always negatively affect profits of an app, I’m not sure I want to risk it.

So, I’m not positive if apps like incredible! or Wooden Rows will ever be fully open source, but I will open source older apps. I will also continue to post Gists of code on GitHub for components and CSS and functions I think could be useful to others.

My first mobile app (foursquare) has always been open source and my Untappd webOS client growlr has been too. So, to add to that, I’ve opened the source for neato! today.

You can find all of my open source projects on GitHub (foursquare is under their account).

I will also make the commitment right now that neato! will always be open source, so when I port neato! to Enyo for cross-platform development, it’ll still be opened. It’ll still be for sale in the various app stores, but it’ll be open as well.

I like the idea of opening up Wooden Rows, but there are lots of server-side aspects of the app that I’m not sure I want to open up, especially since I don’t want my server to get hammered or compromised. I am willing to work with members of the Open Source community to discuss the feasibility of this. Not that it means I”ll definitely do it, but I’d like to hear some ideas before I decide not to.

Text

A lot of talk about piracy in the webOS world has been taking place and I felt like commenting on it here.

First, let’s get this out of the way: piracy, by definition, is theft and theft is illegal. Piracy is in fact illegal, according to pretty much every country. This isn’t an opinion; it’s a fact.

The controversy over piracy isn’t whether it’s illegal or not; it’s over whether it’s moral or not. Before we can dive into that, we should cover some other points.

Effect on Developers
Piracy does affect the developers directly, especially smaller, indie developers like myself. Luckily for me, my apps are a side-job and not my main source of income. A little hit to my bottom line on app sales doesn’t keep food off my table, nor does it mean the bank will take my house. But that’s my situation. A lot of people do depend on their app sales for a significant portion of their household income.

Simple math would dictate that piracy does take money from developers. Let’s say that 1,000 people have downloaded your app that is priced at $1. That would mean your app made you $1,000 (not taking the App Store/Catalog/Marketplace cuts). However, 30 of those 1,000 users actually pirated your app, which means you lost $30. On the first glance, $30 isn’t a whole lot of money and it’s not much to worry about.

But that’s assuming those 30 pirates are the only people that will steal your app. Chances are, a link to download the app is posted somewhere, which means that others will download your app for free until that link is no longer available. That $30 steadily increases, especially if you have a popular app, and if you charge more than $1 for your app (as you probably should be).

Why Do People Pirate Apps?
There are a lot of reasons people pirate apps. The first reason is usually “I don’t want to pay for something I can get for free.” And let’s be honest, most of us are like that. I don’t mean we all steal, but, given the choice between paying for something, or it being given to you for free, most of us would take it for free. This is the type of pirate that I honestly despise and don’t want. They’re under the impression that because they can’t afford to purchase something, they don’t have to pay for it. This is a terrible rationalization.

Taking something because you can’t/don’t want to pay for it is not a valid excuse. I’d love to get a new car right now. My Corolla is showing its age and could really be replaced. But, I can’t afford to buy a new car right now. Does that mean I can just go to the Toyota dealership and just take one? Absolutely not! If you can’t afford something, you have to go without it. 

But, in terms of app theft, there are a couple of other reasons people steal. One is georestrictions. In my experience, a lot of people have pirated my apps because they can’t purchase them through the App Catalog in their country. I make my apps available in every country HP allows me too, but for various reasons, that isn’t every country in the world. As a result, these users can’t use my app. It’s not their fault. So, they find a place to download them and use them. To mean, that’s a testament to how good my apps are. The fact that someone who can’t legally buy my app will seek it out elsewhere means my app is worth it to them.

Another reason people pirate apps is to try them out before buying them. On most platforms, unless the developer offers a separate free/trial version of their app, there is no way to try an app without having to buy it and hope for the best. The Android Marketplace lets users “return” an app within 15 minutes of purchasing it. While this isn’t an ideal amount of time to try out an app, it’s a step in the right direction. I get it, though. You can rent a movie or stream it on Netflix if you don’t want to buy it just yet. You can watch a trailer of the movie before seeing it in theatres. You can listen to 30 second samples of each song on an album before purchasing it, or listen to the whole thing in some brick-and-mortar stores. Heck, most restaurants give you a sample of the wine you order before paying for the whole bottle. A lot of bars will give you a sample of a beer before you buy a whole pint. I get it. We live in a world where, generally speaking, you can try something before you buy it and the app world hasn’t fully caught up to that.

I’m not just a developer. I’m a user, too. I experience all of these things myself, just as you do. I hope and hope that an app (especially one that’s $2 or $3) is worth it. But, instead of just biting the bullet and purchasing the app, I research it. I read reviews in the Catalog. I look at the screen shots or video to see if it does what I expect it to do. I look up reviews of the apps on the various mobile blogs. I search the name of the app on YouTube to see if there are any videos showing how the app works. I research apps the same way I’d research a TV or anything else I was considering buying. I don’t just buy the first TV I see in Best Buy; I look online and ask friends and research the TV myself first. When I walk into the store, I know exactly what I want.

So, What’s Legit?
Well, not a whole lot. Saying you pirated an app because you didn’t want to pay for it or can’t afford to pay for it is the least-valid excuse of all. This is absolutely no different than walking into a store, taking something off the shelves, and walking out without paying for it.

Pirating something as a try-before-you-buy method isn’t as bad, provided you actually make a purchase for the app if you like it, or if you don’t, you purchase some other app that does what you want it to. This is very seldom the outcome of pirating, by the way. Researching something before buying it — whether it’s a house or a TV or an app — is ALWAYS a good idea.

Pirating because you legally cannot buy the app in your country is a grey area. It’s a part of piracy that I sort of turn my eye from. However, if this is the case, it is your duty to contact the developer of the app (any decent developer has contact info in the app or in the app description) and offer to PayPal them for the app. This is not so crazy, mind you. I have received close to 20 PayPal donations for various amounts from people that stole neato! because they could not download the app in their country. Some donated less than the price of the app ($0.50) and some donated more than the cost of the app ($5.00).

Unfortunately, the norm is that people pirate because they don’t want to or don’t have the money to spend on the app. This is not a justification for piracy. “I didn’t have enough money!” “I’m only a teenager without a credit card!” “I don’t have a job!” These are not valid excuses for piracy. And, if that’s the case, then I’d have to question how you got a cellphone and pay the bill each month. If you only have enough money to pay your phone bill each month, then that means you don’t get apps. Either get a less-expensive monthly plan so you can afford apps, or, only download apps that are intentionally free. Those are your choices. There is no “But…”. 

And if you’re a kid and your parents bought your cellphone and pay for your plan, then, guess what — that doesn’t mean you can pirate. If you parents won’t pay for apps, then, buddy, you don’t get apps. It doesn’t mean you can steal them. If they wouldn’t buy you that cellphone, would have stolen that, too?

Furthermore…
There’s this idea in the piracy circles that because it’s so easy to pirate something, it’s okay to do it. Stealing software is very easy. You download the file just like any other file on the web, so it feels no different than legally downloading something. Contrast that with stealing something from a physical store — buying something from a store and stealing something from a store are VERY different actions. This is how people feel that it’s wrong.

Which brings me to my next point: pirates feel that because apps are digital goods, that is, intangible objects, that it’s not a big deal to steal them. In fact, I’ve read arguments that it isn’t stealing at all because you’re not physically taking anything. Some argue that because the copies are produced for nothing, it’s justifiable. They argue that physical goods cost money to make each unit. This is true. The cost to make a TV is the same every single time. It costs the same to make 1 TV as it does to make 1000 TVs (excluding discounted rates for buying parts in bulk). So, taking one TV means taking the cost of making that TV out of the company’s pocket.

But digital goods, you can copy a file a million times and there’s really zero overhead. Technically, as a developer, you only make one app and then you have infinity copies of your app to sell. So, technically, yes, it doesn’t cost the same money to make each copy of your app as it did to make the first one.

Plus, people argue that since all you had to do was type out some code for a few hours and didn’t actually use any materials to make an app that all of your app sales are profits. In some ways, this is true. I won’t deny that. And yes, I would own a computer whether I was a developer or not. So, that cost doesn’t really factor in.

But let’s factor in some other costs. The software I sue to develop my apps, Coda, is $100. I bought that. Also consider the amount of tablets and phones I’ve had to get as test devices. Buying a cellphone off-contract is not $99. It’s usually closer to $500. Now, obviously, these are generally one-time purchases. Unless the hardware company makes a vast change in their device (like, iPad 1 vs iPad 2). Then you have to buy it all over again to test for compatibility, or new features (like a camera or gyroscope or something). Also consider that most mobile platforms require their developers to pay a yearly fee to be a registered developer and have your app in the official Store. This is usually another $100.

What about the costs of running a server if your app uses cloud storage in some way, like all of my apps do? To handle thousands and thousands of simultaneous users on multiple platforms using multiple apps you need a beefy server with a lot of bandwidth. Hell, you might even need multiple servers.

But never mind the things you actually have to buy. What about the time spent developing the app? Researching and learning the device’s ins and outs. Researching and learning the APIs for developing the app on that platform. The time spent in Photoshop (another expensive software…) making graphics and UI components?

Just because, when it comes to apps, I work for myself doesn’t mean I shouldn’t get paid for my time. And even if you consider my development a service and not making a product, should people who provide a service be paid? What a maid services that clean your home or business? They don’t actually give you anything. They provide a service. The same with real estate agents. You pay them to help you pay someone else for a house. (Ok, you don’t always pay them directly, but they still get paid for their time.)

Yes, I develop apps because I can make money from them. I’d be lying if I said otherwise. But that isn’t the only reason. I make apps because I see a void in the way people do things and I aim to fill that void by providing a product that they can use. I also have free apps that I made for that reason. I contribute code to open source. I help other developers and users on forums and Twitter and never expect any cash. Developers aren’t always doing everything for the money. We aren’t greedy (well, most of us. Like any group, there are always the ones that are in it for the wrong reasons and make the rest of us look bad.).

Do I care that people steal my apps? Absolutely. My apps are things I’m proud of. They’re things I’ve literally spend hundreds, if not, thousands of hours creating and marketing and supporting. If I charge for those apps, I expect to receive that money for them. There’s a reason apps are priced so low — we’re recouping the development costs a little on each app sale. A 99¢ app yields the developer a little under 70¢, after Apple or HP or whomever takes their 30% cut. That means, for a 99¢ app, we get 70¢. That’s not a lot. Sure, after several thousand downloads, that number increases, but it’s still not a lot, especially if that developer counts on app sales for a significant portion of their income.

I’ve seen comments along the lines of “It’s just a hobby you do on weekends.” As a customer, it’s not up to you to decide what is considered a hobby or a side job or to even worry how much time we spend making something. The point is that we’ve made something and if you want to use it, you’ll have to pay for it.

Sometimes I wish I could get the streaming AND disc movies from Netflix, but my budget only allows for the cheap streaming-only plan. Just because I want the discs and can’t afford it does not mean I can grab random red envelopes from my neighbors’ mail boxes. I’m sure if I just told the people at Netflix, the Post Office, and my neighbors that I really wanted the discs but can’t afford it, it’ll all be okay, right? I mean, surely Netflix has recouped the costs for that disc already? It’s not like they need my extra dollars each month to cover the cost, right?

But that’s life, man. If you want something that costs money and you don’t have that money or want to part with that money, then you can’t have it. It’s time to be damn adult and realize this.

Again, I get nervous buying apps, too. If it sucks, I’m out of that money. But, as a person who spent that money, that is a risk I’m taking. This isn’t a surprise. This isn’t some hidden fact about app stores. It is well-known that if you buy an app, you bought it for life. There’s no take-backs. No refunds. You know this going in, so, if you’re not willing to work under those rules, then you shouldn’t be using an app-capable device, or you should only use apps that are listed as free.

People say that piracy increases sales. In some media, that’s probably true, but that’s because alternate revenue streams exist. Some musicians say piracy has increased sales for them, which I definitely believe. But, that’s also because some people want to have the liner notes and other things that come with physical CDs. It’s because bands have T-shirts and stickers and concerts tickets to sell, where they actually make more money. It doesn’t work out for all musicians, but I can see how it helps those that it does.

Apps don’t really have those extra revenue streams though. If you steal an app, you have the entire app. There are no physical goodies that you’re missing out on. There are no public appearances that people pay for. There are no T-shirts or bumper stickers to buy (well, most of the time). So, the idea that piracy boosts app sales is really, quite frankly, bullshit.

Will I go after people that steal my apps? Nah, probably not. For me, personally, it’s not worth my time. And, in the end, it’s not in their best interest. They won’t know when newer versions are released. They won’t be guaranteed a fully functioning app. They won’t be guaranteed a safe app that someone hasn’t tampered with to mess up their phone or steal their data. There’s a greater risk to being a pirate, so, I feel they’ll get theirs in the end.

I commend others fighting piracy on the various platforms and I hope they’re successful. What’s happening is illegal and wrong, so, it should definitely be stopped.

St. Baldrick's

Hey guys! If you’re not familiar with St. Baldrick’s, it’s the cool organization that gets people to shave their heads in solidarity with kids undergoing cancer treatment. By promising to shave my head at the local event here in New Orleans, I’m asking friends and family to make a donation on my behalf. 

100% of the donations go to cancer research grants.

So, if you can spare a few dollars, I’d be really grateful!

Text

It finally happened. I’ve finally submitted Wooden Rows to HP. Hopefully it’s reviewed and approved quickly.

In case you don’t know, Wooden Rows is a visual database of your books, music, movies, and video games. You can sort and search your library almost any way you’d want to. Want to watch a movie? Scroll through your movies in Wooden Rows instead of standing in front of your DVD rack forever. Can’t remember which books you own from a series? Pull it up on Wooden Rows.

In addition to just keeping track of your stuff in your house, Wooden Rows can also let you mark whether you lent an item out to a friend and to whom. So, if Bill still has your “LOST” season 6 DVDs, you’ll know right away.

Even better is that all of your data is synced “in the cloud” so if your device gets lost or broken, or if you use Wooden Rows on multiple devices, simply logging in will pull in all of your content. What’s more is, since it’s all on the web anyway, you can view your library from the Wooden Rows website on any device with a web browser. Perfect for those times you’re in the store and can’t remember if you have the director’s cut with actor commentary, or the special edition with the blooper reel.

And, of course, Wooden Rows lets you share any item in your library on Facebook or Twitter. Your friends will get to see your library items like this. And, if you turn the feature on, it’ll share each item you add to your library via Facebook’s Open Graph, which means your items will show up in the Activity Stream on Facebook.

Wooden Rows uses Amazon to find and add your items. The app is smart enough to know whether you use Amazon.com or Amazon.co.uk or any other localized Amazon site so you always get the appropriate content.

Wooden Rows is currently only available for the HP TouchPad running webOS. It will very soon be available on webOS smartphones (with Enyo), iOS devices (iPhones, iPod Touches, iPads), and Android devices (phones and tablets). Shortly thereafter we’ll see a Windows Phone 7 release as well.

Once it is approved by HP, you’ll be able to download it in the App Catalog for $3.99. 

BONUS! As a celebration of the launch of Wooden Rows, I have permanently lowered the price of incredible! from $4.99 to $3.99. If you don’t already have it, grab it from the App Catalog!

Text

So, some time has passed since the open-sourcing of the Enyo framework and I’ve had some time to put aside my “Oh my god! Oh my god!” excitement and start formulating a plan and to reflect on what being a webOS developer has afforded me.

Let’s Take a Step Back
Mid-2009, Palm shows off the first webOS device, the Palm Pre, at CES. I happen to be in the market for a new smartphone. 

Actually, let’s take a few more steps back.

I’m a problem solver when it comes to the way I use computers. I’ve been a developer in some capacity since the second grade (built a Tic-Tac-Toe game in BASIC). Once I discovered Visual Basic 6 (using a “borrowed” copy from my uncle), I discovered that any time a program frustrated me, I’d just make my own that didn’t. Hated the calendar application in Windows 95, so I wrote my own to pop-up reminders for important events, like birthdays. The idea that I could fix something by creating something new excited me.

It was around that time that I got into web development. My first major web project was in high school where I built an online community around (yes, I know…) “new metal”. Yep, a community for Korn and System of a Down and Coal Chamber fans to post lyrics, photos, music videos, etc. It got pretty large. All of it was static pages. I’d take e-mail submissions and manually update the HTML files. A few things were done by copy-pasted widgets, but it was mostly static.

As I got older, I got into ASP, and later PHP, where I started to make websites for friends and family. I’d eventually start my own side business developing websites professionally, once my design and user experience skills increased. By 2009, I had been a professional web developer for about 10 years, both as a freelancer and for my day-job.

Now that you have my background, we can jump back to 2009.

So as I saw and read about webOS I instantly knew it was for me. Why? Because I could develop my own apps for my phone! I had never considered becoming an app developer by any means. I wanted to write apps for my old Windows Mobile 6 device, but frankly, I didn’t want to learn something new.

webOS opened a door for me to make my life easier, not only because the OS was, as I saw it, ahead of its time, but because I could make little apps that did things for me when I found things I didn’t like in existing apps.

And so I began writing the foursquare app for webOS. I wanted foursquare, but webOS users were out of luck. SMS was a terrible way to check in, and the mobile website required you to search for the venue, which wasn’t very helpful or speedy. So, I started writing the app, got some big help from a couple of other guys (Chris van Buskirk!) and the foursquare team (Naveen has had a huge hand in my success as a mobile developer as a result), and people liked what they saw. I made it prettier, made it more like the Android and iPhone experiences, and I got the confidence I needed to build more apps.

It’s important to note that I never intended my foursquare app to be used by anyone but myself. It was, in my eyes, a stop-gap until foursquare eventually developed one in-house. Unfortunately, partly because of my diligence and partly because of webOS’s lack of market-share, that never happened. So, as a result, I kept building to make the app what it is today.

The same thing happened when Google built Chrome-to-Phone for Android, an app that allowed you to send URLs from your web browser to your Android phone. I loved this idea and wanted, so I set out to build a little utility for webOS that did basically the same thing. Again, I was aiming to just make something for myself. But, people wanted the tool themselves and so I expanded its capabilities, made it prettier, and neato! was born.

Not much later, I did the same thing, only because Untappd’s mobile web interface couldn’t get GPS coordinates in the webOS browser, webOS users couldn’t add their location to their beer check-ins. So, to work around that, I built growlr, a little app to let you check-in to Untappd and attach your foursquare location to your check-in. I actually got the very first API Key for Untappd’s API to develop this app. Greg Avola, the CTO, had to add me into the database manually!

These three apps and the support from the webOS community made me realize that I was, sort of by chance, a mobile app developer.

Coming to Terms
Once I realized I was mobile developer, I needed new ideas. I also needed to make some decisions. 

I had come up with my latest idea — incredible!, a sort of aggregator for a user’s social media accounts — and I absolutely wanted it to be a webOS app. At this point, my then-girlfriend-now-wife Rhea was a Pixi user, I was a Pre user, and the murmurs of what webOS was going to be were loud. HP had purchased Palm and all we heard about was what great things were going to happen with this revolutionary mobile OS.

So, because of all of that, I put all of my eggs into the webOS basket and started development for incredible!. This felt like a good idea. Sure, webOS was barely fighting for 3rd place in the mobile market, but everything felt like it was going to advance. It felt like my choice was a smart one. As an indie developer, making the leap to crossplatform is expensive, what with developer program fees (about $100 on most platforms) and the cost of buying devices for each platform (and, in most cases, phone and tablet devices for each platform). It didn’t make financial sense for me to go cross platform at the moment.

So I stuck with webOS. And, despite HP killing off webOS hardware, despite webOS never reaching 3rd place in market or mind share, despite people laughing any time I said “webOS”, despite the quick buck being an iPhone developer made you at the time, this was the best decision I ever made.

I’m Ahead of the Game
You see, because I wrote my apps as webOS apps first, I probably missed out on some cash. That sucks. But, because the webOS community is so good and strong and supportive, and because the webOS Developer Relations group is so good and strong and supportive, I was somewhat successful. I have some dough in my PayPal account. Not much, but it’s there. 

But, because I chose webOS as my target platform, I’m ready for what 2012 webOS will bring. With the open-sourcing of Enyo, I can easily port my apps to iOS and Android using the same code base.

You see, I, today, right now, have a working version of my next app, Wooden Rows, running beautifully on webOS on my TouchPad. Taking that same code, I built a PhoneGap application and have that same app running beautifully on an iPad. And, because of the open source nature of webOS, the Android community has managed to get Android running on the TouchPad, which means, for free, I have an Android tablet to test on. Which also means, in addition to my same code running on webOS and iOS, I also have it running on Android.

That’s such an amazing thing to me, I want to state it again:

I have the exact same code for my webOS app running on iOS and Android.

Is it perfect? Nah, I have to make a few tweaks here and there, but the point is, it’s there and it works, and it’s worth charging money for in the App Store and the Android Marketplace.

And what’s awesome further is that because of webOS and Enyo’s web-based technologies, making my apps scale down to phone-sized screens is pretty much a matter of making some changes to my CSS for the app to work on smaller screens. I’m about 60% done getting my webOS tablet app working at phone resolutions on 3 platforms.

This means that Wooden Rows will be available on:

  • HP TouchPad
  • Palm Pre (all)
  • Palm Pixi (all)
  • HP Veer
  • iPad (all)
  • iPhone (all)
  • Android phones (as many as possible!)
  • Samsung Galaxy Tab
  • Amazon Kindle Fire
  • Other Android tablets

And that’s just the beginning.

So, again, being a webOS developer means that I have a cross-platform app almost ready for the masses, and I have a free webOS and Android tablet device. All because I made a seemingly silly decision to stick with webOS.

Looking Into the Future
Since I’m well-versed in the ways of Enyo, I am head of the game even into the future. Once Enyo 2.0 is fully baked, I’ll start developing all of my new apps using it and targeting webOS, Android, iOS, and Windows Phone 7. 

I can build apps for pretty much any platform using everything I know right now, without having to learn a new language. I can sell my apps 3 to 4 times over. 

I can, for real now, feel like a mobile developer.

And I owe every bit of it to choosing that Palm Pre back in 2009 and never looking back. Thanks, webOS community. Thanks, webOS Developer Relations team. 

Text

I’m pretty excited about the open-sourcing of the Enyo framework. This means big things for me as a developer, so I thought I’d comment on what my plans are.

  1. Finish Developing Wooden Rows. This should happen this week, with a submission to the webOS App Catalog this weekend. (Hopefully!) The app, as promised, will be available on webOS first. It is TouchPad-only at the moment, but I hope to change that.
  2. Make Sure Wooden Rows is Resolution-Agnostic. While it’s best a tablet app, I want to work on making it work at smaller screen sizes so it’ll be phone-friendly, too.
  3. Port Wooden Rows to iOS and Android. Thanks to PhoneGap, this should be relatively easy. I’ll push to these two platforms as quickly as possible. Assuming the app scales down to phone screens well, it’ll be on phones and tablets with these OSes.
  4. Port incredible! to iOS and Android. I’m targeting these platforms first since they’re the big ones. I’m aiming for tablets only on this one.
  5. Begin Developing New App. I have plans for a new app. I’ll give more details as I get closer to starting on it.
  6. Rebuild neato! in Enyo. By this point, Enyo 2.0 will be fully released and I’ll be able to bring neato! to webOS, Android, iOS, and Windows Phone, allowing you to send stuff from your Pre to your iPad or your iPhone to your Kindle Fire or any other crazy combination.

So, there you have it: a rough outline of my development plans. I’m targeting iOS and Android first with the ports, but will work on Windows Phone after that. I also haven’t ruled out a web app for users that currently use the app on some other devices.

And, because of the new Zhephree Accounts, your settings and data will be available across all devices automatically. Have the app on your TouchPad? Sign in on your iPad and boom! it’s all there.

Text

Obviously, you’ve heard about SOPA and PIPA, the bills that will give the government unfettered authority over the Internet. I won’t go into details here as others have done it far better. But it’s important for you to take action and let your Representatives and Senators know how you feel. They take an oath to vote as their constituents want them to vote. Yes, there’s nothing that says they have to and if they’re not up for re-election, they probably don’t care, but many Representatives and reversed their opinions and support because of citizen outcry.

So, to help you help us, here’s where you can find your representatives and senators to contact them.

  1. Go to Wikipedia
  2. When the blackout loads, enter in your ZIP code
  3. Click the “Contact Form” link under one of your Congresspeople.
  4. Fill out the form on their website and ask them to vote against SOPA.
  5. Repeat this for all of your Congresspeople.

If you need help on what to say, here’s the message I’ve been sending out:

[NAME OF REP] —

As you are aware, the SOPA bill is about to be voted upon. As your constituent, I plead with you to do what you can to stop this disaster of a bill.

The internet is a font of knowledge and a communication platform like no other. It enables us to communicate with loved ones across the globe. It helps our troops over seas see their families while they defend our freedoms. It helps students learn and access information in ways and speeds never before possible.

As with all types of theft, there obviously must be something done about rampant piracy and copyright infringement on the Internet — this much is true. However, the carte blanche authority SOPA would give the US government is appalling, and frankly, scary.

The United States has prided itself as a place of freedom where one can go to escape oppression and inequalities from other nations — the very reason our great country exists at all. If SOPA passes, the US will be employing an overly restrictive Internet identical to those in place in China, Syria, and Iran — countries we’ve been trying to get to change their ways. It feels like a step backward to pass SOPA.

Passing SOPA does nothing to curb piracy. It does not go after those that infringe copyrights. Under SOPA, a news organization’s website could be shut down if an anonymous commenter leaves a comment with a link to a site with infringing material. This would be akin to a vandal spray painting the wall of a building and the owner of that building being arrested instead of the vandal.

In order to become a thriving, modern society, we need unfiltered access to the web and to do so, we can’t let SOPA pass. We need a better, more informed game plan.

Thank you.

The key is to explain why SOPA and PIPA are bad, but also why they should care. As you can see, I appealed to their patriotism and troop support. This shows them that this is an un-American bill and that it affects all of is. Likening the bill to “enemy” countries is also helpful. While these are tactics, they are 100% true and accurate.

Please educate yourself on the issue and please pass some links to your friends on Twitter and Facebook and Google+ and wherever to educate them. E-mail your parents and explain it to them.

http://blacklists.eff.org/

http://www.theverge.com/2011/12/22/2648219/stop-online-piracy-act-sopa-what-is-it

http://en.wikipedia.org/wiki/Stop_Online_Piracy_Act (Yes, it still loads)

http://mashable.com/2012/01/18/sopa-dark-ages/

While we as US citizens don’t have a very loud voice, we do still have a voice and it’s time for us to use it.