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 am trying to find the main difference between MVVMlight and MVVMCrossthose frameworks. I am planning to develop for Android and Windows Phone. I will use the Xamarin framework. (and Xamarin.Forms)
The project should be a vehicle tracking application that talks to Azure-run server. The app itself will be (as usual in the beginning of a project) very simple (start, stop, keep recorded locations).
Why should I use one over the other?
Other details: VS2012
Completely up to you. People have gotten MvvmCross working with Forms here but still early days. Do you need any of the nice plugins of MvvmCross? Will there be screens that you'll need to manage per platform because they are too complicated for Forms? I don't think there is a right or wrong answer here....
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 5 years ago.
Improve this question
While most articles and posts I have been through discuss about Native vs Xamarin or Native vs Hybrid(Phonegap) I searched around and very few with Xamarin and Phonegap.
Me and a group of my friends are developing a photo-sharing app of sorts and we want it to be cross platform. But we're stuck with the dilemma of going with Phonegap or Xamarin.
While price-wise both are free(except for iOS development) and we're familiar with the languages and technologies used by both, we're at a stalemate arguing on points such as;
Developer support
API availability
Ability to debug and update easily.
Whichever platform which delivers the best of all of this is what we hope to go with.
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 7 years ago.
Improve this question
Are there any Java/Objective-C skills that are needed in order to write fully featured applications using Xamarin or is it pure C# that compiles into Native without any adjustments needed (UI for example)?
The answer to such question depends on your application needs.
If it's just a standard application without a fancy UI, you can use Xamarin.Forms in which all the UI is written in Xaml.
If you need a more complex UI, you may need to use Renders, which involves a native code (ios/Android) in your app, but still you can write those renders in c#, so your'e not out of C# context, but you will have to know how Android/iOS OS system works, rather than the programming language syntax.
If you have a highly complex UI with interactions, then Forms is not an option, and you can use the traditional Xamarin system, but you'll need to know well how does each platform operates.
Hope it helps you to decide.
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
My understanding of the tool is that it helps people learn about programming by making it easy to create android apps. Is it just for educational purposes or can you actually build a commercial quality app with it?
I know the backend of a professional app would have to be written using something else but is it good enough to create an entire front end android app?
If people are making real apps with it, what are some examples?
Yes, you can
To find some examples do the following:
1. search the App Inventor forums here and here
2. search Google Play
3. take a look at the App Inventor Classic App Gallery thread
4. ask in the App Inventor forum
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I want to make a quite simple application in multiple devices using xamarin (iOS and Android).
So I read/think that the best way to doing this is to put one folder (shared between all projects) that contains all the:
DataLayer (for physical storage)
DataAccessLayer (support data operations)
ServiceAccesslayout (communicate with an external API)
BusinessLayer (Application Facade)
And for the view, the applications will use their custom language
So first question, does it sound great?
Second: How add that kind of folder, that should be updated in every project in Visual Studio 2012? Actually I have one solution with two projects and the two projects (iOS and Android) should have that same folter (tat contains all the "core" layers)
By the way if you have already read a tutorial that talk over that question, please give it to me.
I would have a look at MVVMCross, it is a great way of sharing the maximum amount of code across platforms.
https://github.com/slodge/MvvmCross
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
I want build an application by using the framework.
the application contains two parts: the Back-End and the Front-End.
Everybody who have experiences can suggest me which ways should I do?:
Develop the Front-End first Or Develop the Back-End first
Or give more tips on the start up project?
thanks
I usually start with the backend to get the major functionality implemented, but even so, it's pretty much inevitable that the frontend and backend will have to be developed at the same time at some point in the project.
People can say what they want about separating presentation and functionality, and that's a good principle, but the reality is that the presentation influences the functionality and vice versa.
You might get the backend mostly written, and then you make the frontend, but you will probably decide to change some things and end up working on both together.