Zhephree

With webOS 2.0 on its way sooner or later and foursquare’s v2 of their API coming soon or later as well, I felt it was time to focus on v2.0 of the webOS app. Obviously, I plan on tying into new webOS 2.0 features. As of right now, I can only talk about a few (as I am bound by an NDA regarding unannounced webOS 2.0 features). But, here’s some info on what to expect!

• Rewrite of the app’s core code. I’ve already started on it, but I’m rewriting large portions of the app from scratch to optimize it, remove unused code, increase speed, and decrease memory usage. As the app grew over the last 9 months (and as my knowledge of webOS increased) new features got added into the app, but were really patches on existing code. I’m rewriting the AppAssistant, StageAssistant, Places scene, and Check-ins scene from scratch. These Assistants are pretty messy and convoluted and are ripe with memory leaks. I aim to fix that. I’ve also removed lots of old, unsued images from the package to make the install size smaller. Should give us a speed boost, at least on app launch. 
• Usage of webOS 2.0 features. I can at least say this: almost every feature Palm has already announced to the public that will be in webOS 2.0 will likely involve foursquare. Just Type will allow you to search for venues from the OS (by name or tags, so typing “mexican” will find all Mexican restaurants near you) and it’ll also allow you to send a shout direct from the OS (but opens the app to allow you to select if you want to cross-post to Facebook and Twitter). We’ll be tying into Exhibition mode and Synergy as well, but no details on that yet.
• Usage of new foursquare API. Foursquare hasn’t released or finished their new version of their API, but rest assured, as soon as it is available, the app will be using it. It will likely mean new features, or enhancements to existing features, but right now, I’m just guessing.
• Move to OAuth. The app will move to OAuth instead of requiring you to enter your username and password. Not only is this more secure, but it also means that if you change your password for foursquare, you don’t need to change it in the app. This will be standard in all foursquare apps eventually, just like Twitter recently did.
• New features! In addition to whatever new features foursquare adds to the API, I’ll be adding in some of my own. For instance, you’ll finally be able to tap a user’s avatar and it see it full-size. Also, another new feature: see how many tips and users checked-in are at a venue: 
   
  Plus probably a lot of other cool features.
  
  

So, there you go: some insight into where I plan to take foursquare into its future. Let me know of any ideas you may have!