Mobility Requirements Sample Clauses

Mobility Requirements a. Application shall be designed in a way that is device agnostic, i.e., application performance will be identical whether the end user is connecting from a desktop versus a tablet or mobile device. b. All menus and forms shall scale to display appropriately on any device, regardless of screen resolution, aspect ratio, or orientation. c. Alternatively, application may provide alternate interfaces or points of entry depending on the end user’s device, e.g., a mobile app for tablets, iPads and smart phones versus a full featured application for workstations and laptops. d. If offline access is required, the application shall accommodate devices with limited space by downloading the minimum amount of data needed to function without an active connection to the server. e. All forms and menus shall be designed for optimal performance over slower or unreliable connections, e.g., virtual private network, satellite or burst wireless connections, Wi- Fi, or a tethered internet connection. f. Whenever possible, application shall offload large workloads to the server to accommodate devices with low-power or slower processors, e.g., tablets or mobile phones. g. Forms and menus shall be designed with touch interaction as the primary expected input method through the use of drop-down lists, on/off switches, and context-specific fields. h. Application shall support native functions of the client device, including but not limited to: on-screen keyboards, voice dictation, predictive text and suggested words, front and rear cameras, and GPS location services.
Sample 1Sample 2
AutoNDA by SimpleDocs
Mobility Requirements i. The system shall be device agnostic, i.e., performance shall be identical whether the end user is connecting from a desktop or a tablet or any mobile device. ii. Menus and forms shall scale to display appropriately on any device, regardless of screen resolution, aspect ratio, or orientation. iii. The system shall be designed for optimal performance over slower or unreliable connections. iv. The system shall be designed as the primary expected input methods through the use of drop-down lists, and context-specific fields.
Sample 1
Mobility Requirements. 31 a. Application shall be designed in a way that is device agnostic, i.e., application 32 performance will be identical whether the end user is connecting from a desktop versus a tablet or 33 mobile device. 34 b. All menus and forms shall scale to display appropriately on any device, regardless of 35 screen resolution, aspect ratio, or orientation. 36 // 37 // 1 c. Alternatively, application may provide alternate interfaces or points of entry depending 2 on the end user’s device, e.g., a mobile app for tablets, iPads and smart phones versus a full featured 3 application for workstations and laptops. 4 d. If offline access is required, the application shall accommodate devices with limited 5 space by downloading the minimum amount of data needed to function without an active connection to 6 the server. 7 e. All forms and menus shall be designed for optimal performance over slower or 8 unreliable connections, e.g., virtual private network, satellite or burst wireless connections, Wi-Fi, or a 9 tethered internet connection. 10 f. Whenever possible, application shall offload large workloads to the server to 11 accommodate devices with low-power or slower processors, e.g., tablets or mobile phones. 12 g. Forms and menus shall be designed with touch interaction as the primary expected 13 input method through the use of drop-down lists, on/off switches, and context-specific fields. 14 h. Application shall support native functions of the client device, including but not limited 15 to: on-screen keyboards, voice dictation, predictive text and suggested words, front and rear cameras, 16 and GPS location services.
Sample 1
Mobility Requirements. 1. The system shall be device agnostic, i.e., application performance shall be identical whether the end user is connecting from a desktop or a tablet or any mobile device. 2. Menus and forms shall scale to display appropriately on any device, regardless of screen resolution, aspect ratio, or orientation. 3. The system shall be designed for optimal performance over slower or unreliable connections. 4. The system shall be designed with the primary expected input methods using drop- down lists, and context-specific fields. 5. If required for functional use, the application shall support native functions of the client device, including but not limited to on-screen keyboards, voice dictation, predictive text and suggested words, front and rear cameras, and GPS virtualization technology, whenever possible, for all new systems.
Sample 1
Mobility Requirements a. Application shall be designed in a way that is device agnostic, i.e., application performance will be identical whether the end user is connecting from a desktop versus a tablet or mobile device. b. All menus and forms shall scale to display appropriately on any device, regardless of screen resolution, aspect ratio, or orientation. c. Alternatively, application may provide alternate interfaces or points of entry depending on the end user’s device, e.g., a mobile app for tablets, iPads and smart phones versus a full featured application for workstations and laptops. County of Orange, Health Care Agency File Folder: M042DR089 Page 12 of 25 Contract MA-042-18011826 d. If offline access is required, the application shall accommodate devices with limited space by downloading the minimum amount of data needed to function without an active connection to the server. e. All forms and menus shall be designed for optimal performance over slower or unreliable connections, e.g., virtual private network, satellite or burst wireless connections, Wi-Fi, or a tethered internet connection. f. Whenever possible, application shall offload large workloads to the server to accommodate devices with low-power or slower processors, e.g., tablets or mobile phones. g. Forms and menus shall be designed with touch interaction as the primary expected input method through the use of drop-down lists, on/off switches, and context-specific fields. h. Application shall support native functions of the client device, including but not limited to: on-screen keyboards, voice dictation, predictive text and suggested words, front and rear cameras, and GPS location services.
Sample 1
Mobility Requirements a. Be device agnostic, i.e., application performance shall be identical whether the end user is connecting from a desktop versus a tablet or mobile device. b. Menus and forms shall (i) scale to display appropriately on any device, regardless of screen resolution, aspect ratio, or orientation, (ii) be designed for optimal performance over slower or unreliable connections, e.g., VPN, satellite or burst wireless connections, Wi-Fi, or a tethered Internet connection, and (iii) be designed with touch interaction as the primary expected input method through the use of drop-down lists, on/off switches, and context-specific fields. c. Provide for alternate points of entry depending on the end user’s device, e.g., mobile application for tablets, iPads and smart phones versus a full featured application for workstations and laptops.
Sample 1

Related to Mobility Requirements

  • Accessibility Requirements Under Tex. Gov’t Code Chapter 2054, Subchapter M, and implementing rules of the Texas Department of Information Resources, the System Agency must procure Products and services that comply with the Accessibility Standards when those Products are available in the commercial marketplace or when those Products are developed in response to a procurement solicitation. Accordingly, Grantee must provide electronic and information resources and associated Product documentation and technical support that comply with the Accessibility Standards.

  • Facility Requirements 1. Maintain wheelchair accessibility to program activities according to governing law, including the Americans With Disabilities Act (ADA), as applicable. 2. Provide service site(s) that will promote attainment of Contractor’s program objectives. Arrange the physical environment to support those activities. 3. Decrease program costs when possible by procuring items at no cost from County surplus stores and by accepting delivery of such items by County.

  • City Requirements Design, construction, materials, sizing, other specifications, permitting, inspections, testing, documentation and furnishing of as-built drawings, and acceptance of completed infrastructure shall be in accordance with City Requirements. Design and construction shall be by professionals licensed in the state of North Carolina to do the relevant work. City approval of the design of the Improvements shall be required prior to construction, as set forth in City Requirements. If Developer is connecting to the County sewer system, the City may require Developer to furnish the contract providing for such connection.

  • Quality Requirements Performance Indicator Heading Indicator (specific) Threshold Method of Measurement Frequency of monitoring Consequence of Breach

  • E-Verify Requirements To the extent applicable under ARIZ. REV. STAT. § 41- 4401, the Contractor and its subcontractors warrant compliance with all federal immigration laws and regulations that relate to their employees and their compliance with the E-verify requirements under ARIZ. REV. STAT. § 23-214(A). Contractor’s or its subcontractor’s failure to comply with such warranty shall be deemed a material breach of this Agreement and may result in the termination of this Agreement by the City.

  • Eligibility Requirements The Trustee hereunder shall at all times (i) be a corporation or association having its principal office in a state and city acceptable to the Seller, organized and doing business under the laws of such state or the United States of America, authorized under such laws to exercise corporate trust powers, having a combined capital and surplus of at least $50,000,000, or shall be a member of a bank holding system, the aggregate combined capital and surplus of which is at least $50,000,000, provided that its separate capital and surplus shall at all times be at least the amount specified in Section 310(a)(2) of the Trust Indenture Act of 1939, (ii) be subject to supervision or examination by federal or state authority and (iii) have a credit rating or be otherwise acceptable to the Rating Agencies such that neither of the Rating Agencies would reduce their respective then current ratings of the Certificates (or have provided such security from time to time as is sufficient to avoid such reduction) as evidenced in writing by each Rating Agency. If such corporation or association publishes reports of condition at least annually, pursuant to law or to the requirements of the aforesaid supervising or examining authority, then for the purposes of this Section the combined capital and surplus of such corporation or association shall be deemed to be its combined capital and surplus as set forth in its most recent report of condition so published. In case at any time the Trustee shall cease to be eligible in accordance with the provisions of this Section, the Trustee shall resign immediately in the manner and with the effect specified in Section 8.08.

  • Safety Requirements The Contractor shall comply with all Federal, State, and local safety laws and regulations applicable to the Work performed under this Agreement.

  • Security Requirements 7.1 The Authority will review the Contractor’s Security Plan when submitted by the Contractor in accordance with the Schedule (Security Requirements and Plan) and at least annually thereafter.

  • Check Requirements Any image of a check that I transmit to you must accurately and legibly provide all the information on the front and back of the check at the time presented to me by the drawer. Prior to capturing the original check, I will indorse the back of the original check. My endorsement will include "For Directions E- Deposit Only" in addition to my signature. The image of the check transmitted to you must accurately and legibly provide, among other things, the following information: (1) the information identifying the drawer and the paying bank that is preprinted on the check, including complete and accurate MICR information and the signature(s); and (2) other information placed on the check prior to the time an image of the check is captured, such as any required identification written on the front of the check and any endorsements applied to the back of the check. The image quality for the check will meet the standards for image quality established by the American National Standards Institute ("ANSI"), the Board of Governors of the Federal Reserve, and any other regulatory agency, clearing house or association. Rejection of Deposit. You are not liable for any service or late charges levied against me due to your rejection of any item. In all cases, I am responsible for any loss or overdraft plus any applicable fees to my Account due to an item being returned. Items Returned Unpaid. A written notice will be sent to me of transactions you are unable to process because of returned items. With respect to any item that I transmit to you for remote deposit that you credit to my Account, in the event such item is dishonored, I authorize you to debit the amount of such item from the Account.

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!