=================================
=================================
=================================
출처: https://github.com/freshplanet/ANE-In-App-Purchase
README.md
샘플
출처: https://github.com/freshplanet/ANE-In-App-Purchase/issues/30
만약 결제 다이얼로그가 안뜬다면 아래와 같이 매니페스트 부분을 참고하길 바란다.
<android>
<manifestAdditions><![CDATA[
<manifest android:installLocation="auto">
.......................
.............
<uses-sdk android:minSdkVersion="8" />
<!--billing -->
<uses-permission android:name="com.android.vending.BILLING" />
<application android:enabled="true">
<service android:name="com.freshplanet.inapppurchase.BillingService" />
<activity android:name="com.freshplanet.inapppurchase.activities.BillingActivity"
android:theme="@android:style/Theme.Translucent.NoTitleBar.Fullscreen" android:background="#30000000" />
</application>
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>
<uses-permission android:name="android.permission.UPDATE_DEVICE_STATS"/>
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE"/>
<uses-permission android:name="android.permission.READ_PHONE_STATE"/>
.......................
.............
</manifest>
]]></manifestAdditions>
</android>
Can anyone please hint me on what needs to be done in case there's no InAppPurchaseEvent.PURCHASE_SUCCESSFULL sent back from the store? Have tried everything available on these discussions to no avail. From the catLog it all seems to be starting or being called to start and no error or warning or debug hints on any problems... I'm out of tries please help!
@ChrisGamePill as I said in another post, I personally moved to another ANE implementation:
https://github.com/pozirk/AndroidInAppPurchase
as I read that freshplanet's is now outdated.
Pozrik's ANE is Android only, but it's API is more similar to the native in-app API. If you do move I can help you with an example that works.
For iOS, I use Adobe's native extension.
I'm listening to all these events
InAppPurchase.getInstance().init(GOOGLE_LICENSE_KEY, GOOGLE_FLAG_DEBUG); InAppPurchase.getInstance().addEventListener(InAppPurchaseEvent.PRODUCT_INFO_ERROR, store_callback); InAppPurchase.getInstance().addEventListener(InAppPurchaseEvent.PRODUCT_INFO_RECEIVED, store_callback); InAppPurchase.getInstance().addEventListener(InAppPurchaseEvent.PURCHASE_DISABLED, store_callback); InAppPurchase.getInstance().addEventListener(InAppPurchaseEvent.PURCHASE_ENABLED, store_callback); InAppPurchase.getInstance().addEventListener(InAppPurchaseEvent.PURCHASE_ERROR, store_callback); InAppPurchase.getInstance().addEventListener(InAppPurchaseEvent.PURCHASE_SUCCESSFULL, store_callback); InAppPurchase.getInstance().addEventListener(InAppPurchaseEvent.RESTORE_INFO_RECEIVED, store_callback); InAppPurchase.getInstance().addEventListener(InAppPurchaseEvent.SUBSCRIPTION_DISABLED, store_callback); InAppPurchase.getInstance().addEventListener(InAppPurchaseEvent.SUBSCRIPTION_ENABLED, store_callback); and later in my store_callback function, the purchase event can be checked.function store_callback(pe:InAppPurchaseEvent):void
switch(true) { case (pe.type == InAppPurchaseEvent.PURCHASE_SUCCESSFULL): // get data var inAppData:Object = JSON.parse(pe.data); var receipt:Object = inAppData["receipt"]; var productId:String = inAppData["productId"]; // consume product if it is a consumable InAppPurchase.getInstance().removePurchaseFromQueue(productId, JSON.stringify(receipt)); // and update whatever else in game/server etc case (pe.type == InAppPurchaseEvent.PURCHASE_ERROR): // failed! user cancel etc break; } I hope this is of some use. The other ANE looks interesting too!
=================================
=================================
=================================
출처: http://www.adobe.com/devnet/air/articles/android-billing-ane.html
With the In-App Billing Extension for Android from Milkman Games, you can rapidly integrate In-App-app purchasing into your mobile AIR application using ActionScript 3.
The In-App Billing Extension for Android is a 100 percent native Java solution that enables you to:
- Offer your app for free and earn revenue within-app purchases
- Make a purchase with just a few lines of code
- Jumpstart development with a complete sample application, ActionScript 3 documentation, and a getting started guide
- Invoke testing methods to verify purchases before your app goes live
This native extension requires-the AIR 3.5 SDK or a later version. You can download the latest AIR SDK fromhttp://www.adobe.com/special/products/air/sdk/. If you haven't already installed the AIR 3.5 or later SDK for your Flash Professional CS6 or Flash Builder IDE, follow the instructions below.
Enabling the latest AIR SDK in Flash Professional CS6
- Unzip the AIR SDK package on your hard drive.
- Launch Flash Professional CS6.
- Choose Help > Manage AIR SDK.
- Click the Plus (+) Button and navigate to the location of the unzipped AIR SDK.
- Click OK.
- Choose File > Publish Settings.
- Select the AIR 3.5 (or Later) SDK for iOS as the Target.
Enabling the latest AIR SDK in Flash Builder on Windows
- Unzip the AIR SDK package on your hard drive.
- Close Flash Builder.
- Locate the Flash Builder SDK directory. On Windows, this is typically
c:\Program Files\Adobe\Adobe Flash Builder4.6\sdks. - Make a copy of the current Flex SDK directory, and give it a descriptive name. For instance, copy the
4.6.0SDK folder inside/sdksand name the copy4.6.0_AIR37. - Copy and paste the contents of the AIR 3.5 SDK into the
4.6.0_AIR37directory. Accept all changes. - Edit the
flex-sdk-description.xmlfile inside the new directory, and change the value of the<name>tag to match the version of the latest AIR SDK- for instance,Flex 4.6.0 (AIR 3.7). - Open Flash Builder and choose Project > Properties > Flex Compiler >Configure Flex SDKs.
- Click Add and navigate to the new folder location.
Enabling the latest AIR SDK in Flash Builder on OS X
- Copy the contents AIR SDK package to your hard drive.
- Close Flash Builder.
- Locate the Flash Builder SDK directory. On OS X, it is typically
/Applications/Adobe Flash Builder 4.6/sdks/. - Create a new folder inside the
/Flash Builder 4.6/sdks/folder named after the latest SDK- for instance,AIR37SDK, and copy the contents of the AIR SDK package thatyou downloaded in step 1 into it. - Open the Terminal, and merge the new AIR SDK files into your current SDK directory:
sudo cp -Rp /Applications/Adobe\ Flash\ Builder\ 4.6/sdks/AIR37SDK/ /Applications/Adobe\ Flash\ Builder\ 4.6/sdks/4.6.0/ - Edit the flex-sdk-description.xml file inside the new directory, and change thevalue of the
<name>tag to match the version of the latest AIR SDK-for instance,Flex 4.6.0 (AIR 3.7). - Open Flash Builder and choose Project > Properties > Flex Compiler >Configure Flex SDKs.
- Click Add and navigate to the new folder location.
The next step is to add the com.milkmangames.extensions.AndroidIAB.ane library to your project. (If you are not using FlashBuilder 4.6 and later or Flash Professional CS6 and later you'll need to add the AndroidIABAPI.swc library instead.)
In Flash Professional CS6:
- Create a new project of the type AIR for Android.
- Choose File > Publish Settings.
- Click the wrench icon next to Script for ActionScript Settings.
- Select the Library Path tab.
- Click Browse For Native Extension (ANE) File and select the com.milkmangames.extensions.AndroidIAB.ane file.
- Select Player Settings.
- Select the Permissions tab and enable INTERNET.
- Check Manually Manage Permissions and Manifest Additions for this App and press OK.
In Flash Builder 4.6 and later:
- Go to Project Properties (right-click your project in Package Explorer and select Properties).
- Select ActionScript Build Path and click the Native Extensions tab.
- Click Add ANE and navigate to the com.milkmangames.nativeextensions.AndroidIAB.anefile .
- Select ActionScript Build Packaging > Google Android
- Select the Native Extensions tab and enable the Package checkbox for the extension
In FlashDevelop:
- Copy the AndroidIABAPI.swc file to your project folder.
- Inthe explorer panel, right-click the SWC and select AddTo Library.
- Right-click the SWC file in the explorer panel again, select Options,and then select External Library.
You need to configure your AIR application descriptor file to use the AIR 3.5 SDK (or later), include the In-AppBilling extension, and update the Android manifest additions with some AndroidBilling specific settings. (If you're using Flash Professional, make sure you've followed the steps above for Including the Library in Flash ProfessionalCS6, to ensure the changes you make are not overwritten.) For a working example, see example/app.xml.
- Set your AIR SDK to 3.5 or later in the app descriptor file:
<application xmlns="http://ns.adobe.com/air/application/3.5">- Include a link to the extension in the descriptor:
<extensions> <extensionID>com.milkmangames.extensions.AndroidIAB</extensionID> </extensions> - Update your Android manifest additions. The
android.permission.INTERNETandcom.android.vending.BILLINGpermissions must be present for In-App Billing to work. You also must add theminSdkVersionandtargetSdkVersiontags as shown below:
<android> <manifestAdditions><![CDATA[ <manifest android:installLocation="auto"> <uses-sdk android:targetSdkVersion="12"/> <uses-sdk android:minSdkVersion="8"/> <uses-permission android:name="android.permission.INTERNET"/> <uses-permission android:name="com.android.vending.BILLING"/> </manifest> ]]></manifestAdditions> </android> - Save your work, and build an APK file from your application. Although there is nocode in the application yet, it's a good idea to build it now, as Google Play requires you to upload an APK before In-App Billing will work. Make sure you are happy with the application ID, title, p12 certificate, and version number - if these values change, you will need to upload a new draft – and it can take anywhere from minutes to hours before Google processes the APK file!Important Note for Flash Builder Users: Flash Builder 4.6 will change your application ID every time you switch between a 'release' and 'debug' build. Because the IDs of the uploaded APK and the APK you test with must match, you will either need to commit to using only one type of build during testing, or uploading a new build and waiting a few minutes every time you need to change targets. One solution to mitigate this is to build only for debug until you're ready to publish app, then rebuild and re-upload a new draft at that time. In Flash Builder 4.7, this behavior can be overridden by removing the '.debug' from the 'AppId' box under Run/Debug Configurations Dialog Box (Project Properties > Build Packaging > Run / Debug Settings > Edit.)
- Go to http://play.google.com/apps/publish/ to access the Google Play Developer Panel.
- Choose '+Add new application' to define your new app.
- Enter a title and language for your app, then select 'Upload APK'.
- Select 'Upload Your First APK', and select the APK file you created in step 1.
- From the 'Services & APIs' tab, copy and paste your License Key, and save it for future reference.
- From the 'In-App Products' tab, select 'Add New Product', and enter a name for the first in-app item you'd like to sell.If the Item is a Subscription, choose the Subscription button. Otherwise,choose 'Managed'. (Although you may still select 'Unmanaged', the option is deprecated as all Google Play Billing items are now managed.)
- Enter the Product ID Title, Description, pricing and language information for your product. Then choose Save, and change the status to Active by choosing the 'Activate' option.
- Repeat the process for each product you'd like to sell. If you'd like to create products that match with the example code, create managed items called 'my_levelpack' and 'my_spell', and a subscription called 'my_subscription'.
In order to test In-App Billing, you'll need to update Google Play with your test account address, and possibly make changes to the registered account on your phone.When you first setup your Android device, you entered a Google/ Gmail Account to use with Google Play – the 'primary account' on your phone. This gmail address needs to be added to the Google Play developer panel in order to test In-app Billing. To add the test email to Google Play:
- Select the 'Settings' tab from the left.
- Select 'Account Details'
- Under 'Gmail accounts with testing access', enter the gmail address that is the primary account on the device. You may enter multiple email addresses separated by commas if you wish.
- Unfortunately,Google does not let you 'buy things from yourself'. In other words, if the primary Gmail account is the same as the one you used to sign up for Google Play Developer, you'll need to change the primary account on the device to something else.Although many Android devices will let you remove and add accounts, this isn't good enough for Google Play testing- you'll have to factory reset the device. See the documentation for your device's make and model if you need to factory reset the phone.
While you wait for Google to process your APK, you can start adding code to your application.Follow these steps to get started:
- Import the API Classes:
import com.milkmangames.nativeextensions.android.*; import com.milkmangames.nativeextensions.android.events.*; - Initialize the API by calling
AndroidIAB.create().You can check theAndroidIAB.isSupported()method first, to ensure the current platform is Android and not an unsupported platform (like iOS or Windows).
It is important that this initialization occurs in the entry point of your application. If you are using Flex/MXML, this means you must call create() in the initialize() event of the main class (not a View constructor or createComplete callback.) If you are using pure ActionScript, you must call create() inside the Constructor function of the Document Class. If you are using timeline code in Flash, call this once at the beginning of Frame 1.
if (AndroidIAB.isSupported()) { AndroidIAB.create(); } - Call the
AndroidIAB.androidIAB.startBillingService("YOUR_PUBLIC_KEY_HERE")method to begin interactions with Android's In-App Billing server. Use the public key you retrieved earlier in the section Building the Application and Uploading the Draft to Google Play, Step 6.If the current device will not support In-App Billing (because it doesn't have Google Play, for instance), you'll receive theAndroidBillingEvent.SERVICE_NOT_SUPPORTEDevent. Otherwise, when the service is ready, you'll receive theAndroidBillingEvent.SERVICE_READYevent; once that happens, you may begin calling the other API methods to make purchases.
// listeners for billing service startup AndroidIAB.androidIAB.addEventListener(AndroidBillingEvent.SERVICE_READY,onReady); AndroidIAB.androidIAB.addEventListener(AndroidBillingEvent.SERVICE_NOT_SUPPORTED, onUnsupported); // start the service AndroidIAB.androidIAB.startBillingService("YOUR_PUBLIC_KEY_HERE"); private function onReady(e:AndroidBillingEvent):void { trace("service now ready- you can now make purchases."); } private function onUnsupported(e:AndroidBillingEvent):void { trace("sorry, in app billing won't work on this phone!"); } Once you've connected to Google Play, you can request information about the items that the user has previously purchased. It's a good idea to do this as soon as your app starts, in case the user has installed the app on a new device, had an item refunded, or their inventory has otherwise changed.
- Add event listeners for
AndroidBillingEvent.INVENTORY_LOADEDandAndroidBillingErrorEvent.INVENTORY_LOAD_FAILED. When theINVENTORY_LOADEDevent is dispatched, its 'purchases' property will be populated with a vector array ofAndroidPurchaseobjects, representing the purchases the user has previously made.TheLOAD_INVENTORY_FAILEDis dispatched when an error occurs attempting to load the inventory. Because it is an error event, you should listen for it even if you don't plan to do anything about the error, to avoid an uncaught exception in your code:
// listen for inventory events AndroidIAB.androidIAB.addEventListener(AndroidBillingEvent.INVENTORY_LOADED, onInventoryLoaded); AndroidIAB.androidIAB.addEventListener(AndroidBillingErrorEvent.LOAD_INVENTORY_FAILED, onInventoryFailed); function onInventoryLoaded(e:AndroidBillingEvent):void { for each(var purchase:AndroidPurchase in e.purchases) { trace("You own the item:"+purchase.itemId); // this is where you'd update the state of your app to reflect ownership of the item } } function onInventoryFailed(e:AndroidBillingErrorEvent):void { trace("Something went wrong loading inventory: "+e.text); } - To start the inventory request, call
AndroidIAB.androidIAB.loadPlayerInventory():
// load the player's current inventory AndroidIAB.androidIAB.loadPlayerInventory(); In addition to loading the list of items the player already owns, you may wish to load details about items your app offers for sale, such as title, description, and price.
- Add event listeners for
AndroidBillingEvent.ITEM_DETAILS_LOADEDandAndroidBillingErrorEvent.ITEM_DETAILS_FAILED. When theITEM_DETAILS_LOADEDevent is dispatched, its itemDetails property will be populated with a vector array ofAndroidItemDetailsobjects, representing the details about items available in your app's store.TheITEM_DETAILS_FAILEDis dispatched when an error occurs attempting to load the item details. Because it is an error event, you should listen for it even if you don't plan to do anything about the error, to avoid an uncaught exception in your code:
// listen for inventory events AndroidIAB.androidIAB.addEventListener(AndroidBillingEvent.ITEM_DETAILS_LOADED, onItemDetails); AndroidIAB.androidIAB.addEventListener(AndroidBillingErrorEvent.ITEM_DETAILS_FAILED, onDetailsFailed); function onItemDetails(e:AndroidBillingEvent):void { for each(var item:AndroidItemDetails in e.itemDetails) { trace("item id:"+item.itemId); trace("title:"+item.title); trace("description:"+item.description); trace("price:"+item.price); } } function onDetailsFailed(e:AndroidBillingErrorEvent):void { trace("Something went wrong loading details: "+e.text); }- To start the details request, pass a Vector array of item ids to the
loadItemDetails()function. (The IDs you choose will need to be defined later in the Google Play control panel after you've uploaded your APK):
// load info about the items for sale var allItemIds:Vector.<String>=new <String>["my_spell", "my_subscription", "my_levelpack"]; AndroidIAB.androidIAB.loadItemDetails(allItemIds); - First, add event listeners for
AndroidBillingEvent.PURCHASE_SUCCEEDEDandAndroidBillingErrorEvent.PURCHASE_FAILED:
// listen for purchase events AndroidIAB.androidIAB.addEventListener(AndroidBillingEvent.PURCHASE_SUCCEEDED, onPurchaseSuccess); AndroidIAB.androidIAB.addEventListener(AndroidBillingErrorEvent.PURCHASE_FAILED, onPurchaseFailed); - When
PURCHASE_SUCCEEDEDis dispatched, its purchases property will be a vector array containinganAndroidPurchaseobject for the item that was bought.When this event fires, you can callloadPlayerInventory()again to update the list of items the player now owns. If something goes wrong,PURCHASE_FAILEDwill be dispatched instead:
function onPurchaseSuccess(e:AndroidBillingEvent):void { var purchase:AndroidPurchase=e.purchases[0]; trace("you purchased the item "+purchase.itemId); AndroidIAB.androidIAB.loadPlayerInventory(); } function onPurchaseFailed(e:AndroidBillingErrorEvent):void { trace("Something went wrong with the purchase of "+e.itemId+": "+e.text); } - The extension provides a number of functions for testing purchase event responses with fake items that you have not registered in Google Play. The following example illustrates how to initiate such a fake purchase:
// this will start a purchase dialog and on success callback the PURCHASE_SUCCEEDED event AndroidIAB.androidIAB.testPurchaseItemSuccess(); // this will start a purchase dialog then cause a PURCHASE_FAILED event AndroidIAB.androidIAB.testPurchaseItemCancelled(); - To start the purchase process for a real item, call
AndroidIAB.androidIAB.purchaseItem(itemId),whereitemIdis one of the products you registered on theGoogle Play Developer panel.Note that for the purchase to work on an unpublished app, the test account mustbe set up properly as described above in Section Preparing for Device Testing. As long as you are using a test account, your credit card will not be charged- make sure that the purchase window includes the phrase "You will not be charged."To initiate the purchase of a real item:
AndroidIAB.androidIAB.purchaseItem("your_itemid");- If your item is a Subscription Item, use the
purchaseSubscriptionItem(itemId)call instead. Because not all phones will support subscriptions, you should check theareSubscritpionsSupported()method first:
if(AndroidIAB.androidIAB.areSubscriptionsSupported()) { AndroidIAB.androidIAB.purchaseSubscriptionItem("your_itemid"); } else { trace("this device needs a Google Play Update to support subscriptions."); } Some in-app purchases may be treated as permanent upgrades,such as pack of new levels added to the game. For these types of items, the user purchases them one time, and they are then treated as permanently owned.
Some games or apps may benefit from a 'consumable' type of item: something that can be purchased, used up, and purchased again. To implement such an item, implement the consumption flow as described below:
- Add event listeners for
AndroidBillingEvent.CONSUME_SUCCEEDEDandAndroidBillingErrorEvent.CONSUME_FAILED. When theCONSUME_SUCCEEDEDevent is dispatched, the item has been removed from the player's inventory and can be purchased again, and you should callloadPlayerInventory()again to update the state of the player's inventory.TheCONSUME_FAILEDevent is dispatched when an error occurs attempting to consume an item. Because it is an error event, you should listen for it even if you don't plan to do anything about the error, to avoid an uncaught exception in your code:
// listen for consumption events AndroidIAB.androidIAB.addEventListener(AndroidBillingEvent.CONSUME_SUCCEEDED, onItemConsumed); AndroidIAB.androidIAB.addEventListener(AndroidBillingErrorEvent.CONSUME_FAILED, onConsumeFailed); function onItemConsumed(e:AndroidBillingEvent):void { trace("you consumed the item "+e.itemId); AndroidIAB.androidIAB.loadPlayerInventory(); } function onConsumeFailed(e:AndroidBillingErrorEvent):void { trace("Something went wrong consuming "+e.itemId+": "+e.text); } - To start the consume request, pass the item's id to the
consumeItem()method. (Note that you cannot consume item unless you've previously calledloadPlayerInventory()and the item is present):
// consume an item AndroidIAB.androidIAB.consumeItem("my_spell"); If you're using Flash Builder4.6 or later, or Flash Professional CS6 or later, and have added the In-AppBilling for Android extension library as described above, then you can compile as you usually do directly from the IDE. If not and you are building your appwith the extension from the command line, then you'll need to specify thedirectory containing the com.milkmangames.extensions.AndroidIAB.ane file.
Here is an example build command line:
[PATH_TO_AIR_SDK]\bin\adt -package -target apk-debug -storetype pkcs12 -keystore [YOUR_KEYSTORE_FILE] -storepass [YOUR_PASSWORD] anesample.apk app.xml anesample.swf -extdir [DIRECTORY_CONTAINING_ANE_FILE] If your app is not receiving events as expected, try these tips:
- Make sure you've saved a draft of the application to the Android Market Developer Website as described in Building the Application and Uploading a Draft to Google Play.
- Make sure you've updated your application descriptor file as described in Updating your application descriptor file.
- Make sure the Google email address associated with your device is a Registered Developer Email or a Test Account Email as described in Preparing for Device Testing.
- If you're testing the IAB example application as is, make sure that you've created the In-App Product IDs that it uses: a managed product named
my_levelpackand an unmanaged one namedmy_spell.See Building the Application and Uploading a Draft to Google Play for information on how to set up products. - If you're using a subscription product, make sure you're using the
purchaseSubscriptionItem()method. - Google can take anywhere from an hour to a day to update its servers after you upload a new draft APK or change a product; wait at least an hour and try again.
- If you want to implement purchase verification on your own server:
- The
AndroidPurchaseobject contains the propertiesitemId,developerPayload,orderId,jsonData,signature,purchaseTime, andpurchaseToken. You can pass all or a subset of this data back to your server for verification. Refer to Google's latest documentation for information on how to validate a purchase using your key.
- The
- If your application appears to stop responding after calling certain functions:
- If you don't have a debugger attached, and you're doing something that's causing an
ErrorEvent, execution will halt but you may not notice it. Always add event listeners of the typeAndroidBillingErrorEvent. - If you've done that, look carefully at your function signature, and make sure the type is
e:AndroidBillingErrorEventand note:AndroidBillingEvent.
- If you don't have a debugger attached, and you're doing something that's causing an
- If you want to implement purchase verification on your own server:
Now that you have the In-App Billing Extension for Android up and running, you may want to explore the ActionScript 3 documentation, read about Using the iOS In-App Purchase native extension for Adobe AIR, or check out the other tools from available from Milkman Games.
=================================
=================================
=================================
출처: https://forums.adobe.com/thread/1184574
=================================
=================================
=================================
Since there is no documentation for this ANE, I will post how I made this work for Android and hopefully it will help others.
Application.xml:
The documentation says to add a service to the XML, but I have found this is wrong. You need to add an activity:
Next thing you need to do in your code is to initialize the service:
The GOOGLE_PLAY_LICENSE_KEY can be found in the Google play developer console under the Services & APIs section. NOTE: the initialization process is async, and for some reason freshplanet did not implement an event on initialization end. The only solution I have found is to make sure you wait enough time for the initialization to complete (bad bad practice.. but no good solution was found except to fork and add the event).
To make a purchase:
Everything is async so you have to add event listeners to receive success or error responses.
The InAppPurchaseEvent class holds a data property that is a JSON string with the information received from Google play. The content of the JSON is defined in the Google play in app purchases documentation.
For example, after you make a purchase you can extract the data like this:
Consuming products:
Where receipt is a JSON string that you get from Google play. This receipt is received right after you purchase or you can get it by querying the user's previous transactions.
More things to notice that will prevent problems
That's it, hope it helps, hope it's correct, comment if not.