Cocoa Touch (iOS) vs Yesod: What are the differences?
Cocoa Touch (iOS): The Cocoa Touch collection of frameworks includes everything needed to create iOS apps. The Cocoa Touch layer contains key frameworks for building iOS apps. These frameworks define the appearance of your app. They also provide the basic app infrastructure and support for key technologies such as multitasking, touch-based input, push notifications, and many high-level system services; Yesod: A RESTful Haskell web framework built on WAI. Yesod believes in the philosophy of making the compiler your ally, not your enemy. We use the type system to enforce as much as possible, from generating proper links, to avoiding XSS attacks, to dealing with character encoding issues. In general, if your code compiles, it works. And instead of declaring types everywhere you let the compiler figure them out for you with type inference.
Cocoa Touch (iOS) and Yesod can be categorized as "Frameworks (Full Stack)" tools.
"Backed by Apple" is the top reason why over 5 developers like Cocoa Touch (iOS), while over 5 developers mention "Haskell" as the leading cause for choosing Yesod.
Yesod is an open source tool with 2.11K GitHub stars and 329 GitHub forks. Here's a link to Yesod's open source repository on GitHub.
Apple, Snapchat, and Third Iron are some of the popular companies that use Cocoa Touch (iOS), whereas Yesod is used by DoxIQ, FP Complete, and SimplyRETS. Cocoa Touch (iOS) has a broader approval, being mentioned in 32 company stacks & 19 developers stacks; compared to Yesod, which is listed in 5 company stacks and 5 developer stacks.
What is Cocoa Touch (iOS)?
What is Yesod?
Need advice about which tool to choose?Ask the StackShare community!
What are the cons of using Cocoa Touch (iOS)?
What are the cons of using Yesod?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
When we first built the ArifZefen app our focus was around validating our business assumptions and finding a good product fit. Once we got to a few thousand users, it became clear that we needed to make quality a priority and that meant we needed a reliable tool that will allow us to monitor the health of our app. Crashlytics (now Fabric by Twitter ) was on a short list of solutions we closely explored and we were very happy with its ease of integration and the consistency it brought to our Cocoa Touch (iOS) and Android SDK crash monitoring.
Its daily pulse emails were also super informative in giving us a good sense of how each platform was doing in terms of crash-free and new users, daily actives and other relevant session data. These emails also surfaced any anomalies in daily trends, alerting us of any reason for concern. Overall, Crashlytics was instrumental in allowing us to quickly discover and diagnose crashes and it is one of the main reasons we were able to keep our app store ratings reasonable high. But perhaps even more importantly, we were able to set a high quality bar for our users that absent Crashlytics would have been difficult to maintain.