On https://developer.fleetboard.com/#/getstarted, we can read
To implement your ideas we recommend to use Android Studio.
But we work with Visual Studio, is it possible to use Xamarin ?
yes you can.
However we provide an SDK which makes it easier for you to use our library (access to vehicle data).
If you use Xamarin and want to use the provided functionality you have to integrate the jar on your own.
Related
I'm a Windows developer and have written all sorts of windows client applications using C++ and C#. I wanted to write an Android app and put it on the Google Store, but I'm only equipped with Visual Studio.
I wanted to ask if it is realistic to think that I can create an app, from scratch, including engine and UI using Xamarin only. I saw there are a few Xamarin samples out there, but I didn't want to start only to find out that it's not enough for some reason.
Currently I'm struggling a bit in getting my environment right, but thought I'd throw this question here to you guys ... Maybe it's not even worth starting?
Thanks.
Yes, Xamarin can be used to develop Android apps from scratch. Xamarin has two main libraries that help with this.
Xamarin.Android will give you access to all the Android APIs directly from c#. Note that you still need to know the basic Android concepts like what is an Activity and an Intent.
The other library is Xamarin.Forms. It is a cross-platform library that will give you a basic set of UI controls and widgets that you declare usong an xml syntax, and program with C#. This library has a few limitations, but you can also use the features of Xamarin.Android alongside it to get at the missing features.
Some advice: if possible, develop and debug directly on an Android tablet. Android emulators are not that good and hard to configure. Hope this helps.
There are 2 types of Xamarin you can use.
Xamarin Forms : Which is the unified version that use XAML for the UI. It is very recommended to use this if you are building a simple application.
Xamarin Native : The "native" version of platform that are written in C#, if you want to create Android-only apps, I really recommend this, since it's very similar with the native Android code, but it's wrapped using C# (You can still using nuget package).
Some developers have told me about it's possible to create iOS projects in Microsoft Visual Studio thanks to an Xcode plugin.
However, I can't find the proper way to install it, I already have tried to download it from here and I installed it but it doesn't appear when I try to create a new project.
So, if anyone can tell me the steps I have to follow in order to install the plugin properly, it would great.
Thank you in advance!
The xcode build tool you're trying to use has still a lot of issues and only few workflows are being implemented and supported. I suggest that if you wanted to create cross platform application and would like to use Visual studio code IDE then i suggest on using Xamarin its code base is c#. If you're using a mac computer then why not use xcode and if you're a windows user and wanted to create iOS apps then xamarin would be the best choice for you or unless you want to try frameworks like ionic etc. I hope i was able to help.Also , I can't comment because of still low repu , so I decided to post this as answer.
I was trying to learn basics of xamarin. I came across Adding a Universal Windows Platform (UWP) App and I was trying to figure out advantages of using it over normal UWA with PCL or Shared projects. Is it different from UWP, or does it offers more support from portability?
Xamarin Forms helps dev code once and deploy on cross-platforms.
For front end, there are bit different when you code UWP and Xamarin Forms. stackpanel and stacklayout these kind of UI element. MS is working on XAML standard 1.0 so in future we only have one XAML need to remember.
If you are working on windows 10 app, highly recommended using UWP. There are more docs you can read.
Lot of people using Xamarin Forms to create Android iOS cross-platform apps, and devs lost interesting in support xamarin forms plugins for UWP.
does it offers more support from portability
Yes, or rather I should say that portability is the only practical reason you want to use Xamarin (aside from you being familiar with the platform and not wanting to learn something new, but this seems not to be the case).
Is it different from UWP
As far as I know, Xamarin's UWP is just a UWP project included inside a Xamarin project, so it's basically the same thing.
The answer is: NO
No performance issues
No developing issues
Everything was converted down to the same assembly and run as you expected
However, if you just do mainly in UWP. I suggest not doing it on Xamarin, because the support of new toys come a little bit slower on Xamarin. Right now the communities are waiting for XamlUI Alpha
I have developed applications for Android and iOS using DevExtreme framework.
Can we develop windows desktop apps using Devextreme?
If yes please provide guidelines or steps to get started.
Please help on this.
Are you looking for something like this?
https://www.devexpress.com/Support/Center/Question/Details/T135296
Yes, you can do it. I suppose you use Visual Studio to develop windows apps. If so, the DevExtreme Multi-Channel project template supports WinJS app.
Just create a new Multi-Channel app:
Then, you will be able to select WinJS project template:
The DevExtreme documentation contains some information about WinJS development.
Also, I suppose, you can use Electron. Unfortunately, I have no experience with this tool. And there is one restriction here: Electron supports Windows 7 and later.
I have a project which greatly depends on ServiceStack, unfortunately the V4 releases, which includes PCL release for most platforms(especially after forking out for a Xamarin Licence), is just way out of my price range as an ISV. I have cloned the MvvmCross code but before I start messing around I would like to know what pitfalls I could run into when attempting to create a Non PCL based version compatible with the platforms I target (Currently Xamarin.Android, WPF and WinRT). The idea would be to able to reuse the code for the WPF project to build Android and WinRT clients.
Does anyone have any pointers?
I don't think there is any problem or pitfall with what you are describing - and I don't think you'll need to fork the MvvmCross source.
You should be able to build your apps as native code, and should then be able to reference the MvvmCross PCL libraries directly from the native libraries you are building - you don't need to rebuild MvvmCross to do this. Plenty of people already use MvvmCross using "file linking" rather than PCLs - it's not the default setup encouraged by the Nuget packages, but it still works fine.