Does the Ethereum logo have a trademark and can be used on a company-developed app or official website? - logos

The company's developed APP and official website use Ethereum, can it mark the Ethereum logo?

Related

Is there a way to detect when a user has paid for a Google App Marketplace app you published?

We're currently in the process of publishing a Laravel web app to Google App Marketplace and I have read every section of the guides found here https://developers.google.com/gsuite/marketplace/overview but there doesn't seem to be any mention of detecting when a user has successfully paid for your app. Because ultimately what we want to achieve is to prevent just anybody from accessing the registration/initial setup page and only grant access to G Suite domains that have paid for the app.
The G Suite Marketplace does not support payments. If you have implemented your own payment solution then it's up to you to restrict access to paying users.

Publication of Marketplace Application for Organization Unit Service Account Access

We've a request to build a Marketplace SDK app which would implicitly grant service account access to any organizational unit it was installed within. We've been told this is a common practice, but the app was rejected in the review process as we link to an informational page for the Google Chrome extension this app supports.
Other Marketplace apps appear to do this, notably RingCentral for Google Calendar.
Does anyone have advice regarding how to characterize this app so it passes the review process?
Thank you,
Ben

Mobile Chrome Apps payments API

I'm working on publishing my Chrome App to Google Play using the Chrome Apps for Mobile tools.
As Mihai Ionescu mentioned, there are two Google Wallet Merchant APIs: Google Wallet for Digital Goods API (used for Chrome Web Store apps) and Google Play In-app Billing API (used for Android apps). As far as I'm located in Belarus, Play API is supported for my country, but Digital Goods is not, though the Supported Locations table doesn't mention any API differences.
Mobile Chrome Apps Payment Plug-in ReadMe says:
This plugin allows you to sell digital and virtual goods within your app. It is built on the Android In-App Billing API and the iOS In-App Purchase API. It provides a JavaScript interface similar to the Chrome Apps Google Wallet for Digital Goods API, so that you can use the same API in both a desktop and mobile Chrome App.
Questions
What exact API (Google Play or Digital Goods) is used for mobile Chrome Apps and can I really use one merchant API for both mobile and desktop versions?
If different APIs are used, is there any way for a desktop Chrome app to check that a user has purchased the mobile version via Google Play?
For mobile, you will use Google Play In-app Billing API, as the item will ultimately end up on the Google Play Store. Regardless of the API, you will only need to create a single Google Wallet Merchant account to sell your goods, thus using a single Merchant Id.
Unfortunately, there is no way to verify a user's purchases within the app on different platforms (web vs mobile).

Limiting a private gadget to specific OU

I've been reading through the docs for Gmail Contextual Gadgets and I can't find information on whether or not a private gadget can be deployed to a specific OU or it has to be turned on for the entire org. It seems like you can do this if you publish your gadget to the Marketplace, but in our scenario the gadget may not provide enough functionality to qualify as a Marketplace app.
The Google Apps Extensions console only allows you to deploy a gadget to the entire domain. As you mentioned, using the Google Apps Marketplace you can limit an app to only certain OUs. You can publish your marketplace app as private to your domain, if you don't want to share it with the whole world.

Cannot submit app to google app marketplace

I am integrating google app marketplace SDK to my web app and publishing it to chrome web store as specified here
I have published the app to restricted users (domain users only) to test the workflow.
The app is published to the domain users but when I access it and click to install, it adds as a chrome extension but I cannot access it as a Google Marketplace app.
For marketplace integration, I have created a project under Google APIs Console and enabled Google Apps Marketplace SDK. If I click the "Test Install Flow" button
the app is successfully installed as a marketplace app which I can access from universal app navigator of my domain email.
Question
Is this the best way I can test whether the app installs as a marketplace application for restricted users? Can I not see it added by directly installing it from the published url?
I have gone through a few links which mention that it is now not easy to submit app to marketplace unless you use atleast one of the Google Services APIs and get through the Google Apps Marketplace Listing Review Request.
Can not post Google Apps Marketplace Listing Review Request for API Project
How to create listing on google apps marketplace?
If I do not intend to use any of the Google Services APIs, and just use Google App MarketPlace SDK, will I not be able to get the app listed in marketplace?
Any help is much appreciated!
Assuming you have added both "DOMAIN_INSTALLABLE" and "GOOGLE_DRIVE" in your mainfest.json file. Try adding "app" section to the manifest. See https://developers.google.com/chrome/apps/docs/developers_guide

Resources