You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/articles/getting-started.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Getting Started
2
2
3
-
Get a hybrid desktop app running in under five minutes — a native Avalonia window hosting your web frontend, with type-safe bridge calls between C# and JavaScript.
3
+
Get a hybrid desktop app running in under five minutes — a native Avalonia window hosting your web frontend so you can start building product features right away.
4
4
5
5
## The main path
6
6
@@ -51,6 +51,12 @@ fulora dev
51
51
52
52
You'll see a native window open with your app inside, ready for normal product work.
53
53
54
+
After these three steps, you have:
55
+
56
+
- A native desktop window hosting your web app
57
+
- A web frontend and native host already wired together
58
+
- Fulora services ready for normal app development
59
+
54
60
Alternatively, use `dotnet new` directly:
55
61
56
62
```bash
@@ -59,13 +65,17 @@ cd MyApp
59
65
dotnet run --project MyApp.Desktop
60
66
```
61
67
62
-
## What you'll end up with
68
+
## Fulora services already use the bridge underneath
69
+
70
+
When you use `fulora new`, you mostly work with app-level services and UI code first. Under the hood, those services talk across the Fulora bridge for you.
71
+
72
+
- Your frontend still runs inside a native WebView
73
+
- Your native code still runs in-process in C#
74
+
- Fulora services use generated bridge contracts underneath, so app code can stay focused on product features
63
75
64
-
After the three steps above, you have a native desktop window hosting your web app, with Fulora services ready for normal app development.
76
+
This means you can start by building screens and calling services, then learn the bridge layer when you need custom native capabilities or plugin work.
65
77
66
-
- The **UI** runs inside a native WebView
67
-
- The **backend** runs in-process in C#
68
-
- Fulora connects them with generated bridge contracts underneath
78
+
If you want the mental model, it looks like this:
69
79
70
80
```
71
81
┌───────────────────────────────────┐
@@ -84,16 +94,6 @@ After the three steps above, you have a native desktop window hosting your web a
84
94
└───────────────────────────────────┘
85
95
```
86
96
87
-
## Fulora services already use the bridge underneath
88
-
89
-
When you use `fulora new`, you mostly work with app-level services and UI code first. Under the hood, those services talk across the Fulora bridge for you.
90
-
91
-
- Your frontend still runs inside a native WebView
92
-
- Your native code still runs in-process in C#
93
-
- Fulora services use generated bridge contracts underneath, so app code can stay focused on product features
94
-
95
-
This means you can start by building screens and calling services, then learn the bridge layer when you need custom native capabilities or plugin work.
96
-
97
97
## Manual path: add Fulora to an existing Avalonia app
98
98
99
99
If you already have an Avalonia project or need full control over the setup.
0 commit comments