How should EagleTweet decide, which level of location to use?
At the moment, we have this:
Not very pretty and at least I think it’s not too obvious what exactly is happening and why the tweet selector has checkboxes and the location selector radiobuttons and so on. It does, however give the possibility to rather fine-tune how EagleTweet is working. For a while I had mine set up in a way that it sets the location to my current city but only send a tweet when I am in a new state.
Confusingly enough there is already some other place where you set the location you want EagleTweet to know:
The FireEagle settings. Now I ask you – is it too confusing to have multiple settings? Should it just be “Tweet/Don’t tweet” and “Set location/Don’t set location” or is the current fine tune system better? Or do you have an even better idea?
Filed under: Poll | 2 Comments
Tags: FireEagle, Settings
-
EagleTweet is a small service that updates Twitter with your location from FireEagle.
Why don’t you just keep the settings, but hide them until one clicks on an “Advanced” link or something like that? Fine-graining is good, but keep it simple.
I like that. At the moment I’m experimenting with an interface that doesn’t show the advanced settings unless you chose to send a tweet or set the location. I will definitely try your suggestion, which should unclutter the interface even more.