Skip to content

Latest commit

 

History

History
57 lines (45 loc) · 3.92 KB

README.md

File metadata and controls

57 lines (45 loc) · 3.92 KB

Solana Mobile dApp Scaffold

The Solana Mobile dApp scaffold is a repository template providing a fast and efficient way for developers to build decentralized mobile applications on the Solana blockchain. With the scaffold, developers can quickly set up and get started with building their Solana mobile dApp. The scaffold includes pre-built components integrated with features, such as wallet connection, airdrop SOL(DEVNET/TESTNET), sign messages and send transactions. Scaffold follows clean architecture and MVVM principles, enabling efficient and robust mobile app development.

Believe me, There is no better time to build consumer mobile dApps.

Screenshots

Home

Dashboard

Image 1 Image 2

Getting Started

To start using scaffold, follow the below steps:

  1. Click on "Use this template" dropdown.
  2. Select "Create a new repository".

Structure

By adhering to best practices for architecture and design patterns, the scaffold ensures that developers can create applications that are easy to maintain and extend, with a separation of concerns between the data , domain and presentation layer.
Below is the structure for Mobile dApp Scaffold considering from app/src/main.

├── java/com/example/solanamobiledappscaffold : App's core logic
│   ├── Common : common classes used through of the project
│   ├── data : folder containing Data layer classes
│   │   ├── di : should house the dependency injection components
│   │   ├── remote : contains classes and interfaces related to handling network requests and responses, as well as remote data sources such as APIs etc
│   │   ├── repository : should contain abstract data sources behind a single interface for the domain layer's use
│   ├── domain : folder containing Domain layer classes
│   │   ├── model : should contain data models and and business logic that define the data
│   │   ├── repository : contains interfaces that the data layer implementation must conform to, providing a separation between the domain and data layer
│   │   ├── use_case : contains specific business logic or operations that the application needs to perform
│   │   ├── utils : reusable utility classes or helper functions
│   ├── presentation : folder containing Presentation layer classes, typically activities, fragments, viewModels etc.
├── res : folder contains application resources such as layouts, strings, and drawable assets, that are used by the UI. 

👨‍💻 Contributing

  • Any contributions you make to this project is greatly appreciated.

Bug / Feature Request

If you find a bug in the app, kindly open an issue here to report it by including a proper description of the bug and the expected result. https://github.com/cdhiraj40/mobile-dapp-scaffold/issues/new?assignees=&labels=enhancement&template=feature_request.md&title=%5BFeature+Request%5D%3A+ are appreciated too. If you feel like a certain feature is missing, feel free to create an issue to discuss with the maintainers.