Frequently Asked Questions (FAQ)

• Q: Why is it called the Sapphire Assistant Framework: What is it? What does that mean:
  SAF is an virtual assistant, just like Alexa, Siri, Google Assistant, or Mycroft. I designed the app on the idea that existing assistant apps kind of suck, and they don't really meet the needs of the user. The SAF is designed to be tailored to the specific users needs, and as such can be customized or modified where needed. I built it as a 'framework' because I wanted it to be a platform for experimentation where developer ls can jump in on what they want to change without worrying about the rest. The framework offers a quick way to put together new ideas for testing, but also allows for extension if the existing design doesn't fit your use case

• Q: Can it integrate with Tasker/Mycroft/Termux/Alexa/Google/etc:
  Yes. Due to its heavily modular design it should be able to interface with just about any other app. See the page on customizing for more information

• Q: Why isn't it published on F-Droid:
  I will be publishing it on F-Droid at a later time, but currently it is not suitable for non-developers, and it's not particularly fun to look at it's UI when everything is happening on the back end. Once the app reaches beta quality I will be making a repository for F-Droid so that more people can try it out

• Q: Does it not work on Android 11:
  It should work as is on Android 11, I just don't have the resources to buy an Android 11 based phone and test it. If anything needs to be changed, it's likely the Manifest in CoreModule needs a query permission added

• Q: Does it need Root?
  It does not need Root to work

• Q: Does it rely on Google Play services:
  The app does not rely on any Google Play services.

• Q: Why on device? Its resource intensive:
  There were multiple reasons I decided to have the SAF work on device out of the box. First, I don't always have internet access, and I don't like losing phone functionality when I don't have internet. Second, many peoples phones are their only computer, therefore I wanted an assistant that was the most useful to the largest number of people. Third, it's a more secure initial setup. Because everything is processed on device, there is no risk of accidentally transmitting information to the wrong place, or having a 3rd party lose your data to a cyber security breach. An assistant may be handling sensitive and intimate details of your life, and as such I wanted to reduce the number of places that data goes without the consent of the user. Fourth, the SAF is highly customizable, so it is fairly trivial to swap out the on device resource intensive modules with remote server modules. Doing things on device was the tricky part, and by getting that out of the way other developers can quickly implement the easy parts.

• Q: What is your use case for it:
  I have ADHD. I have always found myself struggling to manage my schedule, time, and projects. This has caused many issues throughout my life, and I have found the tools to remedy it to be lack-luster. I also care greatly about user freedoms and rights in a digital world, and am uncomfortable sharing all if the intimate details of my life with a company that uses me for data mining and profit. I designed the SAF to be a useful tool that I can refine, and that grows with my needs as my life changes. I currently work in an environment where I am often without the internet, and needed to be able to rely on my device to maintain full functionality. Also, I do machine learning and data science for fun, and I wanted a way to track data about myself so that I could use it to gain new insight and have a better quality life for my wife and I. Through trying numerous different apps, programs, and approaches I found non of them suitable and decided to make my own. As such, the SAF is designed to be a craftsman's tool, which fits well in the hand and is well suited to the task that needs accomplishing. It puts the power in the users hands, since nobody knows their needs better than themselves.