Could Devin Apps handle your internal approvals?
Someone asks to buy supplies in a chat. You approve it, but a colleague still has to work out whether the order was placed. Devin Apps is worth a small trial if your team already uses Devin and needs a clear view of each request. Start with a tool that records decisions while a person places the order.
A working link for a small team
Cognition introduced Devin Apps on November 13. Devin builds a private web app from your description and hosts it on its own cloud computer. Everyone opening the link must sign in to Devin. The URL stays the same when you update the app. TLDR AI’s November 16 edition brought the launch to our attention.
This could shorten the path from an idea to something colleagues can try. It is most interesting when people need different actions on the same request: submit it, ask a question, approve it, or record completion. If everyone simply edits a few cells, a shared spreadsheet may already do the job.
Cognition’s Devin Apps announcementDiscovery: TLDR AI, November 16
An illustrative request: approved is not ordered
Imagine a small shop requesting €120 of packing materials. This fictional example shows a proposed workflow; we have not tested Devin Apps. The requester wants a decision. The buyer needs to know whether anyone has already placed the order.
A useful first version would show whether the request is waiting for approval, ready to order, or already ordered. A manager can approve it or return it with a question. Approval makes the request ready to order. Only the person who buys the supplies records that the order was placed, with a reference.
That distinction is the reason to build the app. A single green badge marking the request complete would leave the original uncertainty intact. Keep ordering and payment on the supplier’s website during this first trial. The team can judge whether the review process helps before connecting the app to spending.
Try the handover with two colleagues
Use made-up requests and two intended users for this proposed check. These are requirements to ask for and verify; they are not built-in approval features promised by Cognition.
- Have the requester submit the €120 request twice by mistake. The app should show one request, or clearly identify a possible duplicate before anyone acts.
- Sign in as the requester and try to approve it. The app should enforce the roles you agreed, including on its server; hiding a button is not enough.
- Have the manager return the request with a question. The requester should see what needs answering, and the buyer should see that it is not ready to order.
- Approve the request, then record the order separately. Ask both people to explain what happened and who acts next, using only what the app shows.
Who will use the app, and who will maintain it?
Devin Apps is rolling out gradually. If Apps is missing from your Devin sidebar, your account does not have access yet. Check access before planning a trial.
Cognition says ending or archiving the app’s session takes it offline, and a crashed server does not restart automatically. Each app runs on one machine. That makes a low-stakes internal trial more sensible than making it the only way to complete urgent work.
Name someone who can restore the app, and keep a simple way to record requests during an interruption. Restrict access to the intended users and give approval rights only to the designated managers.
Check the app’s running costs
Cognition bills app hosting by the time its machine is awake; building and changing it are billed as session work. Scheduled automation runs also count as sessions. Frequent refreshes can therefore cost more than simply serving the app.
The plan page does not give an Apps-specific hourly price or a complete Apps eligibility list. Confirm access and the cost for your intended viewers with Cognition before buying a plan for this purpose. A general subscription price is not a quote for your finished tool.
For a trial, measure one ordinary cycle: creating the app, correcting it, and having colleagues use it. Review the recorded usage before adding automatic refreshes. The purchase-request example may need no scheduled refresh at all.
How Devin Apps are billedDevin plans and pricingWhere to review Devin usage
Describe one recurring approval
Wait if customers need a public link, if a short interruption would stop essential work, or if your existing form and approval system already answers the question clearly.
Before choosing an app builder, write down the stages of one request and who can move it to the next stage. If that is difficult, sketch the process first. If it is clear but your current tools cannot support it, you have a useful brief for a small app.
Sources
Give one recurring request a clear next step.
Describe who asks, who decides and what happens after approval. forvertz can help scope a small internal tool; a made-up example is enough to start.
Discuss an internal toolUpdated