Skip to main content
Prompts Maui Banking App CRUD Developer

developer coding template risk: medium

Maui Banking App CRUD Developer

Act as a Software Developer specializing in Maui mobile development to create a cross-platform banking system application supporting CRUD operations. Implement intuitive UI, backen…

  • Policy sensitive
  • Human review

PROMPT 

Act as a Software Developer specializing in mobile application development using Maui. Your task is to create a banking system application that supports CRUD (Create, Read, Update, Delete) operations.

You will:
- Develop a user interface that is intuitive and user-friendly.
- Implement backend logic to handle data storage and retrieval.
- Ensure security measures are in place for sensitive data.
- Allow users to add new banking records, edit existing ones, and delete records as required.

Rules:
- Use Maui framework for cross-platform compatibility.
- Adhere to best practices in mobile app security.
- Provide error handling and user feedback mechanisms.

Variables:
- ${appName:BankingApp} - The name of the application.
- ${platform:CrossPlatform} - Target platform for the application.
- ${databaseType:SQLite} - The database to be used for data storage.

INPUTS

appName REQUIRED

The name of the application.

e.g. BankingApp

platform REQUIRED

Target platform for the application.

e.g. CrossPlatform

databaseType REQUIRED

The database to be used for data storage.

e.g. SQLite

ROLES & RULES

Role assignments

  • Act as a Software Developer specializing in mobile application development using Maui.
  1. Use Maui framework for cross-platform compatibility.
  2. Adhere to best practices in mobile app security.
  3. Provide error handling and user feedback mechanisms.

EXPECTED OUTPUT

Format
code
Constraints
  • Use Maui framework
  • SQLite database
  • Include CRUD operations
  • Implement security measures
  • Error handling and user feedback

SUCCESS CRITERIA

  • Develop a user interface that is intuitive and user-friendly.
  • Implement backend logic to handle data storage and retrieval.
  • Ensure security measures are in place for sensitive data.
  • Allow users to add new banking records, edit existing ones, and delete records as required.

FAILURE MODES

  • May generate incomplete or non-functional application code.
  • Might insufficiently address banking-level security requirements.
  • Could neglect proper integration of specified variables.

CAVEATS

Dependencies
  • Template variables: appName, platform, databaseType.
Missing context
  • Data model/schema for entities
  • Specific security features (e.g., auth, encryption)
  • Output format (e.g., full project code, folder structure)
  • Detailed success criteria or testing requirements
Ambiguities
  • 'Banking records' is undefined – e.g., accounts, transactions, users?
  • Vague 'security measures' and 'best practices' without specifics.
  • No details on UI structure or elements.

QUALITY

OVERALL
0.65
CLARITY
0.85
SPECIFICITY
0.55
REUSABILITY
0.75
COMPLETENESS
0.50

IMPROVEMENT SUGGESTIONS

  • Define entities explicitly: 'Banking records include BankAccount (Id, Name, Balance, UserId) and Transaction (Id, AccountId, Amount, Date, Type).'
  • Specify security: 'Implement user authentication with secure login, encrypt sensitive data with AES, use HTTPS.'
  • Clarify output: 'Provide a complete .NET MAUI project structure with XAML pages, C# code-behind, Models, ViewModels, Services, and SQLite database setup.'
  • Add constraints: 'UI must include ListView for records, Forms for CRUD, validation, and error dialogs.'

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR DEVELOPER