27 Oct 17:24

0.66.0

e9cb360

Latest

0.66.0

feat(api): use different api to check if plugin exists (#173)

Assets 2

11 Apr 20:17

ranmeirman

0.65.0

a978b4e

Show Accounts

Adding a new action: show account to list all the permitted account connected to the Zapp user token

Assets 2

23 Mar 11:16

yuliroth

0.64.0

e4dc80b

New optional field: characteristics

characteristics is a new property for ui_component plugin type.

A property in the manifest that controls the behavior of the ui component in the UI Builder. Goal: set which components can act as a group, and which components can be added to groups or screens.

"characteristics: {
  "group": true|false,
  "appearance": ["group", "screen"]
  ...
}

Notes

Optional propery.
This property is affecting only plugins of category ui_component
If property does not exist, the UI Component's default settings are:
- "group": false - does not behave like a group
- "appearance": ["group", "screen"] - can be added anywhere, to both screens and groups

Examples

Group component

  "name": "My Group",
  "type": "ui_component",
  "characteristics: {
    "group": true,
    "appearance": ["screen"]
  }
  ...
}

This component will behave exactly like a group
It can be added to a screen only
Other UI Components can be added inside the group

General UI Component

  "name": "My UI Component",
  "type": "ui_component",
  "characteristics: {
    "group": false,
    "appearance": ["group", "screen"]
  }
  ...
}

This UI Component can be added anywhere - both inside a screen and inside a group

UI Component inside group only

  "name": "Group Separator",
  "type": "ui_component",
  "characteristics: {
    "group": false,
    "appearance": ["group"]
  }
  ...
}

This UI Component can be put only inside a group

UI Component for screens only

  "name": "My UI Component",
  "type": "ui_component",
  "characteristics: {
    "group": false,
    "appearance": ["screen"]
  }
  ...
}

This UI Component can be added only to a screen
It cannot be put inside a group

Assets 2

08 Mar 20:07

ranmeirman

0.63.0

4d5eaa4

Support pipes-v2

Allowing to publish with pipes v2 key

Assets 2

19 Feb 09:36

yuliroth

0.62.0

3fae788

Plugin owner publishing restriction

As part of Zapp’s evolution we’re rolling out a significant change in the access permissions for plugin development.

The goal of this change is to secure plugins so developers can submit, modify and remove only plugins from permitted accounts.

The change:

Plugins now has an owner; the owner is a zapp account.
Plugins under responsibility of Zapp Core and Official Plugins teams have already been updated.
Make sure to claim ownership on custom plugins by opening a support ticket stating the plugin name and the zapp account to own it.
Plugins with no owner account will still be visible and usable, but developers will not be able to update them without this action.
Plugin developers must have an account-specific role in order to submit, modify and remove plugins.
Make sure to open support requests with the zapp user of the developer and the zapp account to grant the permission.
Plugin developers using the zappifest CLI will have to use the —account argument as described in the developers.applicaster.com documentation.

zappifest publish <path-to-manifest-json-file> --plugin-id <plugin-id> --access-token <zapp-access-token> --account <account-id>

In order to know on which plugins you can touch when you execute zappifest then you can see the list of an account’s associated plugins

Run zappifest get_account_plugins --access-token <zapp-access-token> --account <account-id>

Assets 2

02 Feb 12:15

simonvaucher

0.61.0

b677830

New optional field: ui_frameworks

Goal: Allow the creation of plugin versions that are targeted only to specific UI Frameworks.

Each plugin version can define an array of supported UI Frameworks.
The default supported UI Framework is called "native".
At the time of the 0.61.0 release, the available UI Frameworks are: ["native", "quickbrick"].
If this field is supplied in the manifest, the plugin version will be saved with the default UI Framework.
List of available UI Frameworks is taken from Zapp's API.

Manifest example I: A plugin supported both in QuickBrick and in Native, e.g. a datasource plugin

{
 "platform": "android",
  "author_name": "Me",
  "name": "My plugin",
  "identifier": "my_plugin",
   ... // etc.
  "ui_frameworks": ["native", "quickbrick"]
}

Manifest example II: A plugin that should be added only to mobile QuickBrick apps - notice the targets. e.g. a view component

{
 "platform": "android",
  "author_name": "Me",
  "name": "My plugin",
  "identifier": "my_plugin",
   ... // etc.
  "targets": ["mobile"],
  "ui_frameworks": ["quickbrick"]
}

What should I expect from this field in the future?

Plugins will be filtered for each app version according to the UI Frameworks, e.g.: Only plugins tagged with a "quickbrick" UI Framework will be shown in the Plugin Gallery when working on an App Version using QuickBrick. TBD.

Assets 2