Skip to content

Follow-up to #1023 / #1024 / #1025 - Xamarin references #1026

Description

@MiroslavHustak

Reason for opening this issue:

Follow-up to #1023 / #1024 / #1025.
That PR fixes the dead fabulous.dev links, but the surrounding text on both /guides/mobile-apps/ and /use/mobile-apps/ still describes a discontinued stack.

Xamarin.Forms has been retired (Microsoft moved to .NET MAUI), so "Option 1: ... using Xamarin" (/use/mobile-apps/) no longer applies.
Fabulous also moved off Xamarin.Forms — it now targets .NET MAUI and Avalonia (fabulous-dev/Fabulous).
The sample apps (Fabulous Weather, FabulousContacts) are old Xamarin.Forms-era examples.

Issue Location:
/use/mobile-apps/index.md
https://fsharp.org/use/mobile-apps/

Issue:
Xamarin.Forms has been retired by Microsoft in favor of .NET MAUI, so the former Xamarin-based workflow is no longer the recommended path.

Suggested fix:

Option 1: Build Android and iOS Apps using F# and Fabulous

Fabulous is F#'s declarative, MVU-style UI framework and now targets .NET MAUI and Avalonia, letting you build apps for iOS, Android, macOS, Windows and Linux from a single F# codebase.

// Links to sample apps to be discontinued


Issue Location:
/guides/mobile-apps/index.md
https://fsharp.org/guides/mobile-apps/

Issue:
dtto

Suggested fix:

Frameworks

  • Fabulous - F# functional app development for Android, iOS, macOS, Windows and Linux, using the MVU (Model-View-Update) architecture on top of .NET MAUI and Avalonia.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions