Prosecution Insights
Last updated: November 04, 2026
Application No. 18/908,677

Systems and Methods for Hosted Applications

Non-Final OA §103§DOUBLEPATENT
Filed
Oct 07, 2024
Priority
Aug 28, 2012 — provisional 61/694,166 +8 more
Examiner
OLSHANNIKOV, ALEKSEY
Art Unit
2118
Tech Center
2100 — Computer Architecture & Software
Assignee
Sweetlabs Inc.
OA Round
1 (Non-Final)
56%
Grant Probability
Moderate
1-2
OA Rounds
1y 1m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 56% of resolved cases
56%
Career Allowance Rate
198 granted / 357 resolved
+0.5% vs TC avg
Strong +52% interview lift
Without
With
+52.3%
Interview Lift
resolved cases with interview
Typical timeline
3y 2m
Avg Prosecution
32 currently pending
Career history
401
Total Applications
across all art units

Statute-Specific Performance

§101
8.4%
-31.6% vs TC avg
§103
60.2%
+20.2% vs TC avg
§102
11.8%
-28.2% vs TC avg
§112
17.2%
-22.8% vs TC avg
Black line = Tech Center average estimate • Based on career data from 357 resolved cases

Office Action

§103 §DOUBLEPATENT
DETAILED ACTION This non-final rejection is responsive to the claims filed 03 April 2025. Claims 2-21 are pending. Claims 2, 9, and 16 are independent claims. Claim 1 is cancelled. Claims 2-21 are new. Notice of Pre-AIA or AIA Status The present application is being examined under the pre-AIA first to invent provisions. Double Patenting The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969). A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b). The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/process/file/efs/guidance/eTD-info-I.jsp. Claims 2-21 rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-18 of U.S. Patent No. 12,141,223 B2 and claims 1-20 of U.S. Patent No. 11,741,183 B2 and claims 1-20 of U.S. Patent No. 11,347,826 B2 and claims 1-22 of U.S. Patent No. 11,010,538 B2 and claims 1-20 of U.S. Patent No. 10,430,502 B2 and claims 1-25 of U.S. Patent No. 9,792,265 B2 and claims 1-30 of U.S. Patent No. 8,799,771 B2 and claims 1-19 of U.S. Patent No. 8,775,925 B2. Although the claims at issue are not identical, they are not patentably distinct from each other. Claim Rejections - 35 USC § 103 The following is a quotation of pre-AIA 35 U.S.C. 103(a) which forms the basis for all obviousness rejections set forth in this Office action: (a) A patent may not be obtained though the invention is not identically disclosed or described as set forth in section 102, if the differences between the subject matter sought to be patented and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains. Patentability shall not be negated by the manner in which the invention was made. Claims 1-7, 9-13, and 15-21 are rejected under pre-AIA 35 U.S.C. 103(a) as being unpatentable over Meredith (US 2011/0314389 A1) hereinafter known as Meredith in view of Boodman (US 8,407,584 B1) hereinafter known as Boodman. Regarding independent claim 1, Meredith teaches: A computing device, the computing device comprising: a user interface; (Meredith: Fig. 5 and ¶[0100]; Meredith teaches a desktop computing environment.) a memory storing: processor instructions for rendering a hosted application; and an operating system; and (Meredith: ¶[0017], [0089], [0116]; Meredith teaches a processor and non-volatile storage, a rendering layer 56, and the Application Platform can be integrated within the operating system.) a processor, wherein the processor is configured to: communicate data with the user interface and the memory; and execute the processor instructions to: (Meredith: Fig. 4 and [0017], [0094], [0125]; Meredith teaches the processor executing stored instructions and exchanging data with the interface and storage.) obtain: a first set of one or more resources associated with the hosted application; and (Meredith: [0114], [0118]; Meredith teaches downloading the cross-platform application, which includes a background page and a pop-up page and images.) a second set of one or more resources associated with a webpage; (Meredith: [0103], [0105], [0125]; Meredith retrieving the webpage and/or assets indicated by a specific URL. Further, [0107] teaches that the pop-up page loads a twitter login web page 126.) modify a computing environment of the operating system based on the first set of one or more resources; (Meredith: [0093], [0102], [0118]; Meredith teaches obtaining a file containing a background page. [0093] further teaches the rendering engine layer parses the file to implement the logic contained therein.) … for the hosted application based on: the first set of one or more resources; and the second set of one or more resources; and (Meredith: [0103], [0105]; Meredith teaches rendering the hosted application’s page by retrieving data from a remote serve to populate the notification or user interface.) render, on the user interface, a user interface page integrated into the computing environment …. (Meredith: [0094], [0103]-[0104]; Meredith teaches rendering user interface pages.) Meredith does not explicitly teach but Boodman teaches: build a document object model (DOM) … . (Boodman: col. 9, lines 49-61 and col. 11, lines 34-40; Boodman teaches rendering a page as a DOM built from the page’s content.) … based on the DOM. (Boodman: col. 9, lines 49-61 and col. 11, lines 34-40; Boodman teaches rendering a page as a DOM built from the page’s content.) Meredith and Boodman are in the same field of endeavor as the present invention, as the references are directed to executing application packages. It would have been obvious, before the effective filing date of the claimed invention, to a person of ordinary skill in the art, to combine the application platform that renders the pages from the application package files populated with webpage resources retrieved from remote servers as taught in Meredith with the rendered page as a DOM. As such, it would have been obvious to one of ordinary skill in the art to modify the teachings of Meredith to include teachings of Boodman, because the combination would allow the page to be represented as a data structure that defines the structure, content, and appearance of the page and allows the browser application to render the page in a desired manner, as suggested by Boodman: col. 4, lines 23-45. Regarding claim 3, Meredith in view of Boodman further teaches the computing device of claim 2. Meredith further teaches. wherein: the first set of one or more resources comprises a background page file comprising a first set of interface instructions configured for managing user interactions with the hosted application; and (Meredith: [0093], [0094], [0118]; Meredith teaches obtaining a file with a background page and that the cross-platform application can be implemented using a background page that contains all the logic of the application. Further, the platform’s APIs enable logic within the background page or the pop-up page to modify and respond to interactions with launch points such as icons 76 within the user’s computing environment or to respond to a user hovering over or clicking on the application’s icon.) … Boodman further teaches: the second set of one or more resources comprises a modification file comprising a second set of interface instructions for rendering the webpage on the hosted application. (Boodman: col. 8, lines 7-18 and lines 48-61 and col. 9, lines 1-18; Boodman teaches that “the content script may be configured to read and/or modify the page model (e.g., DOM) 114 of the page 110” and “a given content script should … be injected into the page 110 to be loaded” and “may be registered in the manifest file with the corresponding extension” and that “a given content script may be configured to be injectable to a set of pages … a given domain name may be associated with the web page 110 … and all of these related web page may be associated with the extension icon 120”.) Regarding claim 4, Meredith in view of Boodman further teaches the computing device of claim 3. Meredith further teaches. wherein at least one of the first set of interface instructions or the second set of interface instructions comprises a set of one or more API calls for functions to be performed at a location selected from the group consisting of a remote server and a local module located on the computing device. (Meredith: [0091], [0094], [0105]; Meredith teaches the background page’s instructions work by calling APIs to act on the computing environment. In response to the API calls, the integration layer can communicate with the operating system and/or processes to modify the user’s computing environment. Also, the notification “is populated with data retrieved rom Facebook’s servers via appropriate APIs”.) Regarding claim 5, Meredith in view of Boodman further teaches the computing device of claim 2. Meredith further teaches. wherein … comprises modifying at least one of the first set of one or more resources based on at least one of the second set of one or more resources. (Meredith: [0103], [0105], [0118]; Meredith teaches filling in the pop-up page with the Facebook data fetched from the web.) Boodman further teaches. … building the DOM … . (Boodman: col. 4, lines 37-47, col. 9, lines 50-61, and col. 11, lines 34-40; Boodman teaches the rendering engine builds the page it is about to draw a DOM tree.) Regarding claim 6, Meredith in view of Boodman further teaches the computing device of claim 2. Meredith further teaches. wherein the processor is further configured to execute the processor instructions to: detect user interactions with the user interface page; and (Meredith: [0094], [0107]; Meredith teaches detecting a user’s interaction with the sign-in button.) generate an additional user interface page based on: the user interactions; the first set of one or more resources; and the second set of one or more resources. (Meredith: [0107]; Meredith teaches a new page appears when the user presses the button. The pop-up window grows and loads Twitter’s login page inside it.) Regarding claim 7, Meredith in view of Boodman further teaches the computing device of claim 2. Boodman further teaches. wherein the first set of one or more resources governs modification of a piece of content selected from the group consisting of video content, picture content, textual content, and audio content. (Boodman: col. 8, lines 28-47; Boodman teaches the background page may be enabled to send a message to the content script, to change the appearance of the browser page. The content scripts may be configured to identify URLs within the webpage and convert them into hyperlinks. Content script may be configured to increase or decrease a font size of the page.) Regarding claims 9-13 and 15-21, these claims recite an operating system and a method that performs the function of the computing device of claims 1-7; therefore, the same rationale for rejection applies. Claims 8 and 14 are rejected under pre-AIA 35 U.S.C. 103(a) as being unpatentable over Meredith in view of Boodman in view of Isaacs (US 2007/0050477 A1) hereinafter known as Isaacs. Regarding claim 8, Meredith in view of Boodman further teaches the computing device of claim 2. Meredith in view of Boodman does not explicitly teach but Isaacs teaches. wherein the second set of one or more resources comprises a cascading style sheet. (Isaacs: Fig. 3 and [0024] and [0031]; Isaacs teaches the server holds web pages which may be provided to the client device by the web server, such as style sheets.) Isaacs is in the same field of endeavor as the present invention, since it is directed to retrieving resources from a server for rendering a browser. It would have been obvious, before the effective filing date of the claimed invention, to a person of ordinary skill in the art, to combine the retrieval of resource for populating and rendering the page as taught in Meredith in view of Boodman with the retrieval of the web page’s style sheet as taught in Isaacs. As such, it would have been obvious to one of ordinary skill in the art to modify the teachings of Meredith and Boodman to include teachings of Isaacs, because the combination would allow style sheets, which are already used in pages, to be rendered, as suggested by Isaacs: [0024], [0025]. Regarding claim 14, this claim recites an operating system that performs the function of the computing device of claim 8; therefore, the same rationale for rejection applies. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to ALEX OLSHANNIKOV whose telephone number is (571)270-0667. The examiner can normally be reached M-F 9:30-6. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Scott Baderman can be reached at 571-272-3644. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /ALEKSEY OLSHANNIKOV/Primary Examiner, Art Unit 2118
Read full office action

Prosecution Timeline

Oct 07, 2024
Application Filed
Oct 26, 2026
Non-Final Rejection mailed — §103, §DOUBLEPATENT (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12782905
MACHINE TOOL CONTROL DEVICE, AND MACHINE TOOL
2y 7m to grant Granted Nov 03, 2026
Patent 12769293
COMPACT-FORM MODEL-FREE ADAPTIVE DISTURBANCE COMPENSATION CONTROL IN THE PRESENCE OF UNMEASURABLE DISTURBANCES
2y 12m to grant Granted Oct 20, 2026
Patent 12766917
VEHICLE AIR CONDITIONING CONTROL SYSTEM
2y 8m to grant Granted Oct 20, 2026
Patent 12759104
MACHINE TOOL AND CONTROL DEVICE FOR MACHINE TOOL
2y 1m to grant Granted Oct 13, 2026
Patent 12749899
DISTRIBUTED-POWER-SOURCE CONTROL SYSTEM
2y 4m to grant Granted Sep 29, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
56%
Grant Probability
99%
With Interview (+52.3%)
3y 2m (~1y 1m remaining)
Median Time to Grant
Low
PTA Risk
Based on 357 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month