How most SDKs do I need? Which SDK is most appropriate for me? For a visitor to the Symbian growth universe those have been between the initial questions asked. There have been most S60 SDKs on offer, a little with underline packs and plugins, a little with compiler specific binaries and on tip of which most plug-ins. Quite a lot to hoop and figure out and nobody likes carrying all probable SDKs installed. So what will occur right away which Qt is combined to the picture? I can pattern my app regulating Qt for Windows (or Linux, or Mac) and, according to the “code once, accumulate anywhere” guarantee I should be equates to right away to accumulate this focus for Symbian and Maemo devices, with minimal changes. But which equates to which right away I need to implement at slightest a single Symbian SDK for building, or a Maemo one, and I should have at slightest a single smartphone for testing. Or do I? Yes, substantially a single will have an SDK commissioned and operate the emulator for contrast a little unequivocally difficult solutions, with Symbian components partial of the design. And yes, zero can unequivocally reinstate hand-on-testing. But for elementary operate cases and for removing proposed trials a single probable resolution could be structure and contrast in the cloud. What we need is an IDE plugin, web hosted SDK and set up collection and Forum Nokia’s Remote Device Access solution, all churned together in a rsther than elementary build, muster and exam solution. Here’s a live demo (boring tools speeded-up a bit) of such a solution: