Man I’m sorta’ ticked about WordPress 2 for the iPhone. For one, it has a known problem for some users (a lot of of users!) that it doesn’t always save posts. What happens is when you have a post your working on, 25% of the time WordPress 2 won’t save what you’ve written. This was never a problem with WordPress “1″.

There’s no fix if you experience this issue. You get that? There-is-no-fix… The only way to get this issue fixed is for WordPress to update the app fixing the bug. Problem, from the release of WordPress 2 to today’s date, they’ve released app updates and none of them have fixed the bug or even addressed that it exists.

People have said online that you can hit “publish” as soon as you start your post as a workaround to this problem. That’s a stupid idea because that makes your post LIVE for people to read while your still writing it, typos and all. And also, you must be online at all times to save this way, which includes the same option of saving it as a public draft. You want to keep your posts saved as a local draft, and then publish once it’s finished. So this isn’t possible with this “saving bug”.

So now, I’m typing up my posts with the Evernote app and then copying and pasting the text into the WordPress app to post. I’ll have to switch to WordPress 1 or choose another blogging app. This sucks.

What kinda’ issues are the rest of you facing? When did this start happening and have you found any work around or… anything? If you another blogging app for WordPress, what do you think? I wanna’ hear from ya.

Peace, JbB

I saw, featured in the app store, that a version 2.0 of the WordPress app came out.

Edit: Ok, I don’t know how well this speaks for the new version… but see the images above there? This new version of the WordPress 2.0 app messed up my post. It lost 90% of the post I wrote… just for no reason, so I’m having to jump on the Neocomp (my desktop) to write this post again.

A new version of WordPress came out, version 2.0, but the odd (messed up) thing is that it’s not an update from 1.x but a separate app. Meaning, if you have WordPress 1.x, you won’t get an update notification to upgrade to 2.0. You have to actually go out, find WordPress 2.0, install it, and then uninstall WordPress 1.0. Yes, you will have two different WordPress apps installed, 1.x and 2.0. I don’t know why they did it like this… but it’s ok, we outta’ be thankful they provide us with a completely free blogging system and completely free blogging app.

As far as the app itself, not much has changed. They’ve fixed (I’ve confirmed) the picture order issue, where you would select from your iPhone pictures in order of “A,B,C” but they would be order on your post as “C,B,A”. The work around for it was to select your pictures in reverse on your iPhone, which the WordPress app would then reverse the order and you’d get the pictures ordered the way you wanted. But they’ve fixed that issue, so “A,B,C” will be ordered “A,B,C” (“as easy as 1, 2, 3…”).

It’s got a great new comment managing system, which is really nice. But other than that, there isn’t much that’s been changed as far as features go. They have fixed a lot of bugs and polished the over all improvement of the app… but the fact that the very first post from the app, a post about the app ironically, messed up and lost 90% of the text for my post kinda’ worries me… But let’s hope that was an isolated thing, ‘ight?

Peace, J

The new Neocell 3GS. What can I say about it, but “andale, andale, ariba!!” Yeah baby. The speed of my new 32GB 3GS iPhone is so amazing. You have no idea how amazingly fast the speed is. Let’s start by comparing the speed of 2G / 3G.

We’ll take the old Neocell for example. Being jailbroken with OS 3.0, I couldn’t run Pandora in the background for very long without it crashing (closing in the background from running out of memory). And we’re talking about doing simple things, like typing in the WordPress app. In short, running a program in the background such as Pandora would crash in about two minutes or less… and if it didn’t crash, it’d make the system so sluggish while running something in the background it wasn’t even worth it.

Now we compare the same settings and systems for the Neocell 3GS. I’ve been running Pandora in the background 70% of the time I use the Neocell (including driving places) and Pandora hasn’t crashed once. Not one single time. I’ve even ran it in the backgound of some intensive applications. I’ve been running Pandora in the background while the Tomtom car navigation app runs with zero lag, as well as in the background to some video games, such as Geodefense. You heard me right… not once crash or even lag since I got the Neocell 3GS.

I can’t believe the speed this baby’s got. It’s amazing. Now, for those of you who have a 3GS and are jailbroken, don’t be temped to go out and load it up with all this jailbroken garbage like Winterboard of SBSettings (you heard me right). Having a 3GS is like upgrading from a truck to a sports car. Don’t go loading up that sports car with a trailer full of wood. That sports car will still be faster hauling wood than your truck was, but it’ll no longer be as fast as a sports car. Don’t go loading up your 3GS with jailbroken garbage, or you will make it no faster (even slower) than a non-jailbroken 2G or 3G iPhone.

Peace, J

Backgrounder, I luv ya baby. So… so… so glad’ta have you back!!

As you can tell from my excitement that I’ve got Backgrounder runnin’ successfully on the new Neocell.

For those of ya new to theneocell.com, I was (am) a big supporter of Backgrounder, the jailbroken app that let’s you run programs in the background. (I’m running Pandora in the background while I type this post in WordPress app as we speak). Well I stopped using Backgrounder because the old Neocell (a 16GB 2G iPhone) could barely run anything in the background and, to keep the speed of OS 3.0 up and keep it as snappy as an unjailbroken iPhone, u had to uninstall it and stop using it. I’ve said before that, if / when I get an iPhone 3GS, with it’s faster CPU and more RAM, I was gonna’ try Backgrounder again as it should be able to do it’s thing without causing the system to be sluggish.

Well it seems to be doing good so far. But, I know from experience that I need to wait about a week or so to see if the system slows down in speed at all.

But… so far so good.

Peace, J