The Keyhole Labs team is proud to announce the recent release of the mobile Fly Tyer World application. The cross-platform mobile app is now available free, on the app store for both Android and iOS devices.
Fly Tyer World is a Go-reference web application built by Keyhole labs that displays Youtube fly-tying instructional videos organized into virtual fly boxes by both species and location. The mobile application boasts the same functionality.
It can be challenging to decide on the right strategy for reaching the mobile audience, though. If you decide an app is what you need, the next question is “what are my options?” In general terms, the types of mobile applications you could choose to build can be divided into three groups: vendor-native, cross-platform, and hybrid web.
In this post, we give an overview of the various mobile development strategies on our shortlist for enterprise clients to consider; for example, Xamarin, Flutter, React Native, and Ionic. For each tool, we give a brief introduction and highlight the key advantages and disadvantages found in implementing each mobile development approach.
For more than a decade, we have been developing applications with C# and XAML. Throughout that time, the pair has really only been known for Desktop (WPF) and UWP applications.
Later came Xamarin, which utilizes C# as a unified language to share between all platforms. Then Xamarin.Forms was introduced, which was different in that it utilized XAML to develop the user interface with a single codebase for cross-platform (iOS, Android, UWP).
This progression has excited all the WPF developers out there. The only remaining platform left was web development. At one time, Silverlight was the option, but it was deprecated because of heavy loading and security concerns of browser plug-in solutions.
Then came the WebAssembly [also known as Web Assembly Modules (WASM)] that web browsers can directly execute without having to parse a source file.
In this post, we will discuss how to create a rich user browser interface using the cross-platform Uno Platform and WebAssembly technology. The example application will walk through building Models, ViewModel and View under a shared project that is common to all different platform-specific projects.
The client I’m currently assisting has begun to move applications from more monolithic architecture into a more modern, cloud-based architecture. The organization is a bit of a .NET anomaly in that it is a company that’s primarily Java, yet has some .NET.
So even though Microsoft has a list of framework tools (such as Azure Service Fabric and Azure App Service), it’s fair to say that asking a primarily Java-focused company to use those tools could be an uphill battle. This is where .NET Standard and .NET Core have come to the rescue.
I work with a ton of smart people and I’m pretty amazed at how fast they can pick up on things from reading. I, however, cannot really understand it fully until I touch it. So let’s build a quick RESTful Web API step by step to see how challenging it is. We’ll be using .NET Standard, .NET Core, and ASP.NET Core.
Keyhole assited the client in development of Ecosport UV, which provides a new, educational approach to proactive skin protection from harmful UV rays.
The application allows the user to view the current UV index and temperature by zip code search. Ecosport UV then provides education to the user: what that UV Index means, how it affects the user, and how to proactively combat sun damage. They then have the option to view suggested sun protection techniques for the current index range, including sunscreen application, clothing and eye protection.