Abstract: A modular, computerized tax return preparation application engine including modular tax logic engine and interface controller components loosely coupled to each other and a modular completion monitor. Modular tax logic engine receives runtime data of the tax return and generates a first non-binding suggestion involving a tax topic that is incomplete based on first runtime data and a decision table. Modular interface controller generates a first interface including a first interview screen including content based on the first non-binding suggestion. For iterations or changes of runtime data, completion monitor determines when a previously complete tax topic is now incomplete and notifies modular interface controller regarding the completion status modification. In response modular interface controller generates a second interface comprising an encoded link to an interview screen or screens to address previously complete but currently incomplete tax topics.

Abstract: A system for explaining added tax questions resulting from modified tax data for an electronic tax return preparation program includes a computing device having a completeness graph engine, an explanation engine, and a user interface controller. The computing device executes the completeness graph engine, which takes a first snapshot of input needs for a completeness graph corresponding to a tax topic, takes a second snapshot of input needs for the completeness graph corresponding to the tax topic after receiving modified tax data, and compares the first and second snapshots to identify an added variable in the completeness graph. An explanation engine analyzes the completeness graph and the modified tax data to generate an explanation asset for the added variable. A user interface controller generates a tax question corresponding to the added variable. The computing device presents the tax question and the explanation asset to a user.

Abstract: Approaches enable three-dimensional (3D) display and interaction with interfaces (such as a webpage, an application, etc.) when the device is operating in a 3D view mode. For example, interface elements can be highlighted, emphasized, animated, or otherwise altered in appearance, and/or arrangement in the renderings of those interfaces based at least in part on an orientation of the device or a position of a user using the device. Further, the 3D view mode can provide for an animated 3D departure and appearance of elements as the device navigates from a current page to a new page. Further still, approaches provide for the ability to specify 3D attributes (such as the appearance, action, etc.) of the interface elements. In this way, a developer of such interfaces can use information (e.g., tags, CSS, JavaScript, etc.) to specify a 3D appearance change to be applied to at least one interface element when the 3D view mode is activated.

Abstract: Systems, methods and articles of manufacture for preparing a tax return in which tax questions may be generated and presented to a user in an ad hoc manner. A tax system includes a computing device executing a tax program. The tax program can display a plurality of user interface presentations, such as interview or question screens, with tax questions asking the user to provide tax data related to a taxpayer for preparing a tax return for the taxpayer. The tax program allows the user to skip a tax question on a user interface presentation, and proceed with subsequent user interface presentations. When the tax program determines that a response to the skipped tax questions is required, the tax program dynamically generates a skipped tax question user interface presentation with the skipped tax question and presents it to the user.

Abstract: Approaches enable three-dimensional (3D) display and interaction with interfaces (such as a webpage, an application, etc.) when the device is operating in a 3D view mode. For example, interface elements can be highlighted, emphasized, animated, or otherwise altered in appearance, and/or arrangement in the renderings of those interfaces based at least in part on an orientation of the device or a position of a user using the device. Further, the 3D view mode can provide for an animated 3D departure and appearance of elements as the device navigates from a current page to a new page. Further still, approaches provide for the ability to specify 3D attributes (such as the appearance, action, etc.) of the interface elements. In this way, a developer of such interfaces can use information (e.g., tags, CSS, JavaScript, etc.) to specify a 3D appearance change to be applied to at least one interface element when the 3D view mode is activated.

Abstract: Approaches enable three-dimensional (3D) display and interaction with interfaces (such as a webpage, an application, etc.) when the device is operating in a 3D view mode. For example, interface elements can be highlighted, emphasized, animated, or otherwise altered in appearance, and/or arrangement in the renderings of those interfaces based at least in part on an orientation of the device or a position of a user using the device. Further, the 3D view mode can provide for an animated 3D departure and appearance of elements as the device navigates from a current page to a new page. Further still, approaches provide for the ability to specify 3D attributes (such as the appearance, action, etc.) of the interface elements. In this way, a developer of such interfaces can use information (e.g., tags, CSS, JavaScript, etc.) to specify a 3D appearance change to be applied to at least one interface element when the 3D view mode is activated.

Abstract: Some implementations include displaying icons on a home screen of a computing device based, at least in part, on a predicted likelihood that an individual one of the icons will be selected. The predicted likelihoods may be determined based on a current time of day, a geo-location of the computing device, a current mode of the computing device, or the like.

Abstract: A system for explaining added tax questions resulting from modified tax data for an electronic tax return preparation program includes a computing device having a completeness graph engine, an explanation engine, and a user interface controller. The computing device executes the completeness graph engine, which takes a first snapshot of input needs for a completeness graph corresponding to a tax topic, takes a second snapshot of input needs for the completeness graph corresponding to the tax topic after receiving modified tax data, and compares the first and second snapshots to identify an added variable in the completeness graph. An explanation engine analyzes the completeness graph and the modified tax data to generate an explanation asset for the added variable. A user interface controller generates a tax question corresponding to the added variable. The computing device presents the tax question and the explanation asset to a user.

Abstract: A system for explaining tax questions for an electronic tax return preparation program includes a computing device having a tax logic agent and a user interface controller. The computing device executes the tax logic agent, which analyzes a completeness graph to identify a required variable. The tax logic agent also determines whether an explanation asset is indexed to the required variable in the completeness graph, and sends an identity of the required variable to a user interface controller. The user interface controller generates a tax question corresponding to the required variable. When the tax logic agent determines that an explanation asset is indexed to the required variable in the completeness graph, the computing device presents the tax question and the explanation asset. When an explanation asset is not indexed to the required variable in the completeness graph, the computing device presents the tax question without the explanation asset.

Abstract: A modular, computerized tax return preparation application engine including modular tax logic engine and interface controller components loosely coupled to each other and a modular completion monitor. Modular tax logic engine receives runtime data of the tax return and generates a first non-binding suggestion involving a tax topic that is incomplete based on first runtime data and a decision table. Modular interface controller generates a first interface including a first interview screen including content based on the first non-binding suggestion. For iterations or changes of runtime data, completion monitor determines when a previously complete tax topic is now incomplete and notifies modular interface controller regarding the completion status modification. In response modular interface controller generates a second interface comprising an encoded link to an interview screen or screens to address previously complete but currently incomplete tax topics.

Abstract: Techniques for increasing the efficacy of an affiliate marketing program are described herein. These techniques may allow participants of the affiliate marketing program to easily create links to content that a content site offers. To do so, the content site may determine whether a user that requests content from the site is a participant of the program or a non-participant. Based at least in part on determining that the requesting user is a participant, the content site may serve the requested content in addition to a mechanism for creating links to the content. Furthermore, the mechanism may also illustrate or otherwise include content that is customized based on the content that the participant requests and/or based on an identity of the participant.

Abstract: Initiating a functionality of an electronic device using the device cover and/or other device inputs is described herein. In some implementations, a sequence of operations may be stored on the device to initiate a specific functionality of the device. Each operation in the sequence may correspond to a manipulation of a position of a device cover or an input from a device input component. Once the device determines that two or more received operations complete the stored sequence, the specific functionality of the device may be initiated.

Abstract: Approaches enable three-dimensional (3D) display and interaction with interfaces (such as a webpage, an application, etc.) when the device is operating in a 3D view mode. For example, interface elements can be highlighted, emphasized, animated, or otherwise altered in appearance, and/or arrangement in the renderings of those interfaces based at least in part on an orientation of the device or a position of a user using the device. Further, the 3D view mode can provide for an animated 3D departure and appearance of elements as the device navigates from a current page to a new page. Further still, approaches provide for the ability to specify 3D attributes (such as the appearance, action, etc.) of the interface elements. In this way, a developer of such interfaces can use information (e.g., tags, CSS, JavaScript, etc.) to specify a 3D appearance change to be applied to at least one interface element when the 3D view mode is activated.

Abstract: Approaches enable three-dimensional (3D) display and interaction with interfaces (such as a webpage, an application, etc.) when the device is operating in a 3D view mode. For example, interface elements can be highlighted, emphasized, animated, or otherwise altered in appearance, and/or arrangement in the renderings of those interfaces based at least in part on an orientation of the device or a position of a user using the device. Further, the 3D view mode can provide for an animated 3D departure and appearance of elements as the device navigates from a current page to a new page. Further still, approaches provide for the ability to specify 3D attributes (such as the appearance, action, etc.) of the interface elements. In this way, a developer of such interfaces can use information (e.g., tags, CSS, JavaScript, etc.) to specify a 3D appearance change to be applied to at least one interface element when the 3D view mode is activated.

Abstract: Approaches enable three-dimensional (3D) display and interaction with interfaces (such as a webpage, an application, etc.) when the device is operating in a 3D view mode. For example, interface elements can be highlighted, emphasized, animated, or otherwise altered in appearance, and/or arrangement in the renderings of those interfaces based at least in part on an orientation of the device or a position of a user using the device. Further, the 3D view mode can provide for an animated 3D departure and appearance of elements as the device navigates from a current page to a new page. Further still, approaches provide for the ability to specify 3D attributes (such as the appearance, action, etc.) of the interface elements. In this way, a developer of such interfaces can use information (e.g., tags, CSS, JavaScript, etc.) to specify a 3D appearance change to be applied to at least one interface element when the 3D view mode is activated.