XML 18 R8.htm IDEA: XBRL DOCUMENT v3.19.1
Accounting Policies
3 Months Ended
Mar. 31, 2019
Accounting Policies [Abstract]  
Accounting Policies

2. Accounting Policies

Basis of Presentation

The accompanying interim consolidated balance sheet as of March 31, 2019, and the related consolidated statements of operations and comprehensive loss and cash flows for the three months ended March 31, 2019 and 2018, are unaudited. The unaudited consolidated financial statements have been prepared according to the rules and regulations of the Securities and Exchange Commission (“SEC”) and, therefore, certain information and disclosures normally included in financial statements prepared in accordance with accounting principles generally accepted in the United States have been omitted.

In the opinion of management, the accompanying unaudited consolidated financial statements for the periods presented reflect all adjustments which are normal and recurring, and necessary to fairly state the financial position, results of operations, and cash flows of the Company. These unaudited consolidated financial statements should be read in conjunction with the audited financial statements included in our Annual Report on Form 10-K for the fiscal year ended December 31, 2018 filed with the SEC on March 27, 2019.

Intercompany balances and transactions have been eliminated in consolidation.

Operating results for the three months ended March 31, 2019 are not necessarily indicative of the results that may be expected for any other interim period or for the fiscal year ending December 31, 2019.

Recently Adopted Accounting Pronouncements

The Company adopted FASB ASC Topic No. 842, Leases, and related amendments, as of January 1, 2019, utilizing the modified retrospective approach through a cumulative-effect adjustment to equity. We elected the package of practical expedients permitted under the transition guidance within the new standard which allowed us to carry forward the historical lease classification. Adoption of the new standard resulted in the recording of additional net lease assets and lease liabilities of approximately $3.1 million as of January 1, 2019, and an adjustment to retained earnings of $0.1 million. The standard did not materially impact our consolidated net income or earnings per share and had no impact on cash flows. See Note 11 for further details.

Revenue Recognition

The Company adopted FASB ASC Topic No. 606, Revenue from Contracts with Customers, as of January 1, 2018, and recognizes the sale of goods and services based on the five step analysis of transactions as provided in Topic 606 which requires an entity to recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for such goods and services.

In our Wireless segment, we transfer software licenses to our customers on a royalty free, non-exclusive, non-transferrable, limited use basis during the term of the agreement. In some instances, we perform customization services to ensure the software operates within our customer’s operating platforms as well as the operating platforms of the mobile devices used by their end customers before transferring the license. Revenue related to these services is recognized at a point in time upon acceptance of the software license by the customer. We also earn usage based revenue on our platforms. Usage based revenue is generated based on active licenses used by our customer’s end customers, the provision of hosting services, revenue share based on media placements on our platform, and use of our cloud based services. We recognize our usage based revenue when we have completed our performance obligation and have the right to invoice the customer. This revenue is generally recognized monthly or quarterly.

We also provide consulting services to develop customer specified functionality that are generally not on our software development roadmap. We recognize revenue from our consulting services upon delivery and acceptance by the customer of our software enhancements and upgrades. For certain Wireless segment customers we provide maintenance and technology support services for which the customer pays upfront or as we provide the services. When the customer pays upfront, we record the payments as contract liabilities and recognize revenue ratably over the contract period as this is our stand ready performance obligation that is satisfied ratably over the maintenance and technology services period.

As discussed in Note 3, during the first quarter of 2019 we acquired assets associated with the Smart Retail product suite, later branded ViewSpot, from ISM Connect, LLC. Our ViewSpot contracts with the Tier 1 customers include promises to transfer multiple products and services. Determining whether products and services are considered distinct performance obligations that should be accounted for separately versus together may require significant judgment. When a cloud-based service includes both on-premises software licenses and cloud services, judgment is required to determine whether the software license is considered distinct and accounted for separately, or not distinct and accounted for together with the cloud service and recognized over time. Certain cloud services, primarily ViewSpot, depend on a significant level of integration, interdependency, and interrelation between the on-premise applications and cloud services, and are accounted for together as one performance obligation. Revenue from ViewSpot is recognized ratably over the period in which the cloud services are provided.

We receive upfront payments from customers from services to be provided under our ViewSpot arrangements. The advance receipts are deferred and subsequently recognized ratably over the contract period. We also provide consulting services to configure ad hoc targeted promotional content for our customers upon request. These requests are driven by our customer’s marketing initiatives and tend to be short term “bursts” of activity. We recognize these revenues upon delivery of the configured promotional content to the cloud platform.

In our Graphics segment where we sell off-the-self software products with no customization or post sale technology support services, we recognize revenue at the time we transfer control of the product to the customer. This occurs upon shipment of the product or when the customer downloads the software from our website or website of our resellers. We offer a 30 day return option to our customers; a return reserve is established at the time revenue is recorded and the reserve is monitored and adjusted based on actual experience. Historically, returns have been insignificant.

Fair Value Measurements

The Company measures and discloses fair value measurements as required by FASB Accounting Standards Codification (“ASC”) Topic No. 820, Fair Value Measurements and Disclosures.

Fair value is an exit price, representing the amount that would be received to sell an asset, or paid to transfer a liability, in an orderly transaction between market participants. As such, fair value is a market-based measurement that is determined based on assumptions that market participants would use in pricing an asset or a liability. As a basis for considering such assumptions, the FASB establishes a three-tier value hierarchy, which prioritizes the inputs used in the valuation methodologies in measuring fair value:

 

Level 1 - Observable inputs that reflect quoted prices (unadjusted) for identical assets or liabilities in active markets

 

Level 2 - Include other inputs that are directly or indirectly observable in the marketplace

 

Level 3 - Unobservable inputs which are supported by little or no market activity

The fair value hierarchy also requires an entity to maximize the use of observable inputs and minimize the use of unobservable inputs when measuring fair value.

As required by FASB ASC Topic No. 820, we measure our cash and cash equivalents at fair value. Our cash equivalents are classified within Level 1 by using quoted market prices utilizing market observable inputs. 

As required by FASB ASC Topic No. 820, we measured our warrant liability at fair value. Our warrant liability was classified within Level 3 as some of the inputs to our valuation model are either not observable quoted prices or are not derived principally from, or corroborated by, observable market data by correlation or other means.

As required by FASB ASC Topic No. 350, for goodwill and other intangibles impairment analysis, we utilize fair value measurements which are categorized within Level 3 of the fair value hierarchy.