Who You Calling A Jesse?

Trying to sort the brilliant ideas from the lesser ones.

The iPad won't suck...

Posted by Jesse Rodgers on January 28, 2010 at 10:52 PM

…but it will burn many hours of your work day talking about this enlarged iPod/iPhone. Everywhere I turn people are either making fun of it, dismissing it (passionately), or ready to pull out the credit card and buy one. What really gets me are this new group (to me) of people that think you need a half inch, desktop powerful, physical keyboard using device or it just isn’t good enough.

Here’s my position on the iPad the day after:

  • It is a consumption device.
  • It won’t burn your bits when you try and watch a movie on it.
  • I sat in the coffee shop with morning with email, a web browser, and tweet deck open for 3 hrs—didn’t need my laptop for that.
  • It isn’t expensive for the early adopters that will buy version 1
  • It is a product release that had features dropped that didn’t meet the quality control requirements (think iPhone before the 3G)
  • Developing apps for it will likely be awesome
  • If I were a student, I would be beyond excited to have all my text books on that (hey higher ed, how many will be offering this to first years loaded with all their text books, notes, slides, podcasts, etc?)

I will admit my bias and say that a big iPod touch that can tether with my iPhone is all I really wanted. A full OS would have been nice but I am really excited to see how developers take advantage of the HTML 5 stuff that Safari supports.

Will it be for everyone? No. But I would bet their $50 billion company is safe for now.

Canada 3.0: Day 2 impressions

Posted by Jesse Rodgers on June 10, 2009 at 09:30 AM

The Canada 3.0 conference wrapped up the second day with speeches from the CEO of RIM, the Chair of the CRTC, and others all with a strong patriotic message as well as a surprising amount of useful vision and position stuff specifically from the the Chair of the CRTC. Day 2 did, sadly enough, start off with some rather dry and boring stuff that made for a fun game of buzz word bingo.

Between the speeches I attended the talk that included Waterloo’s own Jacqui Murphy from TechCapital. She took full advantage of having a mic and an audience to make it clear that startups shouldn’t be about seeking funding or exits with big companies buying you. You should dream big and focus on revenue generation. Some great messages to bring back to VeloCity I think.

The round table discussions in the afternoon felt like they lacked energy and urgency. The big rooms and groups just didn’t work well for that but I did meet some really interesting folks around my table. If nothing else, that was a huge bonus.

Overall, the strength of the Canada 3.0 conference was in the diversity of the folks that attended. There were some very obvious complaints about the lack of students attending but we really need to stop idealizing students, if they are interested they will come—if they aren’t there they really don’t care…. yet. There were enough student volunteers to suggest to me that the ones that are interested knew about it and made the effort to attend.

What I think was really missing was the younger entrepreneurs and leaders on the panels. Not the under-25s that the over 50’s marvel at, but the 25-40 yr old professional crowd that have the skills, experience, and know how to really push Canada’s ‘digital economy.’ I would have also liked to see more of an unconference stream. Being a Barcamp/Startup organizer I am already a fan of the format but we needed more conversation over round table sticky notes. I will even volunteer to organize that for next time ;)

I should also point out the technology situation. Stratford doesn’t have 3G, the wireless was overwhelmed by all the mobile devices and laptops begging for data (but we got the tweets out!), innovative things weren’t set up like streaming panels to the media room at the very least. Sure Igloo put together a good site but that was impressive a couple years ago, if this is ‘3.0’ then it should push the boundaries.

Honestly, it was an amazing conference. This should be the start of something… keep the buzz going, follow up with the business cards you collected, and start thinking big!

Canada 3.0 Conference: Day 1 impression

Posted by Jesse Rodgers on June 08, 2009 at 08:23 PM

The Canada 3.0 started today in Stratford Ontario (45km west into farm fields from Waterloo) and surpassed a lot of people’s expectations I think. The morning had the typical political talk you would expect when government folks are given a microphone along with the University of Waterloo making it clear it is committed to the Stratford campus and all the potential developing such a campus may hold. What followed was a day of great conversation about communities, what to do to foster entrepreneurial talent, mobile technology, and more.

It was high level discussion mostly but it was honest discussion focused not on how great Canada is but where Canada needs work. Have a look at the twitter stream under the #can30 hash tag for some great bits of information. Day 2 promises to be more interactive with work groups tackling some of the issues presented today.

I spent a lot of they at the VeloCity booth talking to people that are interested in the idea and colleagues at other schools that are a bit envious that Waterloo has such a residence. I will be around for day 2, stop by the booth and say hi!

RIM needs to 'get' the web

Posted by Jesse Rodgers on November 21, 2008 at 09:35 AM

Seems RIM’s new Blackberry Storm has a raised a few eyebrows over web related things. In the first review I read there is a mention on the browser:

…had zero issues with the Storm’s browser. Zooming in and out is simple and it seems to load most pages fine, except the NYTs as it reverts to the mobile edition and doesn’t want to load the regular site. Anything with a lot of Javascript chorks, though. Everywhere else on the device there are scroll up/scroll down keys but they’re missing on the browser. Seems like an odd move, but the navigation bar would be a bit crowded. – CrunchGear

As a person that believes the browser is the platform I think the browser is where the mobile device will be won (or lost). As much as I love the app store I hate having all those silly icons scattered on my device just to access web based content. Let me use my browser (like google does). Likely a balance needs to be found but at the moment I have app icon overload…

Living in the town of RIM (Waterloo, Ontario) I often hear things at pubs, at events, or through some second hand gossip. What I hear is usually some pretty positive stuff but at the risk of calling out a specific person, when I hear something along the lines of “webkit doesn’t support Acid2 but the Storm browser does” as a point of discussion I get a little concerned.

First, the Acid tests for web browsers are not a target that makes your web browser bad ass. You can pass it one day but not the other for good reason. But what I don’t get is that Safari passed Acid2 in April of 2005. What that person said in that statement (to me) is that they made sure they passed a test they didn’t even understand! Sure if you run Acid2 on the browser on the iPhone it has a little issue but there could be a good reason for it. AND IT DOESN’T MATTER. Web standards are guidelines… just don’t break things and force me to customize my CSS or JS for your browser.

I don’t want to put down the folks at RIM (the value of my house is directly related to their success!), they made some huge improvements. Problem is that they are against a number of new competitors that have years on them with regards to utilizing the web… they need to come across as knowing what they are talking about, even in the local gossip pools.

What mobile development strategy makes sense?

Posted by Jesse Rodgers on September 21, 2008 at 10:20 PM

How can you explain the state of mobile development (both web based on device installed) to non-mobile folks that are use to a windows dominated world that makes ‘adjustments’ for Mac from time to time? Here are my basic assumptions:

  • CDMA devices are in some walled garden most of the time.
  • Carriers don’t want to be a service provider, they want to control and profit from the whole experience.
  • Long term contracts from carriers in North America slow down new device uptake.
  • GSM devices are common and low barrier targets.
  • Software on phones is rarely updated.
  • No device is ‘easy’ to develop for, in fact most are like putting together an entire house worth of Ikea furniture along with all the little things.
  • Mobile browsers suck.
  • Microsoft doesn’t yet get mobile, but it will.
  • RIM changed the game (with email, utility, service) but forgot about changing the rules.
  • Apple changed the game further and re-wrote the rules (utility, Application store, touch it).

From those assumptions I am still at the same place I was over a year ago: supporting ‘all devices’ with regards to mobile development is not practical in North America. This includes mobile focused web sites and device installed applications. That isn’t to say there isn’t a market worth going after. Apple gives you access to a lot of people through it’s App store and you can target their browser easy enough. You can target Blackberry as well and if you target both I think you will hit a pretty good market.

The trick in my mind is defining where the market is. What developers need is good (unbiased, up-to-date) research on who is using what devices for what. Not because mobile developers don’t know their audience but because their paying clients, understandably, deserve some real numbers to decide what they need.

Last week I had the pleasure of participating in a meeting between a local mobile start-up and a mobile marketing start-up based out of Toronto. A major chunk of the meeting was spent discussing the various issues of platform and carrier issues.

The marketing group have a client that wants an app on ‘all phones’ – Bell, Telus, Fido, Rogers – but the local start-up can not justify the resources nor can they even think they could support all devices. The client wants to support all phones not because it thinks that is where their target market is but because they don’t know what devices their target market uses. If they new it would be easier for everyone.

This leaves me wondering… is it even possible to collect accurate information on device usage? Is it easier to just target the iPhone since they have data plans and are more likely to have users that want to try out stuff?

Fido offers UMA service

Posted by Jesse Rodgers on May 23, 2008 at 06:23 PM

I noticed today that Fido (a Canadian mobile telco that is part of Rogers) is now offering the Nokia 6301 with UMA enabled if you buy their UNO router. The router thing is kinda dumb. Its just a crap average wifi router than might have some software installed to point your session to Fido/Rogers servers? Or maybe its just a wifi router for $80?

Anyway, kinda lame in how this is going out. I have heard Rogers is rolling it out as well. Perhaps it pains them to use Nokia devices to roll this out since Nokia likes to offer unlocked devices in the US for the same price Rogers sells them for with contracts? It is really cool technology and could, in theory, reduce costs all around. But pushing 802.11 routers that are special seems to be a bit odd.

UMA is: “Unlicensed Mobile Access or UMA, is the commercial name of the 3GPP Generic Access Network, or GAN standard. GAN is a telecommunication system which extends mobile services voice, data and IP Multimedia Subsystem/Session Initiation Protocol (IMS/SIP) applications over IP access networks.” Wikipidea.

iPhone: its the user experience... not invention

Posted by Jesse Rodgers on November 27, 2007 at 11:58 AM

Under what I think is the wrong category, the iPhone is named Invention of the Year by Time. It’s not an ‘invention’ at all though, unless you count the overall phone, PDA, and billing experience. Apple has maybe invented a better process for mobile computing and cellular networks. The iPhone is an enabling technology through its experience, not through its email, browser, etc. It makes the mobile device easy to use and thus inspires a load of developers to mimic that experience on their applications. For that, it is just amazing. The iPhone should get gadget of the year—which it probably will, voting is still open.

Having only played with an iPhone, owned a Blackberry and an Nokia E62, and still have to deal with the moronic customer service of Canadian cellular providers my opinion is purely based on observation but it is pretty obvious that the inability (or lack of motivation) to provide the activation, service, and billing experience that comes with AT&T in the US is what is stopping Rogers from offering the iPhone.

I still want a real keyboard btw… N810 with the iPhone OS would be perfect.

iPhone proves Canada's mobile carriers suck

Posted by Jesse Rodgers on November 06, 2007 at 06:53 AM

Last night (but dated today) an article on how the iPhone comes with a cost for Rogers appeared on the Globe and Mail web site. The article points out how Apple was able to simplify the silly billing practices of mobile carriers in the US and the EU (the iPhone launching in the EU November 9th). They compare the equivalent bill in Canada for the unlimited data/voice at $70 a month (leaving out the AT&T monthly charge with the exchange rate is actually lower in the US). Sadly in Canada if you try to use the data people have been seeing on their iPhone you could go well over $1000 a month. In theory, that is why Apple has not released the iPhone in Canada yet.

I know of a few people with an iPhone in Canada. Some not using their data, others lucky (or silly for paying that premium for so long) enough to have kept the old Fido (a GSM carrier that didn’t have long term contracts then either) unlimited data plan that was around in 2000 before the phones that would use said data were really in use.

Personally I think the iPhone is cool but the lack of iPhone in Canada doesn’t mean the carriers suck. It is the fact they refuse to have phones that are less than a year on the market in the US (never mind Europe), have wifi, with a two year plan still costs hundreds of dollars, and don’t in reality cost close to $150 a month if you actually use them for talking, texting, etc. Their inability to change this practice when the profits of AT&T, likely in part thanks to the iPhone, are stated is what makes them suck. Then of course there is the possibility that Canadians think both Bell and Rogers (CDMA and GSM carriers and our only real choice) are terrible companies in terms of customer service and technology adoption/reliability and that alone means they suck. They could be happy with the money they are making and fear change but that should mean the CRTC needs to stop protecting them and open up the market, now!

I have seen it stated before but I will say it here too… Apple’s big coup with the iPhone is not the technology, it is taking the position to tell the carriers to stuff it and change or loose out on the coolest technology out there (according to Apple’s marketing machine). One lesser mentioned observation I have had is that Nokia (and Motorola) is also sending a message to carriers but in a more subtle way, they are selling their phones unlocked for a decent price in North America (at least). With the US/CDN exchange rate just drop into a Nokia store in any trendy US mall ;) You will still be screwed on the data plans but you can always just use wifi where you can, maybe a little VoIP.

Introducing UW Chatter

Posted by Jesse Rodgers on May 17, 2007 at 09:00 PM

UW Chatter Let me introduce to you UW’s very own Twitter clone called UW Chatter. It’s purpose, to act as notification resource for students, staff, faculty, departments, groups, etc. Features it has now:

  • post to your groups and stream
  • list friends, add groups, create groups, remove groups, etc
  • jabber client (uwchatter@gmail.com)
  • email to SMS notifications
  • email notifications

What it still needs:

  • SMS gateway
  • other IM clients
  • stable jabber
  • a production server
  • UI love
  • twitter API hook in
  • mobile version
  • a way to post to groups from jabber, right now you can just post to your own stream

About the app…. We built this with Ruby on Rails. It lives on a development box with a Mongrel cluster and mySQL in the back end. The code itself will go to Rubyforge the end of June (as will the rest of our Ruby apps).

Please give it a go, create some groups, post some notes. Try it out! If you join the bug and notes group you can post your thoughts on the app and what you would like to see. We still haven’t written a help file yet so you really need to just try it out!

I was supposed to present this today at Design Camp Waterloo but I ended up running around campus chasing my tail…

Comments: (disabled) Tags: mobile

Social networks as a tool for campus security

Posted by Jesse Rodgers on May 10, 2007 at 09:08 AM

Since the tragedy at Virginia Tech just about every higher education campus is dusting off their emergency plan. Why the Montreal shooting in September didn’t have the same effect is beyond me. I suppose people related it more to high school, although a CGEP is more like a Univeristy campus than a high school… anyway people are looking at security and communication with students, staff, and faculty. For some reason they are fixating on mobile phones and SMS as theanswer to all this. That is wrong, it is only a part of the puzzle.

The problem

The problem is defined as how can we get a blast message out to people on campus immediately. I don’t think anyone is expecting to reach everyone at once but reach enough people that the word will get out quickly. SMS is really good for that. A recent poll of students on the Waterloo campus (1300 respondents) has just over 70% of students with mobile phones. If you have all their numbers and an application to blast it out and you assume most have their phone on, just hope they aren’t desensitized to SMS enough that they will check it within a few minutes of it being received. There you go, problem solved.

There are some problems with this theory though. Like the bouncing IM client on their desktop, how many students ignore the instant message part of SMS? How many have their phones on? How many have the same number they entered (likely more now thanks to number portability)? If students are following the rules, their phones are off or silent in class as well.

I think you will reach a lot students with SMS but I don’t think you would reach enough to rely solely on a SMS alert system. I think an alert needs to go out over SMS, email, IM, post on web pages, and ideally even send an alert over the Facebook Waterloo network (23 500 people in that now).

The solution: social networks.

If you look at a system like twitter, you have IM and phone settings but you also have an active user base. If you sent an alert over a social network that has an active user base I think you are far more likely to reach people. It is just amazing how quickly word gets out on twitter. Back to the Virginia Tech tragedy, students and the media turned to social networks for information. That certainly validates their utility.

With the social network theory as my motivation, I have been working with a great group of people under the banner MMNP to create a twitter like application for the UW community that will have an alert feature. It will send out an alert to all the communication venues the user has in their profile.

I will talk about this topic and demo our application this weekend at BarCampWaterloo. Then I will demo it again at Design Camp Waterloo (they really need to plug that into the BarCamp wiki) on the 17th of May. After that the app will go into public use mode but the server likely won’t be stable for a while. We are just finding our way with Mongrel clusters ;)

Comments: (disabled) Tags: mobile

Creating a mobile version of a static site

Posted by Jesse Rodgers on March 21, 2007 at 11:09 AM

Last week I mentioned a bit about the redirect script based on HTTP_USER_AGENT we use to send mobiles to a special version of the home page. This week I have some basic documentation written along with the PHP for download that we use on the mobile.php version of the home page.

Essentially all we are doing is parsing content from the static site and generating a mobile friendly version that is just content in smaller chunks. They are identified by their div class or id. Have a look at the documentation and let me know if anything needs more explanation.

Comments: (disabled) Tags: mobile

Server side sniffing in PHP for mobile devices

Posted by Jesse Rodgers on March 12, 2007 at 12:25 AM

If you go to the UW home page in a Blackberry or Nokia device you will notice that you get a very different page than what you see on your laptop. I mentioned this change back in January. A few people have asked about how we are doing that and given a post on the quirksmode blog suggesting a similar idea I figure I should post the code for all.

In a PHP script that is included in the top of the index.php file, all we do is:

  1. $ua = $_SERVER[‘HTTP_USER_AGENT’];
  2. if (stristr($ua, “Windows CE”) || stristr($ua, “AvantGo”) || stristr($ua, “Mazingo”) || stristr($ua, “Mobile”) || stristr($ua, “T68”) || stristr($ua, “Syncalot”) || stristr($ua, “Blazer”) || stristr($ua,’BlackBerry’) || stristr($ua,’Opera Mini’) || stristr($ua,’Nokia’) || stristr($ua,’SymbianOS’ ))
  3. {
  4. $DEVICE_TYPE=”MOBILE”;
  5. }
  6. if (isset($DEVICE_TYPE) && $DEVICE_TYPE==”MOBILE”)
  7. {
  8. $location=’http://www.uwaterloo.ca/mobile.php’;
  9. header (‘Location: ’.$location);
  10. }

A bit of a headache was getting the right info for the user agent. Each device displays odd information that either tells you the browser or the device or the OS. A little trial an error was needed here.

Then in the mobile.php (uses the xhtml-mobile10.dtd) file we have minimal links but when clicked they parse content from the main index.php page. No duplication of content, just optimized. I will post more on that later ;)

Comments: (disabled) Tags: mobile

Nokia E62 on Oracle Calendar via syncML

Posted by Jesse Rodgers on January 26, 2007 at 12:42 AM

As part of the ‘mobile tech project’ I have been using a Nokia E62. It is great but slow so I usually use my own Nokia 6680—it just works and I don’t mind typing SMS on the normal phone keyboard. Now that might change as I have my Oracle calender syncing properly (something I can’t even do with my Mac). I was directed to a post from a Oren Sreebny over at the University of Washington (another UW) where he posts how to fill out the sync profile for Oracle Calender in a E62.

This is great but he reports no luck with SSL and the only access to syncML on our campus set up is via SSL. I made a couple changes and it seems to work fine. The following are the settings I used:

Under a sync profile for a calender I used:

  • Include in sync: Yes
  • Remote database: ./Calendar/Events
  • Synchronization type: Normal

Under Connection Settings:

  • Server version: 1.1
  • Data bearer: Internet
  • Access Point: Always ask
  • Host address: https://bookit.uwaterloo.ca/ocas-bin/ocas.fcgi?sub=syncml
  • Port: 443
  • User name: my Oracle Cal user name
  • Password: my Oracle Cal password
  • Allow sync requests: Yes
  • Accept all sync reqs: Yes
  • Network authentic: No

This is essentially the same thing as Oren’s posted settings besides the port number and host address. At a guess this might work on all modern Symbian phones for those that have Oracle Calendar.

Now I can just sync my E62 with iSync and iCal works… how cool is that? My 6680 doesn’t support syncML as far as I can tell :(

Comments: (disabled) Tags: mobile