···

       
2
       
 
       


     

       
3
       
 
       
In this guide, we're going to build a **simple multi-user app** that publishes your current "status" as an emoji.

     

       
4
       
 
       


     

       
0
       
 
       

     

       
0
       
 
       

     

       
5
       
 
       
At various points we will cover how to:

     

       
6
       
 
       


     

       
7
       
 
       
- Signin via OAuth

     
···

       
65
       
 
       
```

     

       
66
       
 
       


     

       
67
       
 
       
When the user logs in, the OAuth client will create a new session with their repo server and give us read/write access along with basic user info.

     

       
0
       
 
       

     

       
0
       
 
       

     

       
68
       
 
       


     

       
69
       
 
       
Our login page just asks the user for their "handle," which is the domain name associated with their account. For [Bluesky](https://bsky.app) users, these tend to look like `alice.bsky.social`, but they can be any kind of domain (eg `alice.com`).

     

       
70
       
 
       


     
···

       
231
       
 
       
      </div>`}

     

       
232
       
 
       
</div>

     

       
233
       
 
       
```

     

       
0
       
 
       

     

       
0
       
 
       

     

       
234
       
 
       


     

       
235
       
 
       
You can examine this record directly using [atproto-browser.vercel.app](https://atproto-browser.vercel.app). For instance, [this is the profile record for @bsky.app](https://atproto-browser.vercel.app/at?u=at://did:plc:z72i7hdynmk6r22z27h6tvur/app.bsky.actor.profile/self).

     

       
236
       
 
       


     
···

       
349
       
 
       
})

     

       
350
       
 
       
```

     

       
351
       
 
       


     

       
0
       
 
       

     

       
0
       
 
       

     

       
0
       
 
       

     

       
0
       
 
       

     

       
352
       
 
       
## Step 5. Creating a custom "status" schema

     

       
353
       
 
       


     

       
354
       
 
       
The collections are typed, meaning that they have a defined schema. The `app.bsky.actor.profile` type definition [can be found here](https://github.com/bluesky-social/atproto/blob/main/lexicons/app/bsky/actor/profile.json).

     
···

       
586
       
 
       
  `

     

       
587
       
 
       
})}

     

       
588
       
 
       
```

     

       
0
       
 
       

     

       
0
       
 
       

     

       
589
       
 
       


     

       
590
       
 
       
## Step 8. Optimistic updates

     

       
591
       
 
       


     

···

       
2
       
 
       


     

       
3
       
 
       
In this guide, we're going to build a **simple multi-user app** that publishes your current "status" as an emoji.

     

       
4
       
 
       


     

       
5
       
+
       
![A screenshot of our example application](./docs/app-screenshot.png)

     

       
6
       
+
       


     

       
7
       
 
       
At various points we will cover how to:

     

       
8
       
 
       


     

       
9
       
 
       
- Signin via OAuth

     
···

       
67
       
 
       
```

     

       
68
       
 
       


     

       
69
       
 
       
When the user logs in, the OAuth client will create a new session with their repo server and give us read/write access along with basic user info.

     

       
70
       
+
       


     

       
71
       
+
       
![A screenshot of the login UI](./docs/app-login.png)

     

       
72
       
 
       


     

       
73
       
 
       
Our login page just asks the user for their "handle," which is the domain name associated with their account. For [Bluesky](https://bsky.app) users, these tend to look like `alice.bsky.social`, but they can be any kind of domain (eg `alice.com`).

     

       
74
       
 
       


     
···

       
235
       
 
       
      </div>`}

     

       
236
       
 
       
</div>

     

       
237
       
 
       
```

     

       
238
       
+
       


     

       
239
       
+
       
![A screenshot of the banner image](./docs/app-banner.png)

     

       
240
       
 
       


     

       
241
       
 
       
You can examine this record directly using [atproto-browser.vercel.app](https://atproto-browser.vercel.app). For instance, [this is the profile record for @bsky.app](https://atproto-browser.vercel.app/at?u=at://did:plc:z72i7hdynmk6r22z27h6tvur/app.bsky.actor.profile/self).

     

       
242
       
 
       


     
···

       
355
       
 
       
})

     

       
356
       
 
       
```

     

       
357
       
 
       


     

       
358
       
+
       
And here we are!

     

       
359
       
+
       


     

       
360
       
+
       
![A screenshot of the app's status options](./docs/app-status-options.png)

     

       
361
       
+
       


     

       
362
       
 
       
## Step 5. Creating a custom "status" schema

     

       
363
       
 
       


     

       
364
       
 
       
The collections are typed, meaning that they have a defined schema. The `app.bsky.actor.profile` type definition [can be found here](https://github.com/bluesky-social/atproto/blob/main/lexicons/app/bsky/actor/profile.json).

     
···

       
596
       
 
       
  `

     

       
597
       
 
       
})}

     

       
598
       
 
       
```

     

       
599
       
+
       


     

       
600
       
+
       
![A screenshot of the app status timeline](./docs/app-status-history.png)

     

       
601
       
 
       


     

       
602
       
 
       
## Step 8. Optimistic updates

     

       
603