Home/Base44 (Vibe Coding) Tutorials/Build a Private Bookmark Manager with Base44
Base44 (Vibe Coding) TutorialBeginner30 min read

Build a Private Bookmark Manager with Base44

Build and publish a private bookmark manager with Base44 using one entity, built-in authentication, owner-only permissions, search, filters, favorites, editing, and confirmed deletion.

Tutorial ForgeUpdated Aug 5, 2026
This public demo uses temporary sample data. The real authenticated app and owner-only records remain protected.

1. What you will build

You will build Bookmark Pocket, a minimal private bookmark manager. The signed-in owner can add, edit, favorite, search, filter, sort, open, and delete their own bookmarks — nothing more.
The whole app uses one Bookmark entity. There are no external APIs, no AI features, no uploads, no payments, and no third-party integrations. That is what keeps the build small, fast, and cheap.

2. Before you begin

Requirements
This tutorial is intentionally designed around one comprehensive prompt with no refinement rounds. Every extra prompt costs credits, so the goal is a single build followed by testing.

3. Create the Base44 project

  1. 1.Open Base44 using the button at the top of this page.
  2. 2.From the Base44 home screen, click the main prompt field labeled "Describe the app you want to create."
  3. 3.Paste the master prompt from the next section.
  4. 4.Click Build/Send.
  5. 5.Do not choose a template and do not add integrations.

4. One-pass master build prompt

Copy this prompt exactly as written and send it once.
Master build prompt — send once
Create a small, production-ready web app named "Bookmark Pocket". PURPOSE A private personal bookmark manager where the signed-in owner can save, organize, search, edit, favorite, and delete useful links. KEEP THE BUILD SMALL Use Base44 native features only. Do not add external APIs, AI features, payments, email, social login, analytics, images, file uploads, agents, automations, or third-party integrations. Do not ask follow-up questions. Use the exact decisions below and build the complete app in one pass. AUTHENTICATION AND ACCESS - Use Base44's built-in email/password authentication. - Require sign-in to access the app. - Do not allow anonymous data access. - Each user may read, create, update, and delete only their own bookmarks. - Enforce ownership in Base44 entity permissions, not only in the interface. - Users must never see another user's records. DATA Create one entity named Bookmark with: - title: required string - url: required URL string - category: required string - notes: optional multiline string - isFavorite: boolean, default false - createdBy: owner/user reference populated automatically - createdAt and updatedAt timestamps INTERFACE - Responsive single-page dark interface with a clean, minimal design. - Header with app name, total bookmark count, and sign-out control. - Compact form to add a bookmark with Title, URL, Category, Notes, and Favorite. - Validate required fields and URL format with friendly inline messages. - Display bookmarks as readable cards. - Each card shows title, domain/URL, category, optional notes, favorite status, and created date. - Clicking the title or an Open button launches the URL in a new tab with safe link attributes. - Search title, URL, category, and notes. - Category filter with an All option. - Favorites-only toggle. - Sort newest first by default. - Edit in a small dialog or inline form. - Delete only after confirmation. - Clear loading, success, error, no-results, and empty states. - Add three sample bookmarks only if they can be created as records owned by the currently signed-in user; otherwise start empty with a helpful empty state. DESIGN - Near-black background, charcoal panels, off-white text, muted gray secondary text, and one restrained amber accent. - Use a normal readable sans-serif body font. - Subtle borders, medium corner radius, modest shadows, and accessible focus states. - Avoid excessive animation, gradients, glassmorphism, oversized headings, decorative illustrations, and complex navigation. - Mobile layout must remain easy to use. QUALITY AND SECURITY - Use semantic labels and keyboard-accessible controls. - Sanitize and validate URLs. - Never expose service credentials or privileged APIs in client code. - Verify create, edit, favorite, filtering, external-link opening, and delete flows. - Keep code and components simple and reusable. - Prepare the app for Base44 publishing. Build this now with sensible defaults and do not ask any questions.

5. Let Base44 build

Base44 may describe its plan and inspect authentication and permission guidance automatically while it works. The successful reference build completed without asking any follow-up questions.
It also correctly declined to create service-role seed data, because those sample records would not belong to the signed-in user. Instead it showed a helpful empty state. That is the right outcome.
Do not add features yet

Wait until you have tested the app before requesting anything new. Extra requests now cost credits and can undo working behaviour.

6. Understand the data and security

  1. 1.Bookmark is the only entity in the app.
  2. 2.The createdBy field identifies the owner of each record.
  3. 3.Permissions must be enforced by Base44 at the entity/data layer.
  4. 4.Filtering records only in the interface is not security.
  5. 5.Signed-out users must not be able to access bookmark data.
  6. 6.One signed-in user must not be able to read or change another user's bookmarks.
A hidden page is not access control

Base44 permissions must protect the records even when someone calls the data API directly. Hiding a screen or filtering a list in the interface does not stop a direct request.

7. Test the completed app

Functional test checklist
The reference app passed create, favorite, filter, edit, confirmed delete, and empty-state tests before publication.

8. Run the Base44 security scan

  1. 1.Click Publish in the editor.
  2. 2.In the Publish dialog, click Run scan.
  3. 3.Wait for the result.
  4. 4.Do not publish if the scan reports unresolved access-control problems.
Reference result

The completed reference app reported "No risks."

9. Publish

When your app is ready, click the Publish button in the Base44 editor. Continue through the on-screen prompts, review the options Base44 presents, and confirm the publication. When Base44 tells you the app is live, open the published link in a new tab and test it once more.
Tip

Save or bookmark your published URL so you can return to the app later.

Publishing the app does not make anyone's bookmarks public. Users must still sign in, and Base44's owner-only entity permissions protect each account's records.

10. Keep credit usage low

Spend fewer credits

Use the master prompt once. Test before asking for changes. Avoid optional suggestions such as bulk actions, Notion sync, tag systems, AI features, or integrations. Make only essential corrections, and stop as soon as the checklist passes.

The successful reference build used a single build prompt and no refinement prompt.

11. Final review

Final review
Tags
#Base44#Vibe Coding#Bookmark Manager#Authentication#CRUD#Beginner