Products · Product
Xamarin
Raised as a usability problem by 35 people on Hacker News over 8 years (2013–2020), in 23 threads.
No issue was raised by at least 3 people in 3 threads this year.
No issue was raised by at least 3 people in 3 threads in the last 5 years.
- 1Developer tooling incredibly slow to useUnreviewed
Every issue, all time, most people first
Developer tooling incredibly slow to useUnreviewed
20132026- Deploying to devices is painfully slow and the tooling is worse than native2020-01-27
- Developer tooling is incredibly slow to use2018-06-03
- Tooling is rudimentary and development is painfully slow2016-10-13
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 35 complaints
- Unusable on HiDPI displays because it consumes too much CPU2020-11-10
- Getting fine details right means fighting the tooling and writing custom code2020-09-11
- Deploying to devices is painfully slow and the tooling is worse than native2020-01-27
- Visual Studio integration terrible at tracking file changes, needs frequent cleans and restarts2019-12-11
- Tooling for Linux was horrible, making cross-platform development painful for their karaoke product2019-11-08
- IDE becomes slow and sometimes fails to connect to Android emulator for debugging2019-08-15
- Connecting Visual Studio on Windows to a Mac build server is broken and hard to get working2019-08-15
- Deploys cached packages so code changes silently don't appear after clean and rebuild2018-09-21
- Errors are vague, undebuggable, and occur at random times2018-09-21
- UI development is verbose, underpowered, and offers few controls2018-09-21
- Android emulator default settings don't work out of the box2018-06-08
- Developer tooling is incredibly slow to use2018-06-03
- Couldn't get a project started; cryptic errors during install and project creation2018-05-23
- Pages take several seconds to render on Android, making the app sluggish to interact with2016-11-16
- Vague deployment errors and cryptic build messages make it hard to know what went wrong2016-11-14
- Buttons misalign text and need custom workarounds; the framework is buggy and slow2016-11-14
- Making a UI is messy, complicated, and produces vague underwater bugs2016-11-14
- Layered stack produces cryptic errors at the top that are hard to diagnose2016-11-14
- Using third-party libraries requires a lengthy, multi-step search for bindings2016-11-14
- Deployments sometimes take 5 minutes, forcing agent restarts to fix them2016-11-14
- No layout preview, so every layout change needs a full recompile and deploy2016-11-14
- Tooling is rudimentary and development is painfully slow2016-10-13
- Hint and help popups get hidden behind the on-screen keyboard on iPhone2016-07-07
- Docs and samples are missing for iOS or Android, so building beyond basics is hard2016-03-31
- Adding or moving files crashes the IDE; UI editors are slow and lack features2016-01-13
- Binding native Android UI libraries to Xamarin is very hard, taking a week without success2015-04-05
- Android layouting is hard to get right, with many conflicting guidelines on what to do2015-04-04
- Slow layout measuring and no ListView recycling make apps perform poorly2015-04-04
- XAML implementation has no intellisense and is awkward to write2015-04-04
- Indentation gets confused around #if blocks, making the IDE hard to use2014-06-29
- Starting an F# project requires searching for add-ons and manual configuration2014-04-06
- Changes made in Xamarin Studio and Xcode designer often fail to sync and must be repeated2014-03-18
- Must write separate UI code for each platform, switching between toolchains2013-11-13
- Third party SDK bindings break with undecipherable errors and useless error messages, making problems hard to diagnose2013-07-18
- Debug fails to run because Android device images are missing or not found2013-04-16