Note 1 - Nature of Business and Significant Accounting Operations | 9 Months Ended |
Jul. 31, 2014 |
Notes | ' |
Note 1 - Nature of Business and Significant Accounting Operations | ' |
Note 1 - Nature of Business and Significant Accounting Operations |
|
Pocket Games, Inc. (the “Company”) was incorporated on October 4, 2013 (“Inception”) under the laws of the State of Florida. The Company is engaged in the development, marketing and sale of interactive games for mobile devices, tablets and computers. The Company has limited customers, products and revenues to date, and follows the accounting guidelines for accounting for and reporting for a development stage enterprise in preparing its financial statements. |
|
The accompanying unaudited financial statements for Pocket Games, Inc. have been prepared in accordance with accounting principles generally accepted in the United States of America (the “U.S.”) and with the rules and regulations of the U.S. Securities and Exchange Commission for interim financial information. Operating results for interim periods are not necessarily indicative of results that may be expected for the fiscal year as a whole. These statements reflect all adjustments, consisting of normal recurring adjustments, which in the opinion of management are necessary for fair presentation of the information contained therein, and should be read in conjunction with the summary of significant accounting policies and notes to financial statements included in the Company’s filing of Form S-1 and any amendments as filed with the Securities and Exchange Commission. |
|
The Company has adopted a fiscal year end of October 31. |
|
Development Stage Company |
The Company is currently considered a development stage company. As a development stage enterprise, the Company discloses the deficit accumulated during the development stage and the cumulative statements of operations and cash flows from inception to the current balance sheet date. An entity remains in the development stage until such time as, among other factors, revenues have been realized. To date, the development stage of the Company’s operations consists of developing the business model and marketing concepts. |
|
Use of Estimates |
|
The preparation of financial statements in conformity with accounting principles generally accepted in the United States requires management to make estimates and assumptions that affect the reported amounts of assets and liabilities, and the disclosure of contingent assets and liabilities at the date of the financial statements, and the reported amounts of revenues and expenses during the reporting period. Actual results could differ from those estimates. |
|
Segment Reporting |
Under FASB ASC 280-10-50, the Company operates as a single segment and will evaluate additional segment disclosure requirements as it expands its operations. |
|
Fair Value of Financial Instruments |
Under FASB ASC 820-10-05, the Financial Accounting Standards Board establishes a framework for measuring fair value in generally accepted accounting principles and expands disclosures about fair value measurements. This Statement reaffirms that fair value is the relevant measurement attribute. The adoption of this standard did not have a material effect on the Company’s financial statements as reflected herein. The carrying amounts of cash, accounts payable and accrued interest reported on the balance sheet are estimated by management to approximate fair value primarily due to the short term nature of the instruments. The Company also had debt instruments that required fair value measurement on a recurring basis. |
|
Foreign Currency Transactions |
|
The Company translates foreign currency transactions to the Company's functional currency (United States Dollar), at the exchange rate effective on the invoice date. If the exchange rate changes between the time of purchase and the time actual payment is made, a foreign exchange transaction gain or loss results which is included in determining net income for the period. |
|
Cash and Cash Equivalents |
|
Cash and cash equivalents consist of cash and short-term highly liquid investments purchased with original maturities of three months or less. There were no cash equivalents at July 31, 2014 and October 31, 2013. |
|
Accounts Receivable and Allowance for Doubtful Accounts |
|
Accounts receivable may result from our product sales or outsourced application development services. Management must make estimates of the uncollectability of accounts receivables. Management specifically analyzed customer concentrations, customer credit-worthiness, current economic trends and changes in customer payment terms when evaluating the adequacy of the allowance for doubtful accounts. |
|
Revenue Recognition |
|
The Company generates revenue from three sources; sale of game applications, sale of advertising provided with games, and outsourced application development services. The Company recognizes revenue using four basic criteria that must be met before revenue can be recognized: (1) persuasive evidence of an arrangement exists; (2) delivery has occurred; (3) the selling price is fixed and determinable; and (4) collectability is reasonably assured, which is typically after receipt of payment and delivery, net of any credit card charge-backs and refunds. Determination of criteria (3) and (4) are based on management’s judgment regarding the fixed nature of the selling prices of the products delivered and the collectability of those amounts. Provisions for discounts and rebates to customers, estimated returns and allowances, and other adjustments are provided for in the same period the related sales are recorded. The Company defers any revenue for which the product has not been delivered or is subject to refund until such time that the Company and the customer jointly determine that the product has been delivered or no refund will be required. Revenues on advertising are deferred and recognized ratably over the advertising period. |
|
Revenue from October 4, 2013 (Inception) through July 31, 2014, includes only outsourced application development services recognized in accordance with ASC 605-28 "Milestone Method". The application development revenue, totaling approximately $45,540, as amended (see Note 5), will be earned upon attainment of stipulated milestones through October 31, 2014. The Company may bill for these services prior to attainment of the performance milestones. Revenues recognized under this arrangement for the three and nine months ended July 31, 2014 and the period from October 4, 2013 (Inception) to July 31, 2014 were $9,490, $40,540 and $45,540, respectively, all of which are from a related party. Receipts in excess of revenue earned as of the balance sheet date shall be included in deferred revenue. Deferred revenues from the Milestone Method were $0 and $8,500 at July 31, 2014 and October 31, 2013, respectively. |
|
Concentration of Revenue |
|
All the revenue included in the accompanying financial statements is from one line of business, outsourced application development services, from a single related party customer, based in the United Kingdom. |
|
Software Development Costs |
|
Costs incurred in connection with the development of software products are accounted for in accordance with the Financial Accounting Standards Board Accounting Standards Codification ("ASC") 985 “Costs of Software to Be Sold, Leased or Marketed.” Costs incurred prior to the establishment of technological feasibility are charged to research and development expense. Software development costs are capitalized after a product is determined to be technologically feasible and is in the process of being developed for market but may be expensed if the Company is in the development stage. Amortization of capitalized software development costs begins upon initial product shipment. Capitalized software development costs are amortized over the estimated life of the related product (generally thirty-six months), using the straight-line method. The Company evaluates its software assets for impairment whenever events or change in circumstances indicate that the carrying amount of such assets may not be recoverable. Recoverability of software assets to be held and used is measured by a comparison of the carrying amount of the asset to the future net undiscounted cash flows expected to be generated by the asset. If such software assets are considered to be impaired, the impairment to be recognized is the excess of the carrying amount over the fair value of the software asset. During the period from October 4, 2013 (inception) to July 31, 2014, the Company did not capitalize any software development costs. |
|
Website Development Costs |
The Company accounts for website development costs in accordance with ASC 350-50, “Accounting for Website Development Costs” (“ASC 350-50”), wherein website development costs are segregated into three activities: |
|
| 1) | Initial stage (planning), whereby the related costs are expensed. |
| 2) | Development (web application, infrastructure, graphics), whereby the related costs are capitalized and amortized once the website is ready for use. Costs for development content of the website may be expensed or capitalized depending on the circumstances of the expenditures. |
| 3) | Post-implementation (after site is up and running: security, training, admin), whereby the related costs are expensed as incurred. Upgrades are usually expensed, unless they add additional functionality. |
|
The Company has not capitalized any website development costs during the nine months ended July 31, 2014 or the period from October 4, 2013 (Inception) to October 31, 2013, respectively. |
|
Advertising and Promotion |
All costs associated with advertising and promoting products are expensed as incurred. |
|
Research and Development |
|
Expenditures for research and product development costs are expensed as incurred. The Company has expensed development costs of $117,362 and $4,942 during the nine months ended July 31, 2014 and the period from October 4, 2013 (Inception) to October 31, 2013, respectively. |
|
Income Taxes |
|
The Company recognizes deferred tax assets and liabilities based on differences between the financial reporting and tax basis of assets and liabilities using the enacted tax rates and laws that are expected to be in effect when the differences are expected to be recovered. The Company provides a valuation allowance for deferred tax assets for which it does not consider realization of such assets to be more likely than not. |
|
Basic and Diluted Loss Per Share |
|
The basic net loss per common share is computed by dividing the net loss by the weighted average number of common shares outstanding. Diluted net loss per common share is computed by dividing the net loss adjusted on an “as if converted” basis, by the weighted average number of common shares outstanding plus potential dilutive securities. For the periods presented, there were no outstanding potential common stock equivalents and therefore basic and diluted earnings per share result in the same figure. |
|
Stock-Based Compensation |
|
The Company adopted FASB guidance on stock based compensation upon inception on October 4, 2013. Under FASB ASC 718-10-30-2, all share-based payments to employees, including grants of employee stock options, to be recognized in the income statement based on their fair values. Pro forma disclosure is no longer an alternative. The Company recognized $2,686,000 and $50,500 for services and compensation for the nine months ended July 31, 2014 and the period from October 4, 2013 (Inception) to October 31, 2013, respectively. |
|
Recent Accounting Pronouncements |
|
In June 2014, the Financial Accounting Standards Board (FASB) issued Accounting Standards Update (ASU) No. 2014-12, Compensation – Stock Compensation (Topic 718): Accounting for Share-Based Payments When the Terms of an Award Provide That a Performance Target Could Be Achieved after the Requisite Service Period. The new guidance requires that share-based compensation that require a specific performance target to be achieved in order for employees to become eligible to vest in the awards and that could be achieved after an employee completes the requisite service period be treated as a performance condition. As such, the performance target should not be reflected in estimating the grant-date fair value of the award. Compensation costs should be recognized in the period in which it becomes probable that the performance target will be achieved and should represent the compensation cost attributable to the period(s) for which the requisite service has already been rendered. If the performance target becomes probable of being achieved before the end of the requisite service period, the remaining unrecognized compensation cost should be recognized prospectively over the remaining requisite service period. The total amount of compensation cost recognized during and after the requisite service period should reflect the number of awards that are expected to vest and should be adjusted to reflect those awards that ultimately vest. The requisite service period ends when the employee can cease rendering service and still be eligible to vest in the award if the performance target is achieved. This new guidance is effective for fiscal years and interim periods within those years beginning after December 15, 2015. Early adoption is permitted. Entities may apply the amendments in this Update either (a) prospectively to all awards granted or modified after the effective date or (b) retrospectively to all awards with performance targets that are outstanding as of the beginning of the earliest annual period presented in the financial statements and to all new or modified awards thereafter. The adoption of ASU 2014-12 is not expected to have a material impact on our financial position or results of operations. |
|
In June 2014, the FASB issued ASU No. 2014-10: Development Stage Entities (Topic 915): Elimination of Certain Financial Reporting Requirements, Including an Amendment to Variable Interest Entities Guidance in Topic 810, Consolidation, to improve financial reporting by reducing the cost and complexity associated with the incremental reporting requirements of development stage entities. The amendments in this update remove all incremental financial reporting requirements from U.S. GAAP for development stage entities, thereby improving financial reporting by eliminating the cost and complexity associated with providing that information. The amendments in this Update also eliminate an exception provided to development stage entities in Topic 810, Consolidation, for determining whether an entity is a variable interest entity on the basis of the amount of investment equity that is at risk. The amendments to eliminate that exception simplify U.S. GAAP by reducing avoidable complexity in existing accounting literature and improve the relevance of information provided to financial statement users by requiring the application of the same consolidation guidance by all reporting entities. The elimination of the exception may change the consolidation analysis, consolidation decision, and disclosure requirements for a reporting entity that has an interest in an entity in the development stage. The amendments related to the elimination of inception-to-date information and the other remaining disclosure requirements of Topic 915 should be applied retrospectively except for the clarification to Topic 275, which shall be applied prospectively. For public companies, those amendments are effective for annual reporting periods beginning after December 15, 2014, and interim periods therein. Early adoption is permitted. The adoption of ASU 2014-10 is not expected to have a material impact on our financial position or results of operations. |
|
In July 2013, the FASB issued ASU No. 2013-11: Presentation of an Unrecognized Tax Benefit When a Net Operating Loss Carryforward, a Similar Tax Loss, or a Tax Credit Carryforward Exists. The new guidance requires that unrecognized tax benefits be presented on a net basis with the deferred tax assets for such carryforwards. This new guidance is effective for fiscal years and interim periods within those years beginning after December 15, 2013. The adoption of ASU 2013-11 is not expected to have a material impact on our financial position or results of operations. |
|