That's the frontend code, it doesn't include the backend API services, which are closed source.

the backend (the AppView) can be found here:

https://github.com/bluesky-social/atproto/tree/main/packages...

there are various supporting services written in Go as well

https://github.com/bluesky-social/indigo

Which is what I said in the second sentence

AppView is a specific term of art within the Bluesky federation architecture: https://atproto.com/guides/glossary#app-view, you were incorrect in identifying the public frontend repo as the AppView.

A frontend is (can be) part of an App View. It is quite literally the app you view the network through. There can also be headless app views and app views which have no backend

this is not correct

The glossary specifically calls out the UI as part of an app view. Can you explain why it is not according to you?

that's not the appview, that's the client

App View is a bit fuzzy of a term. To me it seems like a combination of frontend, backend, custom lexicon, and supporting services. There isn't really another place in the spec or design where clients or browsers fit in, which do in fact provide a view of the network via an app.

"UI" is part of the definition they give in the glossary

https://atproto.com/guides/glossary#app-view