Developer POV: Dave Haupert from DDH Software, on HanDBase, webOS, and Palm | webOS Nation
 
 

Developer POV: Dave Haupert from DDH Software, on HanDBase, webOS, and Palm 59

by Jonathan I Ezor Mon, 01 Nov 2010 12:42 pm EDT

With the recent announcement by MotionApps that webOS 2.0 would not include the necessary files to enable its Classic PalmOS emulator to continue to function, Classic users have been scrambling to plan how to transition away from their remaining mission-critical PalmOS apps. Among the many PalmOS apps still in active use is HanDBase, a flexible, powerful relational database that enabled users to create more than 2000 "applets" for a huge number of functions from medical to education to personal.

While DDH Software, the developer of HanDBase, offers versions of the software for almost every major platform (desktop and mobile), it does not have a webOS app. Nor, apparently, is one currently in the works, according to DDH's president and owner, Dave Haupert. In a pair of e-mails last week, Dave laid out his great respect for Palm, PalmOS and webOS, but also explained the company's lack of plans for a webOS version of HanDBase, driven both by the current state of webOS development tools, and the unknown number of potential customers. With his permission, we are sharing his words with our community (you'll find them below).

Here's hoping that the many existing and potential HanDBase users now on webOS devices demonstrate their interest by contacting DDH, and that the Developer Relations folks and their colleagues at HP/Palm continue and expand their efforts to encourage and support not only new developers, but those that (like DDH) are already aware of the power of webOS and the loyalty of the Palm user community.

(The text of Dave's e-mails can be found after the break.)

In reply to a question about the discontinuation of Classic, and whether there would be a native webOS version of HanDBase, Dave wrote,

I was saddened to see HP/Palm further abandon their loyal PalmOS userbase by dropping support for Classic. The PDK was a step in the right direction, but it's very slow in coming- as of now apps written with the PDK can't mix WebOS technologies and so the entire UI must be done in C/C++. Hopefully they will graduate from that soon as their site has been promising would happen after 1.45.

Unfortunately we don't have any immediate plans to develop a WebOS version of HanDBase. I continue to follow these things very closely and when both the toolsets are in place, and a large enough number of customers are finding the platform compelling enough to support with their purchases, I would certainly revisit. I hope that HP does indeed do a lot more with the platform- the Pre 2 and WebOS 2 both seem like a very small step for the platform when they needed a bold leap to leapfrog the momentum of the competition.
 

In a followup, Dave accepted an invitation to expand on his thoughts for the PreCentral community:

Surely- anything that may help both customers and Palm. I still have a fond place in my heart for Palm- the original Palm devices were my inspiration to start my own software business, and I spent many years working intimately with them and their products. I hope they can find their way back on top, and when WebOS was first announced and released, it seemed like the first step they needed. But while it was good to embrace new technologies, start with a fresh new design, and reduce reliance on legacy compilers and software- the truth is that there could have been a better way- a way to import a project from it's [sic] old Metrowerks Codewarrior backdrop into a new environment and allow retooling of the UI for the new interfaces, rather than have to start from scratch with new coding languages. I have hundreds of thousands of lines of code in C/C++ libraries for doing things like encryption, calculations, fast sorts, indexing, etc. But I am sure they weren't interested in the developers of yesterday, figuring there are more than enough web developers who will embrace the new technologies. But where they failed is that they left behind many developers loyal to Palm, who were acting as their ambassadors to users, and many users who were loyal to Palm, wanting compatibility with the software they had been using for many years.

I don't know if you remember those UI skinners that existed for Palm OS back in the day. There were some that made the PalmOS seem beautiful/gorgeous/up-to-date without any app having to recompile anything. Can you imagine if they would have provided tools to reskin the UI of PalmOS applications to run on WebOS with some tweaking to the code and UI design done by the developers? There's no reason those apps wouldn't run and match the UI appearance of WebOS on the device. And Palm would have shipped out of the gate with many thousands of unique applications that started on Palm, not ported from iPhone or Android. And all the users of those apps would have come along for the ride as well, recommending and showing their apps to their friends and coworkers. I heard from countless PalmOS users who decided to switch to iPhone, Android, BlackBerry, etc because they were having to start all over with their apps, and felt they might as well do so with a big brand with lots of apps already available than take their chances with Palm.

It's unfortunate because as you and I know, the WebOS design is elegant, natural, and highly functional. It would be a real shame if they don't end up near the top of the heap!
 

We agree with Dave: it would be a real shame.

Category:

59 Comments

wait a second. While I agree with what he said about developers jumping on a platform that could offer a larger potential for revenue, he has an iphone app on his website. If porting an app from the iphone is as easy and quick as some have already said it was (ie: angry birds, etc), then why doesn't he just port the iphone app over using the tools Palm provides and leave the PalmOS version behind?

I'm not a developer, so don't flame me here. I'm only regurgitating what I keep reading on these forums day in and out.

Porting iPhone games (not apps) is potentially easy. With regular business and productivity apps, you'd have to re-write most of the app from scratch. They could re-use some of their C/C++ libraries using a PDK plugin (once Hybrid apps are able to be submitted to the catalog), but the rest would have to be re-done.

So I completely agree with their rationale. It makes no sense to invest so much development time into a platform that they feel doesn't have a large enough userbase.

So all this talk about pdk, easy porting of apps, it was designed to port easly games but not productivity apps? If that's the case then it's a serious problem. Developers wait for bigger user base........ Users might wait because of limited apps for webOS. Do you think just because HP will make a great hardware for webOS, users will buy it without making sure it have productive apps?

I'm guessing most iPhone games do not make use of the iOS Objective-C UI classes and just use OpenGL. Cloning those UI classes would be much more difficult and would probably result in legal action by Apple.

welp, I can't find fault with anything he said...

but I was under the impression that webOS2.0 brings with it hybrid applications...

I can, Mainly with his first statements about the PDK and no way to use WebOS technology and being required to do the UI in C/C++. They are called hybrid apps, they are not offically supported in 1.4.5 but they still run so he could probably create his app and test it fairly easily on 1.4.5. With the release of WebOS 2.0 there is support for hybrid apps. He has either not looked into the features of WebOS lately or he just doesn't think there is enough demand. Which is also going to be a joke because HP is going to automatically make the demand increase due to their name, money and connections. Hopefully he takes another look at WebOS's soon and decided to create some apps.

I can.

Sometimes you simply have to let go of the past. Hanging onto a chunk of old code in order to support a very small number of users who are clinging to the past is simply bad software design.

Move on, get over it.

His whole statement is ridiculous. I wrote Palm apps in the 90's and I remember that guy from the old mailing list. We wrote all our apps in C/C++. That's what we did. There's the PDK. C++. If he could figure out C++ on PalmOS, he could figure out C++ on webOS with the PDK.

The hardest hurdle for me was javascript. I had been developing the web services for awhile, so that wasn't a problem, but picking up javascript was annoying. I'd imagine that for an app developer like David, that would be the hangup. But his app is a totally ideal candidate for the PDK. All he has to do is set it up as a local service with a backend that gets passed the SQL strings and allow people to write their own little javascript frontends to hook into his framework running on top of his database. Granted, it might not be the same simple framework that he has on other platforms, but he could do it, no problem. If he paid me, I'd do it for him.

Yeah, I thought the same thing. WebOS 2 does bring hybrid apps among other pretty awesome changes and improvement. I don't get his "small step" comment regarding WebOS 2 at all. I (respectfully) think that it's totally off base. Now, the Pre 2....

sad, real sad...wish Handbase comes to webOS, miss it since my Treo days

So another software vendor has bailed on us. And that on top of key staff jumping ship? Not looking good for the platform these days.

One of the few apps I missed when I moved to webos. Can't really argue against anything he said.

How many users were there for PalmOS when they wrote their first app? Is it actually less than there are now?

listen lets decode what he said.. He likes Palm as a company that brought innovation to the table when they first started... However he doesn't like the users because there are not enough of you to keep paying his car note on his BMW or Porche or both.. So he's jumping ship and concentrating on Android and iPhone to make money.. He's not in it because I likes what he does anymore.. He's in it for the money... So he could really care less for the users.. Your all just dollar signs to him..

and not to sound like an a-hole but come on people move on.. I don't understand the hang up on people NOT letting go of stuff from an old OS that's just legacy stuff.. I miss some things about my old PalmOS.. Not enough to actually get the classic app that allowed me to use old apps from an OS that's years old and super way behind the curve to todays standards...

the classic app was (as I can see) Training wheels for people that couldn't adapt to WebOS right away... It's been over a year now and it's time to remove the training wheel and ride the WebOS two wheeler like a big kid now.... Stop bein scared of change.. If it weren't for change I'd have to still rub 2 sticks together to be able to light my cigarette

While I do agree that people using the Classic emulator should be moving on to native apps I really don't think you can fault someone for wanting to make money . . . . They do have to live too.

I have one app I use the Classic emulator for... But I use it every day, and can't find a suitable replacement for in the standard catalog. (The developer even has a 'lite' version in the app catalog, but it is missing features I need.) I would love to move that app over to a native app. I don't have a choice though.

I still have a working Palm T|X. If I have to, I'll start carrying that again, just for that one app. I'd probably start looking for a new phone at that point as well.

Wow. Just...wow. Your comment is so...uhm...well...the thing is...do you really...oh never mind. smh

Hey, yoshiaka13 I just gotta reply.

I haven't even switched to webOS yet, I am still using my Treo 680 because the new OS isn't up to speed regarding textual apps.

No spreadsheet app, no database app (have tons of JFile databases), no decent memo app, no text file editor (I use SiEd), no outliner (I use Shadow), no TreePad-like app (I use ScrapBook). An appointment book which is worse than the PalmOS one which in turn is not as good as DateBk6)... I could go on

WebOS as-is is aimed at web-centric tasks, media and such like which I would love to have but not at the expense of PDA apps that I use daily.

Google docs work ok for a spreadsheet. Have you looked at Notes, Noted!, Scratch or any other apps? If so, what features do they lack? Their developers would probably welcome the feedback. Given it has sql on the device, I would have thought someone would have put together a database front end by now. Creating a list of features that used would probably help out developers looking for a new project too instead of just complaining that application XYZ hasn't been ported. Complaining to the publishers of the old apps would be more useful than complaining on here though. I can understand the need to vent, but IMHO most of the complaining on this site serves little useful purpose.

hrminer92, "Google docs work ok for a spreadsheet" - I don't want to have to rely on a working Internet connection to enter data into my PDA!

Wasn't complaining - just saying in the hope that someone at HP was listening.

Have e-mailed author's of my favourite apps. Always the same answer - Palm hasn't provided the hooks into the OS for them to do the work... and ROI.

I wonder how easy it would be for Google to make a Google Docs app for webOS. I wonder if HP could make it easier for them...

RogerL, for an outliner/task list manager, have you tried Outline Tracker? There's a Shadow Plan export template: http://outlinetracker.com/outlinetracker/migration.html#ShadowPlan

DougReeder, thanks for that, looks good. So that's one app ticked off the list.

+1

Well, with that said, it seems he is laying out a good explanation as to why Palm stumbled during the initial release of webOS. And I think his words should be taken in with great thought and consideration. With all this talk about hardware, we seem to forget that one of the biggest,if not the biggest, hurdles hp Palm is facing is a user base. Like the elections going on, hp palm needs to tap into and rekindle the productive and beneficial relationships they have shared with the old PalmOS developers. Hp palm needs to win them back. With the anticipation of 2.0 this would be great way to really regain some marketshare. Dave stated that developers were the ambassadors , and there seems to be no good reason why hp palm can't get those ambassadors back to the table and work out a solution. webOS 2.0 is fresh and new and new developers will come, but make it easy on yourselves and do some courting of these old ambassadors he is speaking of. Attract more devs, attract more users.

I hope we see our first set of hybrid apps at palms dev conference. I'm sure all the developers are still under NDA on the details, but if porting non game apps is as easy as regular PDK apps we might actually see a nice uptick in the quantity and quality of the apps.

Message moved

My first paid programming job was developing software for PalmOS, I enjoyed that work but I really think Palm would have been doing us a disservice if we'd stayed backwards compatible. Take PalmOS 6 for instance, it was ready for devices, it was had backwards compatibility built in but nobody ever used it since it was only putting lipstick on a pig.

I can absolutely understand his frustration with not being able to integrate with the native webOS UI at the moment from C/C++ code. I really hope the hybrid SDK becomes available soon and is a great tool.

But allowing developers to use Metrowerks (which was primarily meant for Motorola 68K processors, not arm, it's ancient and no longer supported) would have been silly. Palm had a new philosophy for apps on webOS than PalmOS, allowing developers to "port" apps to webOS by recompiling would have ended up keeping the old philosophy around way past it's best-by-date.

Love your lipstick on a pig analogy! I wasn't advocating using skins and running old apps, using Metrowerks, and not moving on, I was advocating an upgrade path for apps, so the app could import as a project into the new environment, be handled and tweaked accordingly so that it matches the new design paradigms, etc. HanDBase, for example, was finger friendly since 2003, with big graphical buttons and sliding up menus that resemble what was used on iPhone 4 years later! So there was no reason I couldn't have a way to update what I had further without having to start over.

Think of how you can run an app on Windows 7 that was written for Windows 95. If you do nothing, it looks really dated, but if you import your older project, redesign the UI to match current paradigms, you can continue development with only a month or two of work and not a year or two.

Any Palm OS developer who is still around has survived by jumping ship. I think it's safe to say that nobody has been able to make a living developing software exclusively for Palm products over the past several years. I would be hesitant of jumping back on to an unproven platform. He would be better off spending that time and effort developing additional apps for the platform he is most comfortable with - especially if there are many more potential users.

The fact is that people who use a relational database on a regular basis are few and far between. It's one of many niche markets that are best accessed via the most popular software platforms. If you are a user of this kind of niche product, don't expect much support for such a minority platform.

The majority of HandBase users use it for flat-file databases (which are many), not relational (which are few and far between)

He highlights what we all knew when the Pre and webOS were released; Palm made a mistake in not providing an easy way to run old apps on the new hardware. I'm not a software wonk so I don't have any idea or appreciation for how hard that would have been, but is was a huge mistake not to accommodate the thousands of Palm OS apps that were out there.

Having said that, it is time to move on. I have found workable replacements for most of the Palm OS apps that I miss and used all the time. (Though Klondike by Electron Hut is still the best and my wife uses it still on her Centro.)

I hope that the old Palm developers will eventually release their classic apps for webOS. But, if they don't, that will leave room for the hungry and creative webOS developers to fill the gap.

So, all you devs out there, how about a good database app? And, while your at it, how about something as simple and elegant as Electron Hut's version of Klondike. And finally, Simple Bible guys, you know who you are, can you please get the Pro version out before we get webOS 2?

OK, I feel better. Thanks for listening.

Thanks all for your comments. I wanted to respond to a few of them in particular:

- I know you can technically mix the PDK and WebOS technologies, my point was being that this still isn't an officially supported option for us to develop and sell applications. It's taken a pretty long time (in this fast paced industry at least!) since the PDK was available to test with that I'm surprised it's still not an option we can use as developers in the market yet.

- Porting an app involves porting both the backend code and logic as well as the User Interface. Whereas having the PDK means we can more easily port (rather than rewrite) the backend and user logic from other platforms, the UI is the involved part. I just released the app for our Android version. On Android there is something called an NDK which is akin to the PDK on WebOS, except that it's been an option for developers to submit their apps to the store for some time. Despite having that, it was still a solid nine months of development work to rewrite the dozens of screens of UI and interconnecting the two before we could have an app. The same would likely be true on WebOS.

- I will admit that there were less than a million users on PalmOS when I started developing for it. I had a day job, and didn't need to make my entire living on Palm software either. And then again, the average cost of an app was not 99 cents back then!

- yoshiaka13, I don't think you're the only one who thinks it's time to move on from Legacy stuff- HP/Palm obviously agrees with you! The reason people are hanging on to old software, or have an interest in seeing old apps updated to new platforms is because there is no replacement for it on the device! HanDBase is used by many for work purposes, and the lack of that ability on their new device is significant to them.

- Don't have a BMW or a Porsche- I have a Lamborghini ;) Just kidding- I actually drive a 12 year old bomber which I incidentally paid cash for when I bought it new (using the money I made selling Palm OS apps). So while I'm not "rich", I have made a happy living doing this, and I have never been in this purely for hobby or love of technology. This has always been a job for me (though a job I enjoy doing), and the way to pay my bills so I can do the real things I love- spending time with my family, fitness, music, etc. What yoshiaka13 said echoes the thoughts of so many people on the internet, that we developers must be evil money grubbers if we're trying to have a paying job in the software industry. I think it's great that many people make this their hobby and don't ask for money for the work they do, but please let's not annihilate those that do this as, in fact, their job! It is possible to do something passionately and with integrity and still make a good living. That's what I'm seeking to do and why I can have a fondness for Palm as a company, since I'm grateful for the opportunities they've provided in the past, yet make a business decision to not develop on their newest platform because I don't feel it's the smartest decision I could make.

I keep telling customers I hope to be wrong about this- I want WebOS to do well under HPs leadership so that I can revisit this in the near future!

I am guessing that there are many of us who would gladly pay more than 99 cents to get the proven apps from the Palm OS days. Too bad you can't to a pre-buy to test interest on Hand D Base. It was one of my favorite apps too.

I seriously wish you contact palm and get an early start into PDK/SDK hybrid. This community with over 2.5 million people would love to see your app and pay for it too. With H/P in picture and palm pad coming out, I can only see the numbers increase. Again hoping and wishing you would want to join us back.

Just wanted to say thanks for posting a reply here.

Just wanted to say I'm still using handbase on my palm TX because I've found no good replacement on webOS. It's a great product! I hope we see a webOS version some day.

I hadn't realized the irony that you can port an app made for the iphone, but you can't port an app from PalmOS.

I'd certainly like a database program for WebOS (once I've bought a Pre 2) as I use MobileDB on my Centro at work right now. I guess I'll keep the Centro for work and the Pre for play!

Its great to hear directly from respected developers on this forum - I think PalmOS created a lot of loyalty over the years.

It's because of developers like these that we even have a developer problem. They became lazy and never ported to webOS, Palm's next platform. They followed the money and ported to the other platforms, leaving their former customers out in the cold. What could former Palm customers, who relied on these apps, do? They couldn't transition to webOS since their critical apps weren't ported. They could use Classic if they wanted, but they had to know that the developers making the Classic apps would eventually drop support for an outdated OS, and as has been made obvious HP wasn't interested in supporting an outdated OS either. Former Palm customers had to make the jump to other platforms to have a guarantee of keeping their apps for a few more years.

Then again, maybe it was Palm's fault for deciding to support Classic in the first place. They could have pressed PalmOS developers to port their apps to webOS months before webOS was released. At least then PalmOS would have peace of mind when transitioning to webOS. But PalmOS developers saw that their apps would work on webOS, and got lazy about updating their apps. Now the whole thing is such a mess. Palm dropped the ball, these developers dropped the ball, and now customers suffer because of it.

You cannot expect developers to support every single OS out there. They have to consider their resources and potential ROI. When Palm decided to leave PalmOS behind and create webOS, they created a NEW OS. Users always have a choice when it comes to an OS. Palm didn't rip PalmOS out of any of the devices that ran it. They offered new devices that ran the new OS. At this point, a user needed to decide for themselves if they were going to either stick with what they had or pick a new OS. If decision was to "go to a new OS" the choices were whatever the available new OSes were at the time (this includes webOS).

So, it is not laziness on the developer's part. Multiple OSes emerged and anyone with the smallest sense of business would evaluate the landscape based on perceived return on investment, and choose accordingly. It's business, not personal. At some point, consumers must accept responsibility for their purchases. For example, it took me a long time to move from Windows to MacOS because the software that I needed was not available on MacOS. So I waited until I either no longer needed that software or there was a version for the Mac. No matter now "nice" the Mac seemed, it wouldn't have done me any good at the time if I couldn't get my work done on it.

Now, whether Palm misrepresented themselves by letting people believe webOS would always be backwards compatible via Classic could be up for debate. But a developer that leaves an app in good running condition when an OS is abandoned, is not "obligated" to port said app whatever replaces the abandoned OS (especially if the ROI on such an endeavor is perceived to be low).

Doesn't WebOS already provide easy access to sqlite? (I don't know, I'm not a developer, but I do run sqlite queries on some things in webos to move the data to my home servers). With that said, is something like HanDBase even needed? Seems quite easy to write a data driven app pretty quickly with the tools we have on WebOS. The problem of storing complex data and queries goes away with WebOS vs. PalmOS.

never heard of motion apps and i don't have any interest in palmos as i've never used it so i'd just say, "move on or be left behind."

I think Mr Haupert is on exactly the right track here. If HP & Palm are not showing loyalty and support for long time developers such as DDH (and others) what are they supposed to do? While Classic had its failings, what is most disturbing about how HP terminated it is the clear disregard for the developer. That behavior is meant to inspire a firm like DDH to make the investment? As much as I wish Mr. Hauperts points could be countered, I'm afraid that at the moment it is difficult to argue.

Dumping Classic was only disregard for one developer. Do you know any developers out there who still supported their apps specifically for Classic that are now left out in the cold? Most apps that ran on Classic were abandoned when their developers left for greener pastures.

Dataviz bought out the other database program (renaming it Smartlists to Go from ThinkDB, which is a true relational database and easily connected to Access) but they never supported it either. Let alone port it to WebOS, which will never happen now.

It all comes back to where are the apps? Palm's popularity grew by having lots of functional, productivity apps. Even the basic PIM functions of WebOS don't match some of that functionality of the original Palm. How many former Palm users people miss Datebook? That is what got lost in the transition from Palm OS, the applications we use daily that still aren't here (QuickOffice finally?) and don't allow some of us to switch until there is some true alternative. Even it means some pain transferring data from years worth of work into a new format. Preferably an improvement to match the new OS, but at least SOMETHING! There do seem to finally be some apps showing up, but its been slow.

I've never used HanDBase before, but as a novice WebOS developer I have to ask: what are the issues to creating an interpreter in WebOS for the applications written in HanDBase so that the applications can run on WebOS (albeit on a different middleware platform)? I'm assuming that HanDBase apps can be packaged in units of code (think source code in most languages). The "forms" can be converted to WebOS's native one with proper creation of javascript elements. An interpreter could convert all database requests to SQL so that any of the existing open source DBMS available for Linux (e.g. PostgreSQL, MySQL, etc.) can be used as the backend.

It's a lot of work, but no more work than creating an emulator or an interpreter (textbook case for most software dvs.)

Well he mentioned that just the UI work took about 9 months when they did the Android version. So if that's "all" they needed to do (not likely), the question would become: Do I believe the ROI from a webOS version of my app is worth 9 months worth of coding?

In other words:
Is he doing the coding himself? If so, what must he put off for 9 months in order to do this? If not, how much will it cost to pay his developer(s) for this amount of work? Once the initial coding is done, how much time should be spent with bugs, defects, new features, etc.? Is all of this (and all the stuff I'm not asking here) worth what he expects to get back from webOS?

There really is a lot to consider when a dev choses a platform (especially if they have just a tiny bit of integrity).

Hopefully hybrid apps on webOS 2.0 will make this trivial. Making a UI from HTML/CSS is a much simpler process than doing so on Android. I assume then they could port the business logic over without much effort, and easily whip something up with HTML/CSS.

I figured there'd be two ways that could happen: a commercial developer could pick up the task of creating an HanDBase application interpreter for WebOS or it gets created as an opensource project where 1 or 2 main developers would be putting in copious amounts of free time to developing it and others could join. When I asked about "issues", though, I was thinking more along the lines of legal issues. First of all, is it okay legally to take apps written for HanDBase and allow them to run on a different platform?

If so, I'd like to get in touch with a HanDBase app developer and we could talk about what that would entail. What artifacts come out of HanDBase app development that have to be interpreted in WebOS?

I'd be happy to talk to you about this! Use our support page's contact form and that will wind up in my hands shortly enough.

I desperately miss the days of carryin just one phone- my 680-IT JUST WORKED (and if it didn't there was an app for that way before the iphone apps), which now serves as backup for my pre.

I love the functiionality of webOS and all it's potential but I HATE the "ipohne" style touch screen, a major reason why I said I would never be an Iphone user.

I'm all for moving forward with technoloy but while waiting for the Pre to get up to speed I don't know why Palm drop Palm OS. I did not like the Classic app and was hoping with HP's cash the near future would allow Palm OS to run within webOS. There are enough loyal Treo users to make it finacially worth it for HP/Palm to support both devices.

I would have been interested in new "Palm OS Garnet" handheld, the PDA32, if it had a keyboard.

>> There are enough loyal Treo users to make it finacially worth it for HP/Palm to support both devices.

I'm not so sure of that. At the time, Palm couldn't even support one OS without having to be purchased. Things may have been worse had they tried to support both OSes. I don't think they were really making much on their PalmOS-based products anymore as most new buyers wanted "new" and current customers already had had ad PalmOS/WindowsMobile-based product.

There is a reason they came up with webOS in the first place.

Myself, my wife, my son, my daughter and a couple of friends are still using the Treo 680 because it is primarily a PDA.

I wonder how many others there are that the PDA features are the most important to them and are staying with their Treos until they can easily move all their data across and continue working efficiently without jumping through hoops via the cloud.

>>There are enough loyal Treo users to make it finacially worth it for HP/Palm to support both devices

IMO I respectfully disagree, there is still a market for it, palm never ever did get marketing right and always treated the operating system like a hot potato. There are many in the medical profession who still depend on their Treo as well as a generation of users who don't like change and stick to with what works for them. Not to mention the Treo was easier on the eyes with less work readjusting the screen.

btw everytime I see the blackbeery roller coaster commercial...I'm singing it for hours...that should have been the pre2 commercial!

can I get a definitive statement on the state of hybrid PDK/SDK apps on WebOS. Will WebOS2.0 essentially open the gates? Or are there more hurdles to overcome?

The WebOS 2.0 SDK has support for PDK plugins from CSS/HTML so I sure would hope that means the hybrid apps will finally be allowed then.

It seems the developers are having to do a lot more work to barely reach a technology standard that otherwise is surpassed by other phone. People are willing to pay but several of the phones applications are charing for small additions that should other wise be integrated natively into the phone. I have been writing pages on ways and reasons to integrate features in to the Palm. I was actually recently banned from the Palm forum which is being resolved by a moderator who randomly decided his ability to push a button was stronger than my pages of research. This is the simple mentality of many palm developers. Don't question why, but just simply do with what is there, which is fine if your a monkey or in a case of survivor. This is the kind of mindset that could make this technology obsolete. Not listening to the intelligent user base is the equivalent of saying the developers know better than what the user wants, unless your releases over the top technology(which you aren't this rarely holds true).

The real questions Palm users would like to know are, Where is the development for well known applications? Such as Shazam. We all know with certain quality applications come great developer tools, When these applications do not exist we are certain the Palm WebOS is far behind without any excuses.

The real issue at Palm right now and I believe this held true for some time is, there is no administrative support. I went through HP as well as Palm to resolve this forum issue and ended up amongst an exec's cell phone and a fully Arab firm who knew little about the forums ( some literal didn't know the palm forums existed ) To me the 3rd party at Palm may have gone too far. I believe you have people in the company thinking their owners and CEO, as well as project managers and theres literally no one guiding the way and providing accurate comparisons about where Palm exists in the market amongst others.

The post I was banned for said many things but ultimately came down to an analogy for Palm's complacency. The gestures and design of the programming are seen as advance but to the functional user the functions of gestures become aesthetics. Like a dimmer switch for a light, gesture act in the same way. While a dimmer has slightly more function and ability in most typical circumstances it serves regular function for almost all practical user. While it can be seen as advanced it ultimately is nothing more than a convince tool that some would say serves no more purpose that a button. These designs will sell phones for sometime, but ultimately the phone's software must compete at all levels and not based off a simple unique design.

My analogy in my post was worded better but I would hope you understand. Its as if Palm and the developers are caught up in certain niches and forgot to really compete with the market. You don't want to just win the Class C division 2 prototype racing award ultimately you want to win the Class A division 1 award. These niche awards are achievement obstacles and like most Presidents most people don't want to be known as the reoccurring peace price winner of Ethiopia each year.

I want to mention I was banned for the post, My post were locked because the questions were too difficult for the moderators to understand. I asked a simple question about HP E-print commercial , depicting a user sending a photo from their palm pre, and my answer was there must be some sort of cord that connects to the printer. Obviously this is incorrect, as E-print is fully wireless and connecting wires from your phone to the printer was never seen as a unique accessibility feature. I mean this is the equivalent to the mod, who might be a dev, that no one wants involved with product development or their forums. (PDA GUY s/n says it all)

Many users with simple to moderately complex databases on legacy treo database apps have already migrated their data to the webOS database application, My Databank. If your data structure is not overly complex, download the fully functional trial app for free and see if can support your database needs in a webOS environment.

My Databank supports these features:
Up to 5 text, integer, date, and boolean data types.
Multiple categories and items.
Password protection.
Primary and Secondary field sorting.
Text filtering.
Data Export and Import.
Acquires current GPS latitude and longitude coordinates.
Customizable icons.
Frequency logging and Priority sorting.
Field ordering.
Forward values directly into other external applications: Messaging, Web Browser, Google Maps, Email, Phone, Clipboard
Choose phone numbers and eMails from your Contacts app.
Choose filename locations for your Photos/Music/Video/Documents locally on your webOS smartphone.
Generate and eMail your Items as a datasheet Report.
Delete or Export all Items for any specific Category.
Send an SMS message to all recipients for any specific Category.
Supports basic formula calculations against field values.
Supports basic conditional comparison logic against field values.
Supports query filtering logic against Item lists.
Quick column switching view on Item lists.


There's no other webOS database app similar to it. Try it out.