Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I want to develope a native app (for Android and IOS, later Windows Phones, too. It will be designed for tablet computers like IPad etc.). It is an Enterprise application connecting to the database.
What is very important to me, is:
User Experience: It has to have this native Look-In and must be really attractive.
Performance: It has to have a high performance.
So with regard to the points I mentioned, I am looking for a framework offering the best components and controls for native development. Of course, it would be desirable to use an cross platform framework but for native apps.
I tried out Xamarin and read a bit about Appcelerator Titanium.
So referring to the criteria I mentioned, what is the best framework to develop my app?
Personally I would go for Xamarin. It's based on the mono project which is now quite mature. Xamarin have recently partnered with companies such as Microsoft and SAP.
I've generally found the troubleshooting to coding ratio higher for titanium than Xamarin. In my opinion Xamarin is the stronger platform; albeit a commercial product.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I decided to make an application that like statechart simulation tool or flowchart (such as yEd, MS visio etc.). It will be a diagram scene application. But, I have'nt decided to platform that I will use yet. Which one is suitable for this jobs?
Qt,
MS WPF,
Python
Others
well, I have only WPF platform experience but I'll share my experience in those area.
I worked almost 2 years for developing in desktop application using WPF(I know it was 1~3 millions $ project). and some portion of my job is developing and maintaining diagram based canvas with telerik libraries.
but the first, I want to recommend you to choose your program going to be a .net-based/cross-platform/web-based.
If you choose that you are going to make windows application and those diagram chart, then WPF and telerik may be a one of good choices.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
From my understanding, if you want to develop a multi-platform app, it makes more sense to just use NativeScript or some other hybrid language. So would there be a point in using swift, objective-c, java, etc over something like NativeScript?
In the long run, I would love to choose swift/java over cross-platform framework. Even though with NativeScript, React Native or Xamarin, they all render the real UI Component from native API but I think there is still a gap between performances of swift/java and cross-platform.
Cross-platform is perfect for small or medium apps, or companies who have limited human resources as cost for developing and maintaining native apps is quite high. However, the cross-platform apps won't be as stable as native apps, so if you want to have a feature-rich apps, swift/java would be better. Moreover, I don't know much about React Native but you have full access to native API in NativeScript with JavaScript.
Technically, you can do everything swift/java can do in NativeScript. However, there are something in native API (e.g UI components, native function, etc.) that might take lots of efforts to access as it's quite tricky to translate swift/obj-C/java to javascript. Fortunately, there are many plugins or code snippets made by community that might be helpful.
That's my personal idea.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I have no prior knowledge on Mobile application development so these might sound a naive question. Basically my requirement is to develop an application that will work on multiple platforms like Android, Blackberry and iOS. Hence, I wanted to know how well is Worklight suited for the job. Basically I wanted to know:
Q1: What are the technical or functionality concerns of Worklight that one should know before going for it.
Q2: Is it better than PhoneGap?
Q3: What are the basic skill sets required for a person to work on Worklight other than Java.
Q4: Are there any Hardware requirements that might be specific to Worklight applications and might cause the developed mobile app to not function on the phone?
I would be grateful to anyone who could help me out.
Thanks in advance.
You must buy a license if you intend on going to Production; the free Developer Edition may not be used for that purpose. It's not for individuals or small businesses, but for medium to large businesses. Other than that, it depends on your end goal.
Worklight cannot be better than Cordova in the sense that Cordova is bundled within Worklight. So anything you can do in Cordova, you can do in Worklight and add on top of this all the features that Worklight provides you with (and for this, please, just take a look at the Worklight website and Information Center).
You need to know HTML, CSS and JavaScript at a decent to very good level. If you want more, you need to know languages such as Java, Objective-C, C#.
No.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Responsive web design (RWD) is good for admin side (control panel) of web design?
I have more entries and tables in my admin page. so RWD is good for admin development?
Also it is good for develop mobile application for admin forms?
If you know Responsive Web Design as 'Fluid and adaptive layouts with progressively enhancing features', then I think it's probably safe to say that yes, RWD is good for almost any web project. Be aware however, that building responsively is much more difficult and time consuming (read: expensive) and may not offer the necessary ROI that you need.
For example, consider that much backend software like cPanel and such are used by technically skilled people that understand how to resize their browser and work with less-than-polished software.
Also, when you think about cPanel, you must consider whether much of the utilities and functions it provides are efficient and useful in the mobile context - I doubt that sysadmins really want to do module installation or type large amounts of console code with an iPhone keyboard.
So when considering the merits of RWD for backend web software, be sure to weigh up your target audience, their skills and requirements, their equipment and what (and how) they will use the tools available to them to get things done.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
We know that Silverlight currently in 3.0.x version - very fast transition from Silverlight 2.0.x. For those using Windows and Mac, it will not be an issue since the runtime supports those platform. The problem is with Linux users. I know that Mono guys (through Moonlight project) are doing their best to keep it up to date with Silverlight, but unfortunately they are too much behind.
How do you offer Silverlight to clients considering that facts?
If your client base has "full support for Linux on the desktop" as a pre-req, you're really in an interesting niche -- one I'd love to learn more about, btw, but not one I've ever encountered. If you're REALLY in such a situation, I guess your only viable silverlight strategy is to limit your silverlight use to not much more than is currently available via moonlight, clearly document to your Linux-rabid clients what's missing on Moonlight for them to be able to use your latest release, and endeavor (via clients involvement, involvement of your tech people, bounties for developers that add each missing features, etc) to get Moonlight up to the level you absolutely need it to be!-)