P.S. You should apply for a Developer Key, and you should implement OAuth authentication (for getting a token for the user who'll use your application).
Yup, less is more. Especially on an application main page. If you explain it somewhere else, just put a huge pretty button to click to find that guide, and don't give them directions anywhere else except the FAQ/Documentation page you have.
ask for less from Facebook. I didn't even try it based on your permission requests. I'd recommend asking for just the minimum of what you need and then if they need to access a feature that requires more ask for it then. Do a progressive rights request or have some video explaining the service.
Right now with the simple design and just text most people won't offer you their Facebook rights.
Thanks, I'm working on it. I'm still trying to figure it out for myself. It was something I know I wanted...and I use it constantly, but I'm still trying to figure out how to explain what 'it' is.
Ok...so where do I get started. I've seen a lot of command lines over the last few weeks and nothing in them gave me the impression that there was any sort of logic or automation going on. The all look like just one thing is happening. (And that is one of my strikes against them is that they seem to completely lack context)
Start looking into bash scripting, for one. Learning a scripting language like python or perl can do a lot of the same things and is valuable in other ways.
To your comment of looking like just one thing is happening, that is understandable to the untrained mind. Let's take an example where I want to delete all the .bak copies of my old configuration files. To do this I would enter the directory and simply type:
rm *.bak
It's one command, but the star is expanding it to match every file that has a .bak ending. One command line entry, many executions of the 'rm' command.
Yes, context and a trained eye are everything. I like to think that working on the command line is one of many styles of working. It works very well for me in some situations, so I suggest to others to try it out and see if it would fit their needs as well.
Bash is probably the second worst thing unix has to offer, right after vi.
The command you demonstrated is only slightly faster than sorting the directory by type in a file explorer and selecting them with mouse and selecting delete from context menu, and much more dangerous, ie. when you mistype it as rm * .bak you just deleted everything in that folder permanently, whereas in a GUI you would've seen what you actually selected, and most likely only moved them to trash, not permanently deleted them right away.
I'll give you that the flexibility of the command line can be a help if you're really trying to do something outside the lines, but I'll disagree with the second. If we were in 1998 I'd agree, but with the remote desktop tools we have today there really isn't much of an advantage unless you are bandwidth limited.
I really like your text implementation. I've done something similar at http://www.mindwallet.com . I've added a social layer on top. You can post directly to facebook/twitter and keep the posts in context. People can reply in line by adding sub items to your lists. I'm trying to put an api together that lets users create all kinds of apps. I think there is a opportunity for this kind of interface. Maybe we should put our heads together.
You should give it a try. You might surprise yourself. I recently started getting up at 4 just to see what would happen. I've got a ton more time and occasionally need to take a nap around 5-7pm, but other wise have been fine just getting 4 hrs a night.
Hmm. I doubt that would work for me. Less than 8 hours sleep and I'll be s total wreck in no time. I also read somewhere (don't have references) that 7-8 hours sleep is optimal. Naps give me a headache. Can't sleep on a bus/train/airplane either.
I'm trying to do something similar with outlines. It isn't so much a text editor as it is a social collection builder. I call it insanely organized social media. You can call it http://MindWallet.com .
So, for the sake of potential future features that you think people might want, but haven't yet implemented, and don't really know for sure, you make it harder for people to use it now. For the sake of making it "future proof" you put hurdles in place to prevent people from using it now.
People using it now gives you a working group of testers for new features. Don't make it harder for them.
Actually, let me be more clear. One of the core features is that we let you post to facebook directly from mindwallet. We then need to read your stream to let you know when you have new comments. The fb post and comments are given an inherent context by were in your mindwallt you post from. This extends the life of your post beyond the usual temporal stream. The perms we ask for are:
1: email to establish ownership of your mw account.
2: post to wall to let you do so.
3: read stream to show you new comments
4: offline access to show others in context comments when they look at your mindwallet.
I think I can remove friend's stream for now, but that is the only unimplemented feature.
It is mire than that. But you have to read past the first bullet and that is a problem. I'm still tring to figure out what it is myself and I use it constantly.
Mindwallet looks neat. Quick feedback: the +/- signs are too small and frustrate me when I want to expand/collapse. If you made that interaction easier the navigating would be a lot simpler.
