BugHerd is a bug tracking solution designed for users of all technical backgrounds. By making it easy for anyone to report a bug, BugHerd aims to make resolution by technical teams easier and faster.
$39
per month
Xamarin
Score 6.0 out of 10
N/A
N/A
N/A
Pricing
BugHerd
Xamarin
Editions & Modules
Standard
$39.00
per month
Premium
$129
per month
Deluxe
$229
per month
Xamarin
Free
Offerings
Pricing Offerings
BugHerd
Xamarin
Free Trial
Yes
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
BugHerd gives a discount equivalent to the cost of two months for annual subscriptions.
BugHerd offers a 14-day free-trial of all plans.
Custom pricing is available for large enterprises.
Bugherd is well suited to our needs because it's an intuitive tool that doesn't require a ton of training, and we are working with a development agency to improve our backend and communicate issues to developers. From what I've seen, it does require you to use Chrome, which might not be perfect for other companies but it great for us. The tool has great functionality for tracking and allows you to move bugs into stages like "doing", "done" or "backlog". The screenshot tool has been super easy to use, and when we do have a bug that requires multiple screenshots, it's easy to open up a newly submitted ticket to attach a custom screenshot. It isn't easy to track down a specific bug you've logged if there are hundreds, so be prepared to dig quite a bit if you're using it for extensive testing and find yourself trying to go back
Xamarin is well suited for several reasons. The first, it allows companies to share code across platforms. If the app has a lot of business logic and a fairly simple UI, Xamarin is great for this use case. Xamarin also works well if the developers who will work on the app are already fluent in .NET. Xamarin is less appropriate if the company has a lot of developers. If there are plenty of resources to develop apps natively then the headache of dealing with Xamarin's issues are not worth the effort. If the UI is very complex and has difficult animations it's difficult to debug visual/performance issues in Xamarin.
Having also done a lot of native mobile development, some of the IDE's features need to emulator their native counterparts. For example, trying to extract a string resource on Android in Xamarin Studio is painful. There are many useful tools in Android Studio that Xamarin should implement.
Xamarin will always be behind on native platform features. They must catch up when Apple and Google release new platform versions.
The biggest pain point is the random issues Xamarin continues to have. Having a large code base on top of a native platform makes it very difficult to debug issues. Every developer must decide if its an issue with Xamarin or the native platform. Bugs don't get fixed very quickly. Hopefully that will change with the Microsoft acquisition.
Xamarin has been great for developing different projects efficiently and effectively. It's nice to reuse the core business logic across different platforms so that there are less to maintain and little replications are needed. The biggest benefit is that C# programmers do not have to learn a different language to do mobile development.
BugHerd is an easy-to-use, highly intuitive tool that fits seamlessly into our web development process. It is easy for all users to use, web developers, project managers, testers and clients. Clients are able to easily pin bugs and provide explanatory feedback that allows our team to fix what is broken and incorporate client feedback.
If you are required to develop applications that are cross-platformed, Xamarin is a great tool to use. It will help save time and efforts from your development team to be able to build applications seamlessly for android, IOS, windows, and web on a single platform instead of requiring multiple tools to get the job done
Truthfully, we have had very little need for BugHerd support, as the tool is intuitive and does not have many bugs of its own. They have a pretty solid help/FAQ section and their support people have been reasonably responsive the few times we have needed to contact customer support. We have had our issues resolved and questions answered.
I never had to contact support for any help. Most of the problems we ran into, we were able to identify and use peer support through blogs and other internet sources to resolve the problems. There are plenty of sources online which provide tutorials, discuss problems, etc. Example: StackOverflow
Just with any programming tasks, have a plan first. Design out the system, spend time to build it correctly the first time and have plenty of testing and user acceptance opportunities. Xamarin was easy to implement for a C# programmer. However, you need to do tutorials to realize the platform's capabilities.
BugHerd is more focused on web-based tools, which we needed, as opposed to app-based tools like Instabug. Jira has a much higher level of complexity and barrier to entry and didn't suit our use case.
Xamarin runs natively on MacOS, and the debugger and other integration and auto-complete tools are far better than Eclipse for C# .NET. It also carries much of the plugin/add-on capabilities that are so desirable on Atom. Eclipse is a better for generalized software development, provided a developer is comfortable switching between the IDE the command line for certain parts of their workflow, like building, package management, or debugging. But for C# .NET development on MacOS specifically, Xamarin is the best product I've used for the job.
Code Sharing - We were able to launch an Android implementation of our app within weeks after finishing iOS. The amount of time taken to develop a new platform is very small.
Monetization - not the best, but definitely getting better. We've had issues with finding suitable ad networks that work with Xamarin.
