A company called redfivelabs has recently announced an initiative to bring .NET Compact Framework support to Series 60v3 devices. For all those new to the concept, .NET CF is a virtual machine(sort of like Java) that is used on PocketPC devices. While many(I dare to say most) PocketPC applications are not written in the compact framework, the .NET community has managed to create quite a few impressive products.
Users on various forums have gone all bonkers expecting “recompile” ports of various cool applications - however, I am sorry to say that this won’t happen for the following reasons:
Many of the really cool PPC applications AREN’T WRITTEN in .NET CF
Let’s consider the following facts:
- PocketPC’s have had a native programming interface ages before the whole .NET idea came along…and hundreds of applications were written for this API.
- Some PocketPC functions cannot be accessed from the .NET CF.
- Native code is faster
- Native code cannot be decompiled
The four reasons above allow only one clear conclusion…most PocketPC apps do not run in the compact framework and will thus not benefit from redfivelabs’s work.
S60 devices lack a touchscreen
PocketPC devices all have one bit of hardware in common: the touchscreen. While most of you probably don’t miss a touchscreen in their S60 devices, trust me if I tell you that having a touchscreen available has a huge impact on UI design. Some of my applications won awards for their simple UI - putting this UI onto a touchscreen is an extremely difficult task at least. Virtual mouse pointers exist and are used in web browsers - but, please, forget using them for your app’s main UI…
A well-designed mobile application has had hours of work invested into its UI - developers will definitely need a lot of time to rethink their interfaces…
Single-supply problematic
redfivelabs is the only company that offers such a framework. What happens if they go belly-up? The recent death of AppForge has made developers painfully aware of this…reducing the chances that time will be invested into the product…
The company will be at the roadshow - so we will definitely know more on Tuesday!
Related posts:
Fine…..! but not all the facts….
as you told…
_______________________________________
Many of the really cool PPC applications AREN’T WRITTEN in .NET CF
Let’s consider the following facts:
* PocketPC’s have had a native programming interface ages before the whole .NET idea came along…and hundreds of applications were written for this API.
* Some PocketPC functions cannot be accessed from the .NET CF.
* Native code is faster
* Native code cannot be decompiled
______________________________________________
now my reply…(cool reply)..:-)
@ All PocketPC functions can be accessed from the .NET CF(through P/invoke)100%.
@ Native code is faster in some scenarios else ~same speed.
@ if you obfuscate the .net CF code properly,then .net CF code cannot be decompiled.
@ if the product is targeting multiple types of processors,then .net CF is good options only one Build file(for Native code, there will be one Build files for each type of processor (manes so many build files…)
>>> Note: if a person want to develop a OS related(like device drivers etc..)project then Native is good ,else in other any type of application development using .net CF is fast and powerful way……
so there is a choice for ports of various cool applications ….
THats aLLLLLLLLLLLLLLLLLLL.
if any comments please let me know ….
schoudhary@xora.com
Hi Sandeep,
full ack here…but:
x) in the moment an app uses PInvoke, there goes compatibility and easy portability
Also, what compelling reason does a software house that currently has well-selling native PPC apps have to port to .net CF?
Best regards and thanks for talking back
Tam Hanna
Hi Tam,
As you asked ,about reasons for portiong native PPC apps to .net CF?
@ if an app uses PInvoke, compatibility can be managed by one build only at runtime on target device by checking target environment and behave according that only…
@ More Application maintainability ,and robustness (like features enhancement etc),these provides fast app development.
@ The Golden point of CF is GC(great one).90% new Native app’s (in dev/testing period) are suffering from problem of memory leakage.
@ only one build for all type of devices.
@@@ and the Key Point , if an app is made in .CF it can run on Symbion 60 also..
Best regards,
Sandeep Choudhary
Hi Sandeep,
in fact - many of the topics addressed here were explained in the redfive keynote…which is available here:
http://tamss60.tamoggemon.com/2007/10/19/net-compact-framework-for-symbian-further-information/
As for the made in CF running on Symbian…this definitely wont work out - end users are not able to purchase the VM. Developers of CF apps will need to actively support Symbian users - any pay a decently high fee for this privilege… :(.
Best regards
Tam Hanna
Hi Tam,
Thanks for the posting about our framework. I enjoyed your comments and look forward to exploring all the possibilities Net60 enables. I thought I’d drop you a line to say that the Net60 beta is available for download off http://www.redfivelabs.com if you would like to kick the tyres.
BR,
Adriano
Hi Adriano,
thank you so much for your post!
If you add Tamog@gmx.at to your press release distribution list, you make it easier for me to stay up to date!
Best regards
Tam Hanna