ZeroHour Posted May 12, 2010 Posted May 12, 2010 Hi Just to let you all know that things havent stalled. I have been looking into the big 3 SDK's (apple,droid,wp7) and evaluating various options for each and trying to come up with some sort of the common interface for this all. I am also getting sorted with the various app stores that edugeek needs to buy to allow us to publish it to you all. I am away from Thurs till Tuesday so there wont be any updates over the weekend but I am hoping to get rough app gui's for you all to gander at soon. So far wp7 is by far the best to dev on, VS simply rocks tbh along with c# but droid is not bad and iphone is hell. One thing to watch/consider is monodroid which novell is expected to release this summer/august which could be very nice for the droid app as it appears most of us love c# (who coudnt) I am not sure about the situation with monotouch (the iphone c# engine) after all the anty-adobe junk apple pulled but that team has requested info from apple to hopefully clarify if those apps will be allowed (good luck with that) I will update you all again next week when I get back and we can get underway with a private forum for dev work too. Cheers all
featured_spectre Posted May 24, 2010 Posted May 24, 2010 I think the people behind VBulliten are actually designing web interfaces for mobiles as we speak, so I personally think its best to stall until its done. An APP is going to require a tremendous amount of coding for each system, so why not let them do the work for us!
SYNACK Posted May 25, 2010 Author Posted May 25, 2010 @nephilim - Unless they are doing a web service component then I don't think that they cover the same ground. A local app will allow for a full experience on a mobile device and be able to offer features that would simply not be feasible on a majority of mobile devices via html/java. It also has the ability to allow for much less data transfer when checking stuff mobily which is important for speed and makes it more affordable and practical for those of us stuck in stone age countries where mobile data can be $1/MB. Depending on the API made avalible this could also mean clientside caching further speeding up the experience and limiting the cost. All it would take is a last retrived attribute in the request for any changing list like the iSpy system currently uses and it would lower both the load on the server and the load on the device. You are right that it will take a chunk of coding on both sides server and client but for most devices it does seem as there would be a reasonable amount of code portability for stuff like the logic, the UI and low level communication side may need to be customized per OS but this is doable as the code should be tiered anyway. @plexer - as the central code should be tiered out in a way that makes it as portable as possible it should hopefully not be to difficult to port it to other platforms that support the right kinds of development languages. Symbion appears to be programmed in C++ and while there were toolkits and apps for C# support they appear to have stoped being supported. This may make the port more challenging but if there are some symbion os users out there with the skillset the code once written for one platform should be a good basis for a port.
SYNACK Posted September 9, 2010 Author Posted September 9, 2010 Looks like Apple have done a bit of a reversal of their heavy handed stranglehold on development environments for their phone/pad Apple relaxes iOS development tool restrictions, app review guidelines released This should bode well for code shareing between ports so long as they don't decide to pull any other stunts.
Recommended Posts