Top Posts
Gaia GPS How-To: Using the Click Drawer on...
Meet What’s New in the Web Route Editor 
Introducing Adventure Modes: The Right Map for Every...
Trip Report: A Rider’s Guide to Bikepacking in...
How to Hike a Colorado 14er: A Step-by-Step...
Trip Report: A Rider’s Guide to link Boulder...
Trip Report: A Rider’s Guide to the South...
Battling the Wind: Setting Your Shocks to Firm...
The Hike Map That Broke Me: How Gaia...
A Fond Farewell to National Geographic Maps —...
Gaia GPS
  • Explore The Map
  • Get the App
  • Upgrade Today
  • Explore The Map Catalog
  • New Features
  • Activities
    • Backcountry Skiing
    • Boating
    • Emergency Response
    • Fishing
    • Offroading
  • Adventures
    • User Stories
  • Help
Author

Staff Reports

Staff Reports

Gaia GPS

Facebook – Culture of Coercion

by Staff Reports September 25, 2011
written by Staff Reports

I started using FourSquare recently – I’m now the Mayor of San Pablo Park, and I check in there everyday. My wife and I just moved to a new neighborhood, and it’s strangely fun to log our daily walks. It’s also been neat to run into other FourSquare users, after recognizing pictures of their dogs.

After using FourSquare for a couple weeks, I was poking around their website, and I decided to connect with all of my various social utilities and import my contacts. I did them all – GMail, Twitter, and of course Facebook. Of all the services, I felt betrayed only by Facebook – that was the only one that took the excuse of me inviting my contacts to also sign me up for Wall Posts. I will almost never connect with a Facebook app for this reason – nearly all app makers will ask you for a slew of permissions, among them making public posts on your behalf.

So after the first wall post I nipped it in the bud, using the convenient way Facebook provides to remove the permission, available from the Wall Post itself. I think the Facebook employees would tell you that the system is working, and they would point out how easy it was for me to get what I wanted in the end. Each application explicitly asks you to post stuff, and you have to explicitly say yes. And then it’s easy to fix things on the back end.

I would argue that both this system and the attitude that fosters it are broken. In almost all cases, I simply say no, and decline to trade my privacy for the small bit of utility of an app. But is everyone like me? How many of these users facing these coercive choices are unable to understand the devil’s bargain they are making? How many are drunk, sad, or lonely? Heck, how many of these people are even old enough to be entering into binding agreements like this? Children who connect with their FourSquare friends on Facebook, and then end up posting automatically to their walls are being exploited in the same way as child actors – the only difference is that child actors are protected by contracts and labor law, and they get paid.

In the end, the Facebook API is a system of coercion. It preys on our weakness for being social, for being cool, and being part of the group. It preys on laziness. And it preys on our children. It’s not exactly a gun to the head, but then again the system isn’t trying to coerce you into handing over the money in the safe, so they don’t really need a gun. This light, social coercion is enough.

Facebook holds up the straw man of simplicity of UI. They claim that the interface makes it easy for you to share and control that sharing, but the simple truth is the interface makes it simple for programmers to coerce you into doing what they want.

The main problem is that applications use the carrot of things like “connect with your friends” to get you to also allow them to post on your wall. This simply should not be allowed – if FourSquare wants to connect me with my Facebook friends, they should not be allowed to ask for other permissions, most importantly they should not be allowed to ask for the Posting Publicly Permission. I can hardly blame FourSquare for this – they basically need to do it to keep up with other apps, but I can blame Facebook for making the rules of the game. This all starts higher up, in the form of a thought in Mark Zuckerberg’s head, that privacy is dead. But it does not manifest until it becomes this API.

The solution is apparent – the API should let you ask for just one permission at a time, for the thing that your app wants to do. At the very least, it should not allow developers to use the ultimate social tool – the contacts import – to erode your privacy. Until this changes, Facebook will never be a trustworthy system, and user ire will build and foment. The end result is unclear, but I think Facebook underestimates the growing tide, and there will be some consequences in the form of lawsuits, regulation, or platform change.

UI simplicity is a straw man – Facebook simply knows that favoring viral spamminess and coercion is a sure way to grow the network, and they will continue to develop the platform that way and hide behind a veil of good intentions and engineering issues. Until there is a change of heart at the highest level, or until people and our governments take action, Facebook’s attitude will continue to define social on the web.

September 25, 2011
0 FacebookTwitterLinkedinRedditEmail
Gaia GPS

How Freelancers are Like Terrorists

by Staff Reports September 20, 2011
written by Staff Reports

Freelancers are like terrorists – you don’t negotiate with them, because it just doesn’t work. The proper way to handle a freelancer is to ask them how much money they would be delighted with, and then you give it to them. And if you can’t give it to them, you don’t hire them.

We work with about 6-8 people depending on the week, who helps us code, design, and write stuff. We pay them anywhere from $25-150/hour, and the common thread in how those rates came about is we just gave them whatever they asked for. And if it was too low, we even gave them more.

You may think that this is going to lead to high costs, and you should be negotiating down the rates. You may think – I should negotiate everything. But this is just wrong, because you may shave a few dollars off the cost in the short term, but you are doomed in the long. Here are the many likely failure cases you will hit:

  1. You hire bad people – People who work for whatever you are willing to pay aren’t in demand, and therefore probably suck.

    Any good programmer will tell you there are a vast array of cushy, high-paying jobs that they can have. In this terrible economy, it’s not the software developers that suffer (it’s insurance salesmen, parking lot attendants, toll-takers, and other irrelevant jobs that suffer if I were to guess).

    It’s easy to suffer a delusion of grandeur here and think that you have such a killer project that you can get rockstars for less than they want or need, but who are you kidding? Unless you have as much caché as Kevin Rose or something (just to name a random famous guy), then your money is the only thing talking.

  2. You lose good people – Congratulations, you have just hired the architect of Facebook’s photo sharing site for your Flickr-killer. Somehow, it just happened – maybe you had a connection, or he saw some spark in your company, or maybe he just needed some rent money because of strange circumstance.

    Welcome to two months later – your start-up is thriving on the back of a rockstar engineer, and it’s looking like Series A is just around the corner. And hey, what do you know – things are looking up for your programmer too – he got his mojo back, sent a resume to Google now that the he’s forgotten the annoyances of Facebook – and your 60/hour (he wanted 100), with a max of 30 hours per week, is both not stacking up very fast and a little embarrassing.

    One day, he comes to you and lets you know he’ll be going to Google soon, and he just didn’t want you to be surprised. At this point, you have your $2.2M in funding, and you offer to match his salary, plus stock (plus even more when he shoots you down). Maybe he would have left anyways, but it would have helped if you hadn’t over-negotiated in the first place… if you were as interested in his needs as you want him to be in yours.

  3. You get billed anyways – Even if you negotiate down the project cost or hourly rate, let’s face it – you are liable to get billed whatever the freelancer cares to bill you. Your minor changes, which he would have accommodated with gusto at the rate he asked for, now become major changes in the spec. Outside of scope. Extra hours needed. Savings down the drain. Who is really to say whether certain behaviors are features or bugs? Well, I guess you, as the project lead should say, and he’ll be willing to listen for just a few more bucks.

  4. The work sucks – Let’s say you even manage to hire a good person, but maybe you are the lowest paying gig of 2-3 he has. Do you think your deadlines, requirements, bugs, or user needs are going to rate? Think again. You’ll get your code, eventually… maybe.

So that gets me back to how I hire freelancers. We just give them whatever they want, sometimes more. The caveat is you have to pair this strategy with both a knowledge of what you are getting, and a willingness to fire people who are doing a good job, but not a good enough job. Not everyone we have ever tried to work with did not work out – some were not fast enough, some not good enough, some didn’t care enough. And each one of those people cost us a few hundred or a few thousand dollars to find out.

In the end, it’s not about getting a good rate, it’s about getting a good value. And you do not get a good value from underpaid, unhappy programmers working on other people’s dreams.

So, if you’re a founder, find someone who you have enough money to excite. And if you are a freelancer, we’re hiring.

September 20, 2011
0 FacebookTwitterLinkedinRedditEmail
Gaia GPS

How We Protected Our Trademark

by Staff Reports September 19, 2011
written by Staff Reports

When I noticed a company had named their new Android app “Gaia GPS to Your Email” I was at first a little excited. I thought someone had made an app that hooked our GPS app into email functionality. Wouldn’t that be flattering!

However, after I checked out the app, I realized it had nothing to do with Gaia GPS at all, and that the names just happened to be similar.

So, next I sent an email asking them to change the name, and that was that, because people are generally nice and cool. The company changed the named to Genie GPS to your Email right away, and they even apologized for the mixup.

I just thought I’d take a moment and thank these guys on my blog, because they really could have ignored me and I wouldn’t have done a thing, Instead, they took a little time and found a new name, just because I asked, and because it was the right thing to do.

My takeaway from this is if you are ever thinking about getting aggressive with someone over a trademark, you shouldn’t immediately pay a lawyer to write a letter. I would hope that sending a personal email, devoid of threats and legalize, doesn’t do anything to endanger a trademark down the road, but I guess it wouldn’t surprise me.

Since it seems apropos, let me also close by saying that we’ve signed The Patent Pledge, and we hope you will too. Not that we haver any plans to file any patents, but I’m told that we’ll feel differently after we grow a tad more.

September 19, 2011
0 FacebookTwitterLinkedinRedditEmail
Gaia GPS

Board Member’s Business

by Staff Reports September 16, 2011
written by Staff Reports

If you need custom cabinets in Pittsburgh, I suggest you check out National Woodwork. One of my board members runs it, so I thought I’d give a little shout out!

September 16, 2011
0 FacebookTwitterLinkedinRedditEmail
Gaia GPS

Technical Post: UISegmentedControl subclass for iOS5

by Staff Reports September 6, 2011
written by Staff Reports

Lately, we have been tweaking our apps to be compatible with iOS5.

One thing we noticed is that the UISegmentedControl, which shows a bar of menu options, no longer works exactly as it did under iOS4. Specifically, when you programatically set the selectedSegmentIndex property, it no longer calls the associated method. Under iOS4, when the user pressed the menu option, or you set the index, the method would run. But under iOS5, it only gets run if the user presses the button. You can see this bug popping up on the internet here.

Rather than put a bunch of logic throughout my code to deal with this, I developed this subclass of UISegmentedControl on the advice of Anna, which works as expected. Download it from GitHub here.

September 6, 2011
0 FacebookTwitterLinkedinRedditEmail
Gaia GPS

iBurn 2011 for Android Update – Wednesday?

by Staff Reports August 31, 2011
written by Staff Reports

We are still working on getting iBurn 2011 for Android out there. The code from last year was very dependent on how the map was set up, and it ended up being a much bigger job to redo this year to accommodate the new map.

We’re very sorry! Given the gates have been open for a couple of days, we know time is of the essence, and we’ll try and get it out by Wednesday. Total SNAFU.

August 31, 2011
0 FacebookTwitterLinkedinRedditEmail
Gaia GPS

Download iBurn 2011 for Android

by Staff Reports August 31, 2011
written by Staff Reports

You can now download iBurn 2011 for Android at this link. If you have trouble installing, download tAttachApkInstaller from the Android Market, and use that option when touching the link to install.

We are going to test this out for a little while now, and then we will also post it to the Market this afternoon for easier downloading. Please email iburn@gaiagps.com with any bug reports.

It’s a little late for the Droid version, but now’s better than never we hope!

August 31, 2011
0 FacebookTwitterLinkedinRedditEmail
Gaia GPS

iBurn Password

by Staff Reports August 29, 2011
written by Staff Reports

Since gates are now open, we are announcing the password:

effigy

If your app doesn’t automatically hit the server, type this in and you should be good to go.

Also, regarding iBurn for Android – we’re still working on it. Sorry for the delay!

August 29, 2011
0 FacebookTwitterLinkedinRedditEmail
Gaia GPS

iBurn 2.01 update now in review – bug fixes

by Staff Reports August 26, 2011
written by Staff Reports

Update: Apple expedited after all. Have fun at the Burn!

We have submitted iBurn 2011 (v2.01) to the App Store, to address a couple of bugs that people reported. Most importantly, iBurn is showing all events an hour late because we goofed on a time zone, and the app is not showing repeating events on subsequent days.

We’re very sorry for any confusion this may cause, and hopefully the app still has a lot of utility. It’s quite a challenge to navigate getting the app put together and approved in time for gates open, with the API in flux, data unavailable until the last minute, and Apple’s approval process on the back-end.

At this point, Apple is not going to expedite the review, and the update probably won’t be live until mid-next week. While they were nice enough to speed through the 2011 release, I guess we’re stuck with our bugs for a few days. If you are a Burner who works at Apple, please help.

Here is the complete change list for 2.01:


  • multi-day events are now listed on each day

  • event times should now be correct (they were off by an hour)

  • added in camps ending in “W” that were accidentally omitted

  • pin labels are now easier to read when overlaid on black parts of the map

  • fixed the location of Pee Funnel camp

  • added a shout out to BurnerMap.com

  • made the Detail screen for Art/Camps/Events more compact

  • added a disclaimer that the data might be inaccurate

August 26, 2011
0 FacebookTwitterLinkedinRedditEmail
Gaia GPS

iBurn for Android will be Ready When Gates Open

by Staff Reports August 25, 2011
written by Staff Reports

Update, 4:43pm, Monday: We are almost done and hope to get it out by tomorrow. It ended up being trickier than we expected.

Update, 11:34pm, Sunday: Still working on it :/

Folks keep emailing and asking if we are going to update the Android iBurn app this year, since the iOS app went live yesterday. The answer is almost certainly yes – we will try and at least have the app as it was last year, showing the map, and it won’t be ready until basically when gates open.

If you are an Android developer, we would very much appreciate anyone chipping in and either getting the app ready or improving it, as you see fit. You can either contact us at iburn@gaiagps.com, or you can simply go to town on the open source code, hosted on GitHub.

Due to the embargo we have to observe on the camp geo-data, we probably won’t publish the Android version until gates open. For the iPhone version, we worked around the embargo by locking up the data in the app, but on Android, we don’t have as many developers, and we don’t really have time to code the app for early release. As I understand it, there should be some wi-fi on the playa this year, so hopefully the early-goers will be able to get it regardless.

August 25, 2011
0 FacebookTwitterLinkedinRedditEmail
Load More Posts

Categories

  • Adventures
  • Android
  • App Comparisons
  • App Updates
  • Backcountry Skiing
  • Boating
  • Company News
  • Emergency Response
  • Featured
  • Fishing
  • Gaia GPS
  • Gaia GPS Offroad Podcast
  • GaiaCloud
  • Hikes
  • How-To
  • Hunting
  • iOS
  • New Features
  • New Maps
  • Newsletter
  • Offroading
  • Out and Back Podcast
  • Overlanding
  • User Profiles

Recent Posts

  • Gaia GPS How-To: Using the Click Drawer on gaiagps.com
  • Meet What’s New in the Web Route Editor 
  • Introducing Adventure Modes: The Right Map for Every Adventure in One Tap
  • Trip Report: A Rider’s Guide to Bikepacking in Bears Ears National Monument
    • Facebook
    • Twitter
    • Instagram
    • Youtube
    • Rss
    • Explore The Map
    • Get the App
    • Upgrade Today
    • Explore The Map Catalog
    • New Features
    • Activities
      • Backcountry Skiing
      • Boating
      • Emergency Response
      • Fishing
      • Offroading
    • Adventures
      • User Stories
    • Help

    @2024 - All Right Reserved. Gaia GPS


    Back To Top
    Gaia GPS
    • Explore The Map
    • Get the App
    • Upgrade Today
    • Explore The Map Catalog
    • New Features
    • Activities
      • Backcountry Skiing
      • Boating
      • Emergency Response
      • Fishing
      • Offroading
    • Adventures
      • User Stories
    • Help