https://github.com/enflow/component-brick

The enflow/component-brick package provides the logic to connect to the iOS and Android side of the Brick framework.
https://github.com/enflow/component-brick

Last synced: about 1 month ago
JSON representation

The enflow/component-brick package provides the logic to connect to the iOS and Android side of the Brick framework.

• Host: GitHub
• URL: https://github.com/enflow/component-brick
• Owner: enflow
• Created: 2019-08-29T17:22:29.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2024-03-15T12:40:34.000Z (10 months ago)
• Last Synced: 2024-08-10T23:44:16.970Z (5 months ago)
• Language: Blade
• Homepage: https://enflow.nl
• Size: 37.1 KB
• Stars: 3
• Watchers: 4
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Connect with the Brick framework

The `enflow/component-brick` package provides the logic to connect to the iOS and Android side of the Brick framework. **Brick is meant to be used as the server-side variant of the Brick framework. See "Whats Brick"**

## What's Brick

Brick is Enflow's framework to create hybrid iOS and Android apps. These wrappers communicate with the server side trough a JavaScript bridge. This package writes a tag to your application that those native wrappers communicate with. The primary function of this package is to support push notifications by fetching the device ID from the device and write it to a table.

## Installation

You can install the package via composer:

``` bash

composer require enflow/component-brick

```

### Migrations

This package includes a migration that needs to be published. This table (`brick_devices`) includes the mapping between the user and the hardware UUID of the iOS or Android device required for push notifications. New devices will be automatically assigned to the user. You can publish this migration by running:

`php artisan vendor:publish --provider="Enflow\Component\Brick\BrickServiceProvider"`

## Usage

This package adds the `BrickManager` class to the container and injects a `$brickManager` variable to all views. This variable can be used to render the required tag automatically. We recommend adding this to the end of the master template, just before the `