Swiftify vs. Xamarin

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Swiftify
Score 9.0 out of 10
Small Businesses (1-50 employees)
When Apple rolled out Swift back in 2014, Objective-C was set to be replaced. Even nowadays, however, there are plenty of apps and projects that still use Objective-C, and developers are faced with the prospect of either starting again from scratch or attempting to convert them to Swift. Swiftify for Xcode is designed to automate much of the conversion process, handling the task of replacing syntax while letting you focus on other aspects of migrating your project to…
$5
per file
Xamarin
Score 6.0 out of 10
N/A
N/AN/A
Pricing
SwiftifyXamarin
Editions & Modules
Pay As You Go
$5
per file
Cloud 30 (Monthly)
$49
30 files per month
Cloud 100 (Monthly)
$99
100 files per month
Cloud 300 (Monthly)
$199
300 files per month
Cloud 1000 (Monthly)
$299
1000 files per month
Cloud 30 (Yearly)
$399
300 files per year
Cloud 100 (Yearly)
$799
1000 files per year
Cloud 300 (Yearly)
$1,599
3000 files per year
Cloud 1000 (Yearly)
$2,399
10000 files per year
Offline Converter
custom pricing
per seat
Xamarin
Free
Offerings
Pricing Offerings
SwiftifyXamarin
Free Trial
YesNo
Free/Freemium Version
YesYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
SwiftifyXamarin
Considered Both Products
Swiftify
Chose Swiftify
This is the only product that I use when I convert codes. So far I'm happy and will stick with it.
Chose Swiftify
There's not much to compare - we haven't found any proprietary like it. Existing OpenSource solutions are unmaintained and Swiftify supports the latest versions of Swift.
Chose Swiftify
Swiftify tries to convert the code even if the code can not be executed in a real situation.
I chose Swiftify because most of the times you just need to convert one line, one method... That of course, it is using and used by other code that you didn't add in the conversion code, …
Xamarin
Chose Xamarin
Android Studio and IOS SDK are some of the competing programming methods for mobile development that competes with Xamarin. However, these utilize other programming languages like Java, or Objective C. In addition, these methods may be used more directly with Android or IOS …
Chose Xamarin
We use both Xamarin and React Native to create cross-platform applications fast. React Native is relatively new at our company and few developers have embraced coding in it as compared to developers building in Xamarin. I have noticed developers have it easy jumping from coding …
Chose Xamarin
Xamarin allows us to natively code against IOS and Android as opposed to just putting a Skin over it. Because of this native code stack the performance on Xamarin is off the charts better. You can really see the performance when you are using native phone features like GPS, …
Chose Xamarin
As I said before: Code sharing and using existing skills was the most important factor to choose Xamarin. With phonegap code sharing exists but business logic must be written in JS.
Chose Xamarin
Coming from a .NET background I always wanted to like Xamarin. Now that Microsoft bought them and made the product available to all, it's a no brainer.
Chose Xamarin
In Native app development we need to employ specialized developers solving some business problems in different technologies. Xamarin solves that problem to some extent delivering a native application experience. Hybrid has the same code base but suffers from lack of performance.
Chose Xamarin
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 …
Chose Xamarin
None of the HTML-based cross-platform solutions can easily provide a native look and feel like Xamarin can. I've had to rescue multiple organizations that went down this path only to be disappointed with the results.
Chose Xamarin
Apache Cordova is nothing more than a HTML Web VIew App. I've built an app using Cordova and it was a mess. With Xamarin, you get the platform level capabilities, which make the performance, in theory, no different than real native development. Cordova is not suitable for any …
Chose Xamarin
Xamarin is a good platform compared to Cordova, as it gives better API access, documentation and customer support as well as a robust community. It allows you to develop code using native Visual Studio and helps the developer to reuse the codebase for different platforms, …
Best Alternatives
SwiftifyXamarin
Small Businesses
Jotform
Jotform
Score 8.5 out of 10
Swiftify
Swiftify
Score 9.0 out of 10
Medium-sized Companies
Jotform
Jotform
Score 8.5 out of 10
Swiftify
Swiftify
Score 9.0 out of 10
Enterprises
ServiceNow Now Platform
ServiceNow Now Platform
Score 9.1 out of 10
Swiftify
Swiftify
Score 9.0 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
SwiftifyXamarin
Likelihood to Recommend
8.2
(0 ratings)
7.0
(0 ratings)
Likelihood to Renew
-
(0 ratings)
10.0
(0 ratings)
Usability
-
(0 ratings)
10.0
(0 ratings)
Support Rating
8.3
(0 ratings)
10.0
(0 ratings)
Implementation Rating
-
(0 ratings)
10.0
(0 ratings)
User Testimonials
SwiftifyXamarin
Likelihood to Recommend
For me as a picky person I never used the file convertor but for a small portion of code, it is good. With the classes that have more than one initializer, it got confusing and I had to dig to find the exact issue to fix.
Read full review
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.
Read full review
Pros
  • Put in your Objective-C code, select the version of Swift language to convert, click convert. That's all!
  • Swiftify is now creating a platform to convert Objective C to #C, something that can help for different development projects platforms.
  • Swiftify offers a few free converts to try to show you the power of it. Their price for a subscription plan is really good for big projects.
Read full review
  • We save development time with Xamarin, because we use Xamarin Forms an so we can share most of the code over 3 platforms.
  • We can use our C# knowledge to develop iOS and Android Apps.
  • Xamarin's integration into Visual Studio is very good and became even better during the last releases of Visual Studio.
Read full review
Cons
  • It lacks general performance and availability
  • It doesn't handle Objective-C macro well
  • Overall conversion speed expected to be much better
Read full review
  • 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.
Read full review
Likelihood to Renew
No answers on this topic
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.
Read full review
Usability
No answers on this topic
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
Read full review
Support Rating
There are constant upgrades to improve the conversion.
Read full review
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
Read full review
Implementation Rating
No answers on this topic
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.
Read full review
Alternatives Considered
Swiftify tries to convert the code even if the code can not be executed in a real situation. I chose Swiftify because most of the times you just need to convert one line, one method... That of course, it is using and used by other code that you didn't add in the conversion code, but you just need to convert that for now. In this situation, Swiftify converts the code, other ones such as iSwift will report an error in the code and will not convert it.
Read full review
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.
Read full review
Return on Investment
  • good ROI, saves a lot of time.
Read full review
  • 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.
Read full review
ScreenShots

Swiftify Screenshots

Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of