Xamarin and Visual Studio
Discover Action Components
That’s where Appracatappra comes in. With our growing suite of high quality, cross platform Action Components for Xamarin and Visual Studio we do all the heavy lifting for you and allow you to focus on making your mobile app great. Our components are designed to allow for the maximum of code sharing between Android and iOS mobile apps, all while rendering in the native theme of the OS they are hosted in.
Our components were designed to be quickly added to your mobile project with a minimum of code, making it easy to add high-quality, professional features and functionality to your mobile applications.
That’s why each tool in the Action Components suite has a fully documented API, with comments for every element included. Check out our API documentation to discover every feature that Action Components have to offer.
Empower your mobile development today with Action ComponentsPurchase a year’s license of Action Components for iOS and Android development with Xamarin and Visual Studio for the introductory price of $199 per developer seat. Multi-seat discounts are available upon request, please contact Sales for more details.
Frequently Asked Questions
Can I use Action Components on multiple projects?
Are Action Components royalty free?
Can I install Action Components on multiple development machines?
That said, Action Components are sold on a per developer seat license. If you have multiple developers, each one will need to purchase their own individual copy of the components.
Discounts are available on multi-seat purchase, please contact sales for more details.
What does a year's subscription to Action Components provide?
Additionally, you’ll recieve any new UI control or time-saving feature added to the Action Components suite, again, free of charge, while your subscription is valid.
Will my Action Components stop working if I don't renew my license?
However, you will no longer receive any new bug fixes, updates or feature enhancements so an update to iOS, Android, Xamarin or Visual Studio could potentially break compatibilty with your component version.