Build a User Management App with Swift and SwiftUI
This tutorial demonstrates how to build a basic user management app. The app authenticates and identifies the user, stores their profile information in the database, and allows the user to log in, update their profile details, and upload a profile photo. The app uses:
- Supabase Database - a Postgres database for storing your user data and Row Level Security so data is protected and users can only access their own information.
- Supabase Auth - users log in through magic links sent to their email (without having to set up passwords).
- Supabase Storage - users can upload a profile photo.
If you get stuck while working through this guide, refer to the full example on GitHub.
Before we start building we're going to set up our Database and API. This is as simple as starting a new Project in Supabase and then creating a "schema" inside the database.
Create a project#
- Create a new project in the Supabase Dashboard.
- Enter your project details.
- Wait for the new database to launch.
Set up the database schema#
Now we are going to set up the database schema. We can use the "User Management Starter" quickstart in the SQL Editor, or you can just copy/paste the SQL from below and run it yourself.
- Go to the SQL Editor page in the Dashboard.
- Click User Management Starter.
- Click Run.
You can easily pull the database schema down to your local project by running the
db pull command. Read the local development docs for detailed instructions.
_10supabase link --project-ref <project-id>_10# You can get <project-id> from your project's dashboard URL: https://supabase.com/dashboard/project/<project-id>_10supabase db pull
Get the API Keys#
Now that you've created some database tables, you are ready to insert data using the auto-generated API.
We just need to get the Project URL and
anon key from the API settings.
- Go to the API Settings page in the Dashboard.
- Find your Project
service_rolekeys on this page.
Building the App#
Let's start building the SwiftUI app from scratch.
Create a SwiftUI app in Xcode#
Open Xcode and create a new SwiftUI project.
Add the supabase-swift dependency.
https://github.com/supabase-community/supabase-swift package to your app. For instructions, see the Apple tutorial on adding package dependencies.
Create a helper file to initialize the Supabase client.
You need the API URL and the
anon key that you copied earlier.
These variables will be exposed on the application, and that's completely fine since you have
Row Level Security enabled on your database.
Set up a Login view#
Set up a SwiftUI view to manage logins and sign ups. Users should be able to sign in using a magic link.
The example uses a custom
redirectTo URL. For this to work, add a custom redirect URL to Supabase and a custom URL scheme to your SwiftUI application. Follow the guide on implementing deep link handling.
After a user is signed in, you can allow them to edit their profile details and manage their account.
Create a new view for that called
ProfileView.swift, you used 2 model types for deserializing the response and serializing the request to Supabase. Add those in a new
Now that you've created all the views, add an entry point for the application. This will verify if the user has a valid session and route them to the authenticated or non-authenticated state.
Add a new
Update the entry point to the newly created
AppView. Run in Xcode to launch your application in the simulator.
Bonus: Profile photos#
Every Supabase project is configured with Storage for managing large files like photos and videos.
Let's add support for the user to pick an image from the library and upload it. Start by creating a new type to hold the picked avatar image:
Add PhotosPicker to Profile page#
Finally, update your Models.
You no longer need the
UpdateProfileParams struct, as you can now reuse the
Profile struct for both request and response calls.
If you upload additional profile photos, they'll accumulate
avatars bucket because of their random names with only the latest being referenced
public.profiles and the older versions getting orphaned.
To automatically remove obsolete storage objects, extend the database
triggers. Note that it is not sufficient to delete the objects from the
storage.objects table because that would orphan and leak the actual storage objects in
the S3 backend. Instead, invoke the storage API within Postgres via the
Enable the http extension for the
extensions schema in the Dashboard.
Then, define the following SQL functions in the SQL Editor to delete
storage objects via the API:
_34create or replace function delete_storage_object(bucket text, object text, out status int, out content text)_34returns record_34language 'plpgsql'_34security definer_34as $$_34declare_34project_url text := '<YOURPROJECTURL>';_34service_role_key text := '<YOURSERVICEROLEKEY>'; -- full access needed_34url text := project_url||'/storage/v1/object/'||bucket||'/'||object;_34begin_34select_34into status, content_34result.status::int, result.content::text_34FROM extensions.http((_34'DELETE',_34url,_34ARRAY[extensions.http_header('authorization','Bearer '||service_role_key)],_34NULL,_34NULL)::extensions.http_request) as result;_34end;_34$$;_34_34create or replace function delete_avatar(avatar_url text, out status int, out content text)_34returns record_34language 'plpgsql'_34security definer_34as $$_34begin_34select_34into status, content_34result.status, result.content_34from public.delete_storage_object('avatars', avatar_url) as result;_34end;_34$$;
Next, add a trigger that removes any obsolete avatar whenever the profile is updated or deleted:
_32create or replace function delete_old_avatar()_32returns trigger_32language 'plpgsql'_32security definer_32as $$_32declare_32status int;_32content text;_32avatar_name text;_32begin_32if coalesce(old.avatar_url, '') <> ''_32and (tg_op = 'DELETE' or (old.avatar_url <> coalesce(new.avatar_url, ''))) then_32-- extract avatar name_32avatar_name := old.avatar_url;_32select_32into status, content_32result.status, result.content_32from public.delete_avatar(avatar_name) as result;_32if status <> 200 then_32raise warning 'Could not delete avatar: % %', status, content;_32end if;_32end if;_32if tg_op = 'DELETE' then_32return old;_32end if;_32return new;_32end;_32$$;_32_32create trigger before_profile_changes_32before update of avatar_url or delete on public.profiles_32for each row execute function public.delete_old_avatar();
Finally, delete the
public.profile row before a user is deleted.
If this step is omitted, you won't be able to delete users without
first manually deleting their avatar image.
_14create or replace function delete_old_profile()_14returns trigger_14language 'plpgsql'_14security definer_14as $$_14begin_14delete from public.profiles where id = old.id;_14return old;_14end;_14$$;_14_14create trigger before_delete_user_14before delete on auth.users_14for each row execute function public.delete_old_profile();
At this stage you have a fully functional application!