It really considers your market and whom you think will be buying the application.
The cheaper your app, the better of a chance
your end user has and older machine. Personally, we started developing our current
app just when the first Palm IIIs were shipping.
We noticed that anyone of "power user" status was either getting a III or upgrading
their PalmPilot� Pro with the 2 MB/beam upgrade
card (mid 1998). We found supporting 2.0 was compromising a lot of our effort to a
decreasing market share and a lot of our code
takes advantage of UI features only found in 3.0 or beyond. Thus we decided to only
support 3.0 and if it is run on an older OS, a
message pops up instead of the app saying that we only support 3.0 or higher.
So far, we haven't heard a single complaint from any of our customers. Those who
wanted our software and hardware immediately
upgraded their system without any moaning. I feel 3.0 will be around for a few more
years just to the sheer number of them sold due
to the form factor. Also the incredible sales performance of the Palm V and it being
OS 3.1 at least created a lot of demand for
our product. Palm V customers stats wise tend to buy more third party software than
Palm III owners.
Steve
Joseph Koral wrote:
> Any opinion on making Palm OS 1.0 compatible applications? Is it worth the
> extra effort to conditionally remove some features/functionality, but allow
> your app to run and function on Palm OS 1.0)?
>
> My application currently requires OS 2.0, but of course a co-worker has a
> Pilot with 1.0.6... and I'm wondering how many actual users may still have
> old Pilots. Any thoughts?
>
> Joseph Koral
> [EMAIL PROTECTED]
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe, please see
>http://www.palmos.com/dev/tech/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
