XML 17 R7.htm IDEA: XBRL DOCUMENT v3.10.0.1
Accounting Policies
9 Months Ended
Sep. 30, 2018
Accounting Policies [Abstract]  
Accounting Policies

2. Accounting Policies

Basis of Presentation

The accompanying interim consolidated balance sheet as of September 30, 2018, and the related consolidated statements of operations and comprehensive loss and cash flows for each of the three and nine months ended September 30, 2018 and 2017, 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, 2017 filed with the SEC on March 30, 2018 and amended April 17, 2018.

Intercompany balances and transactions have been eliminated in consolidation.

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

Recently Issued Accounting Pronouncements

In August 2018, the Financial Accounting Standards Board (“FASB”) issued Accounting Standards Update (“ASU”) No. 2018-13, Fair Value Measurement (Topic 820), which is designed to improve the effectiveness of disclosures related to fair value measurements. This ASU is effective for annual periods beginning after December 15, 2019 and early adoption is allowed in any interim reporting periods within those annual reporting periods. The Company is currently assessing the impact that this ASU will have on its consolidated financial statements.

In February 2016, the FASB issued ASU No. 2016-02, Leases (Topic 842), to increase transparency and comparability among organizations by recognizing all lease transactions (with terms in excess of 12 months) on the balance sheet as a lease liability and a right-of-use asset (as defined). The ASU is effective for fiscal years beginning after December 15, 2018, including interim periods within those fiscal years, with earlier application permitted. Upon adoption, the lessee will apply the new standard retrospectively to all periods presented or retrospectively using a cumulative effect adjustment in the year of adoption. The Company will be evaluating the impact of this guidance on our consolidated financial statements.

In May 2014, the FASB issued ASU No. 2014-09, Revenue from Contracts with Customers (Topic 606). This updated standard supersedes nearly all existing revenue recognition guidance under the accounting principles generally accepted in the United States of America (“U.S. GAAP”). The core principle of this Topic is to recognize revenues when promised goods or services are transferred to customers in an amount that reflects the consideration that is expected to be received for those goods or services. This Topic defines a five-step process to achieve this core principle and, in doing so, it is possible more judgment and estimates may be required within the revenue recognition process than are required under existing U.S. GAAP, including identifying performance obligations in the contract, estimating the amount of variable consideration to include in the transaction price and allocating the transaction price to each separate performance obligation. In July 2015, the FASB deferred the effective date of Topic 606 to annual reporting periods beginning after December 15, 2017 (including interim reporting periods within those periods). The amendments may be applied retrospectively to each prior period presented or retrospectively with the cumulative effect recognized as of the date of initial application. The Company adopted the provisions of Topic 606 during the first quarter of 2018, and there was no impact on the consolidated financial statements.

Revenue Recognition

We currently report our net revenues under two operating groups: Wireless and Graphics. Generally, we recognize revenue when persuasive evidence of an arrangement exists, delivery has occurred, the price is fixed and determinable, and collectability is probable.  We recognize revenues from sales of our software (or software that we are licensed to distribute) to our customers or end users as completed products are shipped and title passes, or from royalties generated as authorized customers duplicate our software, if the other requirements are met. If the requirements are not met as of the date of shipment, revenue is not recognized until these elements are known or resolved.

For Wireless, we recognize revenue using several different methods beyond the method previously mentioned. First, we provide some customers a subscription service arrangement (the “Platform”). This Platform is then deployed to their customers, the end users, either directly by our customer or by the end user initiating a download of the Platform. Our service arrangement can include the use of the software application, hosting services, and maintenance and support services for the Platform. This type of arrangement is recognized on a point in time basis separately for each billing cycle (i.e. monthly or quarterly) based on the individual metrics within that period, and results in either a fixed fee per end user or a revenue sharing arrangement based on amounts received by our customers. Second, we provide other related services to some customers specific to hosting services, and maintenance and support services. These arrangements are recognized on a per period basis (i.e. typically monthly or quarterly) based on the individual arrangements agreed upon with our customers. These arrangements typically include a fixed fee for services offered within the period.  Sometimes these types of services include up-front, non-refundable set-up fees. Revenue is recognized for these fees over the term of the agreement.  Third, we provide a limited custom software development services under a fixed fee arrangement. This revenue is recognized based on agreed-upon deliverables and milestones – when value is provided to the customer a portion of the revenue is recognized. There are no significant judgments required for this revenue. However, we do make some estimates to accrue revenue through the fiscal quarter ends.  

For Graphics, we review available retail channel information and make a determination of a return provision for sales made to distributors and retailers based on current channel inventory levels and historical return patterns. Certain sales to distributors or retailers are made on a consignment basis. Revenues for consignment sales are not recognized until sell-through to the final customer is established. Certain revenues are booked net of revenue sharing payments. Sales directly to end users are recognized upon shipment. End users have a thirty-day return period, but such returns are reasonably estimable and have historically been minimal. We also provide technical support to our customers. Such costs have historically been insignificant.

Deferred revenue represents amounts billed to customers for which revenue has not been recognized. Deferred revenue primarily consists of the unearned portion of monthly, quarterly and annually billed service fees and prepayments made by customers for a future period.

Revenues on a disaggregated basis are as follows (in thousands):

 

 

 

For the Three Months Ended September 30,

 

 

For the Nine Months Ended September 30,

 

 

 

2018

 

 

2017

 

 

2018

 

 

2017

 

 

 

(unaudited)

 

 

(unaudited)

 

Wireless:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Software

 

$

48

 

 

$

193

 

 

$

311

 

 

$

264

 

Platform

 

 

5,908

 

 

 

3,603

 

 

 

15,780

 

 

 

10,858

 

Services

 

 

339

 

 

 

593

 

 

 

1,406

 

 

 

1,954

 

Contract

 

 

(12

)

 

 

301

 

 

 

108

 

 

 

602

 

Total wireless

 

$

6,283

 

 

$

4,690

 

 

$

17,605

 

 

$

13,678

 

Graphics:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Software

 

 

242

 

 

 

1,114

 

 

 

1,328

 

 

 

3,564

 

Total revenues

 

$

6,525

 

 

$

5,804

 

 

$

18,933

 

 

$

17,242

 

 

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 measure our warrant liability at fair value. Our warrant liability is 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. 820, we utilize quoted market prices to estimate the fair value of our fixed rate debt, when available. If quoted market prices are not available, we calculate the fair value of our fixed rate debt based on a currently available market rate, assuming the loans are outstanding through maturity and considering the collateral securing the loans. In determining the current market rate for fixed rate debt, a market spread is added to the quoted yields on federal government treasury securities with similar terms to the debt.