Ruby on Rails Developer based in Dublin
In my last post , we learned how to enter full screen mode on Android. We used two methods. First, we setup a Bridge Component to toggle full-screen mode with a button and then we demonstrated using path configuration to trigger a full-screen view. With iOS, it’s just as straightforward. We will start with Path Configuration and then move on to using a Bridge Component. Prerequisites I’m assuming…
The default experience for hotwire native and native apps in general is to show the Top Bar at the top of you app but sometimes it’s advantageous to create a more immersive experience. A great example is when you press the full screen-mode on the YouTube app. This uses all available screen real estate so the user can enjoy the content. To enable full-screen mode with a Hotwire Native application,…
Welcome to the final post on debugging Hotwire Native iOS and Hotwire Native Android applications. We have covered everything from obvious questions to ask to logging , webview debugging and now we’re finishing with breakpoints. Both Xcode and Android Studio have powerful debuggers that suspend the program, allowing you to inspect different objects and variables at that point of suspension. Let’s…
Welcome back to the Debugging Hotwire Native series, the series to help you when things go wrong. Today we’re talking about logs. Regardless of the programming language or framework I use, I always strive to keep logs within my line of sight. This practice has come from over 10 years of working on 100’s of applications. Working with Hotwire Native means that you must understand four different…
Continuing on our journey to learn about debugging Hotwire Native applications, we are going to touch on specific techniques. Previous articles covered broad strokes, and today we are digging into WebView Debugging. Remember, Hotwire Native works by wrapping a webview in a native app. iOS WebView Debugging We’ll start with iOS because there are more steps, and you are more than likely going to…
Once you have a good understanding of how Hotwire Native works, debugging problems gets much easier. However, to truly understand it, the best approach is to build a few apps. Spin up a repo that you can play around with and try things with. At this stage, I’ve worked on at least 10 Hotwire Native apps—a combination of my own, new greenfield apps for clients and existing apps for clients. I have…
When I recently attended RailsWorld, I had the chance to do a lightning talk titled “Debugging Hotwire Native”, which was 10 minutes in length. It was a ton of fun, but I think it would be more useful to share what I learned about debugging Hotwire Native Applications here in more detail so people can revisit it from time to time. In this article, we will not cover specific techniques but provide…
In the last few posts, we have achieved a lot. We rendered our Rails app within a native app with very few lines of code. We added some navigation tricks that demonstrate how to make the app feel native and finally we added bridge components to demonstrate native sprinkles such as a Save button on our modals. However, we are really just beginning to touch on what’s possible. Between the native…
In the last post, we explained how to navigate to a native screen and render it using Android Views or Jetpack compose. However, there is a trade-off. Duplicating your screen multiple times across platforms comes at a price. That price is complexity and cost. Yet, sometimes, we want to take advantage of native platform features. Today, we’ll show you how to take advantage of native features from a…
In my previous article , I explained the steps needed to set up path configuration. Path Configuration is a vital concept in both Hotwire Native iOS and Hotwire Native Android. It allows you to display certain content as web screens, modals, or native screens. Crucially, you can update this from the server to facilitate deployment compared to the app store process. Today, we will render a native…