HUAWEI IAP provides a product management system (PMS) for managing the prices and languages of in-app products (including games) in multiple locations. Other than thses two catagories that developers can use directly in Huawei App Gallary, are there other functions PMS provides and how can developers use them?
The Product Management System (PMS) API allows you to create and update product and promotion information, including the product price and display language, implementing in-app management of product prices and display languages for localized pricing for global locations.
Creating Products: Including Creating a Non-Subscription Product (Consumables and Non-consumables) and Creating a Subscription Product (auto-renewable)
Querying Products: You can call the Querying Details of a Product API to query a specific product based on the app ID and product ID or call the Querying Products by Criteria API to query all products that meet the criteria that you have specified, for example, all products in a specified app and all products in a specified subscription group, which can be sorted by attribute.
Updating Product Information: Basic product information includes the product name, language, price, and status. You can call the Updating a Product or Updating Products in Batches API to update basic product information.
Managing Product Statuses: The status of a product is specified when it is created. You can then call the Activating Products in Batches or Deactivating Products in Batches API to update product statuses in batches.
Managing Product Promotion Information: You can call the Creating Product Promotion Information API to create product promotion information for both subscription and non-subscription products, including the including the promotion time period, applicable countries/regions, and promotional prices. To update the information, call the Updating Product Promotion Information API.
Related
I've developed an application with in-app purchase functionality. And for that, I used the in_app_purchase package.
App has more than one product want to generate dynamic product ID without doing manually .
Its currently Impossible to add dynamic products to purchase. Each product has to be added in dashboard and reviewed before it can be used in the app. For multiple price product purchase you can use some third party payment gateway that supports Apple Pay. For example Razor pay or stripe
https://pub.dev/packages/razorpay_flutter
https://pub.dev/packages/stripe
If you wish to use only the IAP then you may have to set products at different prices for example
product 1 - 0.99
product 2 - 1.99
product 3 - 2.99 and so on
and use that for different products. That will be an exhaustive list of product pricing.
I have an idea but I have no technological background. Here is the idea:
The following information is collected from the customers:
• Products they are looking for (e.g. trainers, jeans, t-shirts, hoodies, bags).
• Sizes for each product category.
• Budget for each product category.
• Favourite brands for each product category.
• Colours for each product category.
Website searches all leading online luxury retailers and automatically sends the best deals and sale items based on the customer’s saved preferences. A list of suitable deals are sent to the customer via email on a weekly basis, or alternatively, the customer can log in to their account via our website in order to view their up-to-date deals selection.
Customers can change their preferences at any time via the website and the following week’s selection will be updated accordingly.
(Website needs to be able to send deals of multiple brands for different product categories e.g. customer wants hoodies from Nike, Adidas or Puma and wants trainers from New Balance or Converse)
What software will do this/where can I get this software?
Thanks!
Olly.
I have created one reference IAP Product on iTunes connect, but I want to know if there is any way to add a new product or replace with new product name and price to an existing Product programmatically.
I am getting a number of products from Server side and there is a chance to increase the number of products in future.
Application is about selling Audio books.
Option 1 : Consumable In App Purchase
It Will have different product ids with common price.
e.g. Audio A and Audio B both have price $2 then both Audio A and Audio B will share common product id.
All user purchase will be managed from server
Option 2 : Non Consumable In App Purchase
Will have different product ids for each audio.
I am confuse because there could be 10k + Audios. Can we create dynamic Non Consumable item ?
Any ideas how to make this scalable?
For that amount of dynamic content you will probably have to implement some kind of custom "currency" which would be a consumable item.
You can either make it completely arbitrary in amount, or you could try to make a few different IAP products to correspond with audio books in different price ranges. So something like $0.99$ book purchase, $1.99 book purchase, etc.
Apple allows up to 1000 in app purchase products to be created. So you cannot create 10k+ products. Also finding the product amongst this will be a very complex task for the user. See if you can bundle books of same price into a single bundle and price them economically so that users tend to purchase. 10 books for 10$ is better than 20$.
You should definitely go with non-consumable option since audio books do not deplete in time.
You have to maintain your own server in between the app and the Apple in app purchase and you need to have a user account management to track what books the user has purchased. You can create a different SKU For each price and and associate the product id with the book on your server and track the purchases done by the user on your own. Since multiple books could map to the same in-app product id, your app should handle the restoring purchases explicitly and based on your app user login enable the audio books on different devices.
Basically the in app flow would be used just for payment purposes. Enabling and downloading of the audio books will have to be controlled between your app and the server.
I would use something like a 2-Dimensional int array. [x][y] whereas x is your individual product ID, and y is the count on how many items are sold. You can then always link your x to a certain price. This way you can easily keep track on how many audio files 'y' with product ID 'x' got bought.
Never give two different audio files with maybe equivalent price the same ID. An ID should always be unique since there are a lot of problems that might occur later:
Implementing the audio files in a seperate database
Audio file becomes cheaper/more expensive, then you´d have to use another ID anyway
ios InApp purchases: Why do you have to fetch a list of products before selling them?
Following this list: http://troybrant.net/blog/2010/01/in-app-purchases-a-full-walkthrough/
Why do we even need to fetch the list of products before selling them? Why not just sell the hardcoded id's we create for the app?
It's a bit difficult to sell a product without stating the price.