When i want move to RoR, they provide asp mvc 3 include EF migration.
When i want move to js, they provide async keyword.
Now when i want move to f#, they provide it all in c# language
36 karma · joined March 10, 2015
When i want move to RoR, they provide asp mvc 3 include EF migration.
When i want move to js, they provide async keyword.
Now when i want move to f#, they provide it all in c# language
1. This is very bad for windows phone developer. It will make the ecosystem more suffer
2. There is a little hope. Windows phone is more efficient than android. If wp10 full compartibility with android hardware spec, wp10 can fight on below 100 dollar price
1. Put free price / comunity product on price plan
2. Provide simple guide and script to convert existing bitbucket hg to git (because people are lazy)
thx for responding my comment. after read your explanation, i agree with your argument about xamarin form. it just need more feature and more sample. Xamarin sample layout is not esthetic. You should look at telerik example. And last one, when feature listview drag and drop swap row available on android ?
thx
If you dont have mac, and belive in xamarin,
My sugestion is try build on android first,
If have good respond from customer, then buy mac and porting to iOS
Porting xamarin android to iOS is very easy if you have mvvm knowledge
I'm following your blog.
In last month, you try to prove UI xamarin form capable do all layout
Here is the idea, if you dont mind, would you convert ListViewAnimation android to xamarin component
(Warning: this is not a light library)
At the moment, there is no listview xamarin component support drag and drop swap row.
Need that to move and reorder and row sequence
I'm sure every project need powerfull listview
Love your work Thx
From my experience, xamarin take wrong UI improvement strategy
Dont get me wrong, this is a good product, i love it, but just going to wrong direction
This is the big 2 mistakes:
1. You change the API class and method name to .net version
For first time user, this is good approach, but i must rename every sample snippet code from stackoverflow
You should save the resource for renaming API to something else more valueble ( hint : fixbug )
Are you rename the API because of patent and legal issue?
2. Xamarin form
This is the worst strategy.
Maybe this is good for B2B
And maybe B2B is good money
But for me, indie programmer, B2C product, i dont need xamarin form
I need best approach to use UI library
Stop xamarin form, there is other way to get 90 percent shared library
Support more on MVVM cross
Duplicate total of the xamarin component store
Improvement object sharpie to support UIKit.h
Object sharpie not working if using UI library
Android binding still design for eclipse project, not android studio
I'm wasting 1 week to bind ListViewAnimation android, and still not working
My point is, it really hard to bind UI library on xamarin
Conclusion,
Please please turn around and go back to your real core value.
We like native, improve native, do not recreate the UI component
You know what happend when you try recreate UI?
Go check java se and Qt