As my Twit­ter fol­low­ers know, I’ve been pretty peeved with Ever­note recently. The iPhone client ver­sion has decided that it absolutely, pos­i­tively will not com­plete a sync with the Ever­note servers on my 3G. I’ve done every­thing I can, even sent my log files to the com­pany (no response as of yet), and all of my tou­bleshoot­ing comes down to the same thing. Even after a fresh reboot of my iPhone, with 30MB of RAM avail­able (the most a 128MB 3G ever gets after load­ing the mobile ver­sion of OS/​X), Ever­note will fight for a while and then either spit up the error mes­sage you see here or just crash com­pletely and dump be back to the home­screen, the typ­i­cal reac­tion when an iPhone app runs out of RAM. (The new iPhone 3GS seems to run Ever­note just fine, but then it would; it’s got 256MB of RAM, or five times the free RAM on boot as the 3G has, 150MB com­pared to 30MB.)

The prob­lem with this is that up until just a cou­ple days ago, the mobile web ver­sion of Ever­note wasn’t all that impressive.

This was a pain in the ass to use on my Win­dows Mobile devices, and it’s a pain in the ass to use on my iPhone. It’s a sim­ple WAP-​style page that doesn’t do much. But hey, it worked on my iPhone when the ded­i­cated client didn’t, so at least it was some­thing. I only used it for look­ing up notes, opt­ing to email new notes to my pri­vate Ever­note email address when I wanted to cre­ate some­thing new. It wasn’t pretty, but it worked.

Well, now it’s pretty too.

The new ver­sion of the mobile web Ever­note uses some nice iPhone/​Androidish CSS to look far more pro­fes­sional, more like a real app than a web page. It even sports some slick new menus that are both touch friendly and easy to use.

It’s a webapp rather than a native app, but that really isn’t a prob­lem for me. I’m already using the Safari-​optimized Gmail instead of the iPhone’s Mail client for read­ing my Gmail, the Safari-​optimized Google Reader instead of Byline, and iPhone-​friendly ver­sions of Google News, AP News, GoodReads, Wikipedia, the list goes on and on. Using webapps instead of native clients is a way to mul­ti­task on the iPhone with­out jail­break­ing and run­ning Back­grounder since you can have up to eight pages open at a time. And the inter­face for man­ag­ing them even bears a strik­ing resem­blance to man­ag­ing cards on the Pre.

Only one prob­lem remains, really. There is a JavaScript-​based clip­per avail­able for Safari Mobile that allows you to send what­ever you’re cur­rently look­ing at to Ever­note. The JavaScript looks like this:

javascript:location.href=‘http://www.evernote.com/clip.action?url=’+encodeURIComponent(location.href)+’&title=’+encodeURIComponent(document.title);

And it works.

The prob­lem, as you can see above, is that this script directs you to the full size ver­sion of Ever­note rather than a mobile page. This is espe­cially awk­ward when try­ing to tag what you just clipped.

I’ve tried every vari­a­tion I can think of to merge the JavaScript above with the URL of the new mobile site:

https://www.evernote.com/mobile/MobileSetup.action?noRedirect=true

And noth­ing seems to work. So for now, I’m deal­ing with the awk­ward clip­ping in Safari, but pretty happy with the rest of the Ever­note Mobile Web expe­ri­ence. So much so that I’m really not even all that wor­ried about the iPhone client. The mobile web ver­sion does almost every­thing I need, and for the rest — pho­tos and other mul­ti­me­dia — I can email stuff to Ever­note. All I’m really miss­ing is the iPhone client’s offline favorites, but I’ll live.

I had just about quit writ­ing alto­gether. I’ve been try­ing to build up enthu­si­asm for a num­ber of dif­fer­ent writ­ing projects recently, get­ting just a lit­tle enthu­si­asm before los­ing inter­est in each. I had nowhere near the spark nec­es­sary to see an entire novel through to com­ple­tion. Basi­cally, writ­ing wasn’t fun any­more, and it hadn’t been in years. And I’d got­ten to the point where I was almost ready to give it up completely.

Yes­ter­day I noticed on Twit­ter that one of my favorite authors, James Rollins (@jamesrollins on Twit­ter), hap­pened to be here in Den­ver and was going to do a book sign­ing at The Tat­tered Cover, Denver’s awe­some inde­pen­dent book­store. More to the point, he was going to do the sign­ing on my side of town, at a store I didn’t even know they had. See­ing as how I didn’t have to take my oddly-​overheating car all the way down­town, there was no way I could pass that up. I even hap­pened to be read­ing his lat­est book (fin­ished it today).

I’d admired Rollins for many years. Like me, he had no for­mal train­ing in Eng­lish or Lit­er­a­ture, and con­tin­ued his vet­eri­nary prac­tice for many years before switch­ing over to being a full time nov­el­ist. He writes exactly the sort of books I enjoy most, a mix of adven­ture and really inter­est­ing sci­ence. He’s one of the authors pub­lish­ing today whose books I’ll buy as soon as they hit the shelves, sight unseen. I’ve got a num­ber of inter­est­ing obser­va­tions about the talk (which will be avail­able as a pod­cast soon), but that’s not the point of this post.

After the talk, I walked up and had him sign my iPhone (get­ting his auto­graph in Sim­ple­Draw, then send­ing a screen­shot of that to my cam­era roll) and asked him my ques­tion. I told him I’d been a sto­ry­teller in one way or another most of my life, but that I’d started to lose the faith. Writ­ing wasn’t fun any­more. What advice did he have?

First he told me to keep send­ing out queries. Sub­ter­ranean, his first novel, didn’t find an agent until his 50^th try. He’d send out ten queries to ten dif­fer­ent agents. If he got back a rejec­tion, he’d imme­di­ately send out a query to a new agent. If he got two rejec­tions, he sent out two new queries, always keep­ing 10 in cir­cu­la­tion. This is good advice, but in and of itself didn’t help much as I’ve already pub­lished all my fin­ished works, and indeed did so a decade ago.

But the corol­lary to this first bit was what really got me think­ing. He also said to keep writ­ing, because once you were writ­ing some­thing new you weren’t quite so attached to what you’d already sent out, and it get­ting rejected didn’t hurt quite so much. I con­firmed that this only really worked if you were writ­ing indi­vid­ual sto­ries, not an ongo­ing series in which every­thing you wrote was depen­dent on every­thing else, and you could be sunk if the first item in the series didn’t sell.

I thanked him, shook his hand, and wan­dered out of the book­store with my mind rac­ing. It occurred to me that I hadn’t really had a new story idea, well, this cen­tury. Or at least since Josh Curry and I were work­ing on Heroes 101, back in 2003. Every­thing else I’ve done this decade, even my NaNoW­riMo 2006 novel and my attempt this year at Script Frenzy, were ideas I had a long time ago and just finally got around to doing. I haven’t come up with a new idea, a char­ac­ter I don’t already know, in years.

And sud­denly, I knew why writ­ing wasn’t fun any­more. Because there was no sense of dis­cov­ery, no sus­pense, no adven­ture. No mat­ter which project I tried to work on, it was all well tread ground. I hadn’t fin­ished any of these works (although I got 80,000 words into the sequel to Between Heaven and Hell, just a few scenes from the end), but I’d been pick­ing at them for so long they were lit­tle more than bleached bones.

I need new sto­ries, new char­ac­ters, new ideas. And I’m start­ing to believe I can find that well­spring of cre­ativ­ity again. That I don’t have to keep cling­ing to ideas I came up with in my 20s. More impor­tantly, I’m start­ing to believe I want to.