Hello everyone!
I wanted to let you know that we continue working on the new app and that we’ll likely be able to publish a beta version in the first quarter of 2026.
The first beta version won’t have all of FacileThings’ functionalities, but it will have everything needed to execute daily work: capture, clarify, organize lists and projects, choose the next action to perform, etc.
We want to launch this version as soon as possible so you can try it out and give us your feedback, allowing us to improve and complete it throughout the year.
Our goal for 2026 is for the new app to have all the functionality of the old one, plus significant UX improvements, new reference material management, and the ability to communicate with AIs and LLMs.
This is the current state of the beta project:
In recent weeks we’ve been working to improve the performance of the synchronization engine with lists containing thousands of items, we’ve completed the capture stage, and we’re developing the ability to (optionally) clarify inbox items by answering the right questions. Acquiring this mental model is fundamental for those still getting familiar with the method.
One of the most requested UX improvements is the ability to attach files to tasks by dragging and dropping. As you can see in this video, it will be available in the new beta:
That’s all for now.
I wish you happy holidays and a prosperous 2026!
12 comments
Thank you for the update! Can’t wait to try out beta and give feedback. I’m so happy with the progress made. Have a deserved break and let’s crush our goals in 2026!
Thank you for the update! Can’t wait to try out beta and give feedback. I’m so happy with the progress made. Have a deserved break and let’s crush our goals in 2026!
Will there be a Beta group to test? If so, is there an enrollment? I really look forward to seeing the updates and enhancements that you build in to a product that I use to manage both my personal and professional lives. Best wishes for a happy holiday season and happy new year.
Will there be a Beta group to test? If so, is there an enrollment? I really look forward to seeing the updates and enhancements that you build in to a product that I use to manage both my personal and professional lives. Best wishes for a happy holiday season and happy new year.
Well on track. I'm looking forward to being part of the beta program in the first quarter of 2026.
Well on track. I'm looking forward to being part of the beta program in the first quarter of 2026.
Thanks for the update Francisco. I am looking forward to being part of the beta test. From what I remember you are the only app which is trying to express all six horizons (1) ground or tasks, (2) aggregation of tasks into projects, (3) areas of focus or responsibility, (4) short-term goals, (5) vision, and (6) guiding principles/standards and being able to trace them up and down
I don't see fixes for Contexts in the list. You will remember that there are five common contexts, namely:
• Specific Location or Place (where the Task occurs)
• Tool or Resource (necessary to perform the Task)
• Presence (or the names/job titles of people or teams who will undertake the Task because it is delegated to them, are responsible for aspects of it such as quality control, or who provide specialist services such as diagnosing or providing troubleshooting analyses)
• Weather (the prevailing conditions that suit the Task), which is very important for people working outdoors like myself
• Occasion (or an important time, event, ceremony, or celebration) which transforms the "complexion" of a whole day and according to David Allen does not belong in the Calendar because it is not an appointment or meeting
These need to be separate dimensions that can be filtered independently to give an accurate decision at the engage step.
Wishing you and the team Merry Christmas and Happy New Year/gary
Thanks for the update Francisco. I am looking forward to being part of the beta test. From what I remember you are the only app which is trying to express all six horizons (1) ground or tasks, (2) aggregation of tasks into projects, (3) areas of focus or responsibility, (4) short-term goals, (5) vision, and (6) guiding principles/standards and being able to trace them up and down
I don't see fixes for Contexts in the list. You will remember that there are five common contexts, namely:
• Specific Location or Place (where the Task occurs)
• Tool or Resource (necessary to perform the Task)
• Presence (or the names/job titles of people or teams who will undertake the Task because it is delegated to them, are responsible for aspects of it such as quality control, or who provide specialist services such as diagnosing or providing troubleshooting analyses)
• Weather (the prevailing conditions that suit the Task), which is very important for people working outdoors like myself
• Occasion (or an important time, event, ceremony, or celebration) which transforms the "complexion" of a whole day and according to David Allen does not belong in the Calendar because it is not an appointment or meeting
These need to be separate dimensions that can be filtered independently to give an accurate decision at the engage step.
Wishing you and the team Merry Christmas and Happy New Year/gary
Hi everyone!
Thank you so much for your interest in participating in the beta testing. There will be a testing group starting with a few users, which we will gradually increase to properly manage feedback. But eventually, all users will have access.
I'll let you know how to get early access closer to the release date ;)
Hi everyone!
Thank you so much for your interest in participating in the beta testing. There will be a testing group starting with a few users, which we will gradually increase to properly manage feedback. But eventually, all users will have access.
I'll let you know how to get early access closer to the release date ;)
Hi Gary,
Yes. I think all contexts related to locations, tools, weather or occasion can be managed with the current tags (words starting with #) while presence is better managed with people tags (words starting with @, representing people, roles or bigger entities) in order to feed agendas.
Thanks for your feedback!
Hi Gary,
Yes. I think all contexts related to locations, tools, weather or occasion can be managed with the current tags (words starting with #) while presence is better managed with people tags (words starting with @, representing people, roles or bigger entities) in order to feed agendas.
Thanks for your feedback!
Hi again Francesco and many thanks for your comment. I still do not see why these are not separate in their own right. It is clear that David Allen has changed his view from 2001 when he first wrote his book on GTD in which he had Context = location after he realised (probably from working with the senior executives) that other factors governed whether a Task could be actioned:
• Specific Location or Place (where the Task occurs)
• Tool or Resource (necessary to perform the Task)
• Presence (or the names/job titles of people or teams who will undertake the Task because it is delegated to them, are responsible for aspects of it such as quality control, or who provide specialist services such as diagnosing or providing troubleshooting analyses)
• Weather (the prevailing conditions that suit the Task), which is very important for people working outdoors like myself
• Occasion (or an important time, event, ceremony, or celebration) which transforms the "complexion" of a whole day and according to David Allen does not belong in the Calendar because it is not an appointment or meeting
Hi again Francesco and many thanks for your comment. I still do not see why these are not separate in their own right. It is clear that David Allen has changed his view from 2001 when he first wrote his book on GTD in which he had Context = location after he realised (probably from working with the senior executives) that other factors governed whether a Task could be actioned:
• Specific Location or Place (where the Task occurs)
• Tool or Resource (necessary to perform the Task)
• Presence (or the names/job titles of people or teams who will undertake the Task because it is delegated to them, are responsible for aspects of it such as quality control, or who provide specialist services such as diagnosing or providing troubleshooting analyses)
• Weather (the prevailing conditions that suit the Task), which is very important for people working outdoors like myself
• Occasion (or an important time, event, ceremony, or celebration) which transforms the "complexion" of a whole day and according to David Allen does not belong in the Calendar because it is not an appointment or meeting
Hi Gary,
I understand the distinction between different types of context, but David Allen is only talking about something conceptual, which has no bearing on management. At the software design level, it doesn't make sense to distinguish between types of context because there are no differentiating attributes; they all serve the same purpose: choosing the most appropriate action at any given time.
Hi Gary,
I understand the distinction between different types of context, but David Allen is only talking about something conceptual, which has no bearing on management. At the software design level, it doesn't make sense to distinguish between types of context because there are no differentiating attributes; they all serve the same purpose: choosing the most appropriate action at any given time.
Thanks, Francisco, for your reply on the eve of Christmas. You justify lumping all five "contexts" together by saying they all serve the same purpose: choosing the most appropriate action at any given time, but this is true of most categories in GTD, e.g., relative priority, due date, etc. Some other GTD apps have separated Presence by calling it People or Contacts, so this seems to contradict your position. In my experience, for example, identifying Tools/Resources serves as a prompt to determine the kind of tool, find a supplier and determine whether a lead time is required to order and obtain materials, say, from overseas.
Thanks, Francisco, for your reply on the eve of Christmas. You justify lumping all five "contexts" together by saying they all serve the same purpose: choosing the most appropriate action at any given time, but this is true of most categories in GTD, e.g., relative priority, due date, etc. Some other GTD apps have separated Presence by calling it People or Contacts, so this seems to contradict your position. In my experience, for example, identifying Tools/Resources serves as a prompt to determine the kind of tool, find a supplier and determine whether a lead time is required to order and obtain materials, say, from overseas.
Hi Gary,
There's no contradiction. FacileThings has tags for presence contexts (@john) and tags for all other contexts (#errands), and I think that's all you need to manage next actions. Separating the other contexts into different types doesn't make sense for management purposes, although it might make organizational sense (I'll keep that in mind for future consideration, I've added a reminder to our Someday/Maybe list).
On the other hand, your example of using contexts to request materials needed to perform an action doesn't make much sense. In fact, a task that can't be performed because it lacks materials isn't even a next action (it's not actionable). Contexts are for choosing the next action, and nothing more. Providing each possible action with everything necessary for its execution (materials, resources, tools) should always be done, but it's independent of the execution context.
I appreciate your perspective. We'll consider identifying context types in the future if the user base perceives that this adds value to their organization. Thank you!
Hi Gary,
There's no contradiction. FacileThings has tags for presence contexts (@john) and tags for all other contexts (#errands), and I think that's all you need to manage next actions. Separating the other contexts into different types doesn't make sense for management purposes, although it might make organizational sense (I'll keep that in mind for future consideration, I've added a reminder to our Someday/Maybe list).
On the other hand, your example of using contexts to request materials needed to perform an action doesn't make much sense. In fact, a task that can't be performed because it lacks materials isn't even a next action (it's not actionable). Contexts are for choosing the next action, and nothing more. Providing each possible action with everything necessary for its execution (materials, resources, tools) should always be done, but it's independent of the execution context.
I appreciate your perspective. We'll consider identifying context types in the future if the user base perceives that this adds value to their organization. Thank you!
Hi Gary, I think your workflow would create more mental clutter than solutions for an average user. If such feature were ever created, I guess I'd turn them off. I suggest however a workaround: start each hashtag with an abbreviation:
• Specific Location or Place: #l_office, #l_home etc
• Tool or Resource: #t_iphone, #t_drill
• Weather: #w_sunny, #w_cloudy
• Occasion: #o_gradution #o_anniversary
Hope this helps or inspires you a little.
Hi Gary, I think your workflow would create more mental clutter than solutions for an average user. If such feature were ever created, I guess I'd turn them off. I suggest however a workaround: start each hashtag with an abbreviation:
• Specific Location or Place: #l_office, #l_home etc
• Tool or Resource: #t_iphone, #t_drill
• Weather: #w_sunny, #w_cloudy
• Occasion: #o_gradution #o_anniversary
Hope this helps or inspires you a little.
Thanks, Michael, for your response. I don't think you understand my comment because your suggestion actually would add to mental clutter because it would require each of your coded prefixes to be deciphered. My suggestion is simpler because they are separate and is consistent with GTD. As I understand it, Francisco is trying to strictly present GTD in an app that the David Allen organisation hasn't been able to do, despite an abandoned attempt for Windows.
Thanks, also, Francisco. My comments to Michael also apply to your Lumping" suggestion. Materials is a resource and I think you misunderstood the point I was making about Tools/Resources "lead time". It is no different to needing a tool I dont possess which entails a decision on how I can procure it or if I need to come up with an alternative to stay on schedule. I think this kind of realisation is something that David Allen can take credit for through his Review step. I will be interested to see what is in the beta and what is slated to follow
Merry Christmas and Happy New Year/gary
Thanks, Michael, for your response. I don't think you understand my comment because your suggestion actually would add to mental clutter because it would require each of your coded prefixes to be deciphered. My suggestion is simpler because they are separate and is consistent with GTD. As I understand it, Francisco is trying to strictly present GTD in an app that the David Allen organisation hasn't been able to do, despite an abandoned attempt for Windows.
Thanks, also, Francisco. My comments to Michael also apply to your Lumping" suggestion. Materials is a resource and I think you misunderstood the point I was making about Tools/Resources "lead time". It is no different to needing a tool I dont possess which entails a decision on how I can procure it or if I need to come up with an alternative to stay on schedule. I think this kind of realisation is something that David Allen can take credit for through his Review step. I will be interested to see what is in the beta and what is slated to follow
Merry Christmas and Happy New Year/gary