I’ve just pushed an update to Spoons, which has the following:
– Added a clear view of how many spoons are Planned and how many are marked Completed.
– The pink Spoon Count is now simply the daily quota.
– Big Fix where spoon counts may not update when added or removed.
– Link to Twitter and Web Site added to Settings.
Spoons was designed around the request from a close friend of mine who suffers chronic pain. In a way, this is very much in the DNA of Valley Software, as we focus on people’s mental and physical wellbeing along with creative expression.
They had found the Spoons method of managing pain in hindsight, but hadn’t been able to apply it as a plan for days ahead or as a recording system to work with their medical professionals.
So we worked together to make Spoons as fast, simple and effective as possible, knowing that in these cases all energy is precious.
As with all things health related; privacy is a big concern. So keeping you, the customer, at heart; all data is kept on your device (not cloud) and we made it paid (one off purchase) to support a 100% advertising and marketing free experience.
We’d love your Feedback on Spoons, which can be submitted at our Feedback Page.
With your feedback we can prioritise features and enhancements for version 2 of this already popular app.
For those interested in the technical backend of things; Spoons is made with Xamarin Forms in C# with a local SQLite Database.
I’ve been tinkering in Xamarin, to allow my development to more easily target multiple mobile platforms.
I’ve made a start on two apps, and I just hit a little wall that was easily fixed but I thought was worth sharing:
The Xamarin tutorials show navigation as being done with a “Push” like this:
await Navigation.PushAsync (newPage2Xaml ());
Which is great, except it doesn’t work out of the box.
The issue is for this to function, you need your app to be utilizing a NavigationPage element. A Navigation page is a page which holds other pages and navigation… I suppose (very) roughly like a Frame in UWP.
But the default templates don’t include one. So the easy way to change it is to go to your App.xaml.cs and change the constructor from opening a regular page like this:
MainPage = new MyAppName.Views.MainView();
to this creating a NavigationPage and then “Push”-ing to the start view**:
var p = new NavigationPage();
MainPage = p;
Now your whole application exists within the NavigationPage element and navigation should work as intended.
** Yes the var is not required, however this is a logical layout to show the example.