![garden tracker mac garden tracker mac](https://i.etsystatic.com/21688625/r/il/a0fcc3/2468840048/il_794xN.2468840048_e1bw.jpg)
![garden tracker mac garden tracker mac](https://jacanswers.com/wp-content/uploads/2021/12/canva-nurse-MAC7_ufuHDc.jpg)
There's also a page that's pushed onto the navigation stack via tapping on a plant on the "currently planted" page - which shows the plant's name along with a Wikipedia page - so I could test out a WebView. This third page groups plants by type, vegetables, herbs, and flowers - arranged on a TabView. There is a third page which is also reached via the MasterDetailPage and that's the garden center page - where I can restock on plants - which adds them back into the "currently planted" page. Those two pages are both comprised of ListViews with straight up TextCells and are navigated to via a MasterDetailPage. (Unfortunately though I love to garden, I do sometimes I have the touch of death.) Taking it off the list of "planted" plants and moving it to another screen of "dead plants". Via a ContextAction on a cell in the ListView the app allows me to record that a plant died. The app holds a list of plants that are "currently planted in the ground" in a ListView. So I could theoretically keep track of what I have planted, what managed to die on me, and then restock plants. So the app that I decided to create would be a "Garden Tracker". I love to garden, in fact, I'm sitting in my backyard typing this looking at my garden. Well, it's summer right now in Wisconsin.
GARDEN TRACKER MAC CODE
Then add in the macOS app, and see how it works without adding any platform specific code or making any compromises to functionality.
GARDEN TRACKER MAC ANDROID
The idea is to get a generic app working on iOS and Android with 100% shared code (the intialization code notwithstanding). In order to test that out, I decided to throw together a quick app that contains a lot of the UI elements, navigation metaphors, and Xamarin.Forms techniques (like Behaviors) that I have found myself using a lot lately. And all the code can be found on GitHub, of course. In other words, how much work would it be for me to create a macOS app from an existing Xamarin.Forms application and are there any shortfalls that I would hit immediately?Īnd most importantly of all, would I be able to stay away from having to write any macOS specific code? I want to prove out, at least to myself, the viability of adding a macOS app to a Xamarin.Forms solution and have it work well enough where I could potentially deliver it to a customer. That's what I want to take a look at in this article - how much work it really takes to create a Xamarin.Forms macOS app. And according to everything I've read, it "should just work". There are a couple of big time features in this release that are hiding under that last version number being bumped from 2.3.4.Ī show stopping feature of Xamarin.Forms 2.3.5 is the ability to create a macOS app. The big buzz ever since Microsoft Build has been about Xamarin.Forms 3.0 - and rightfully so - there's a lot of cool features in it.īut I don't want to overlook the next release of Xamarin.Forms - and that's 2.3.5.