Brainstorming ways teachers might be more productive with Microsoft’s New Fluid Framework

Microsoft kicked off a developer conference earlier this week. The Verge writes about a very cool set of forthcoming productivity features.

Microsoft’s new Fluid Office document is Google Docs on steroids – The Verge

Microsoft is creating a new kind of Office document. Instead of Word, Excel, or PowerPoint, the company has created Lego blocks of Office content that live on the web. The tables, graphs, and lists that you typically find in Office documents are transforming into living, collaborative modules that exist outside of traditional documents.

Microsoft calls its Lego blocks Fluid components, and they can be edited in real time by anyone in any app. The idea is that you could create things like a table without having to switch to multiple apps to get it done, and the table will persist on the web like a Lego block, free for anyone to use and edit.

This is obviously very cool, but it’s the next part that gets me excited.

Fluid is designed to make those tables, charts, and lists always feel alive and editable, no matter where you create them and regardless of how you share and copy them into other apps. Instead of getting a static and dull chart you copied from Excel, you’ll get a chart that can be edited anywhere you paste it, and you’ll see everyone making edits as they happen. That might be in the middle of an email chain, in a chat app like Microsoft Teams, or even third-party apps eventually.

So certain parts of Office documents can be shared between multiple spaces, or with multiple users, across multiple apps. If I am understanding this correctly, I can instantly think of 25 ways this could make my job easier. Here are a few…

  1. Copy tasks from a Microsoft To Do project called Field Trip into an email to my music team and have everyone check off tasks in the email as they do them. Status of those completed tasks syncs back to my project in To Do.
  2. Say I am logging a spreadsheet of student concert attire orders and I need some data for a few choir kids. I can copy and paste just those cells, email them to the choir teacher, he can fill out the data right in the email, and I watch as it syncs back to my spreadsheet.
  3. Similar to that last one. My school district sends me an updated list of recommended private teachers. I email just the flute teachers to my flute students and it stays up to date when the data is edited by those who maintain the list.
  4. No more putting the same student names in multiple different documents. I can have one Word document that acts as a primary roster. All concert programs, student lists, sectional roster documents, etc. are just snippets of text from my primary roster document, that automatically update when I update the primary roster. No more misspelled names, inconsistency, or duplicated work.
  5. Various data from documents can be clipped into media rich notes in OneNote where I can access them alongside one another without thinking about document management. For example, a short list of Concert Attire tasks could coexist in the same note as a portion of a payment spreadsheet, and both could update in real time when I edit their respective documents in To Do and Excel.

For the reccord, I don’t use any of Microsoft’s apps as my default tools, but I can certainly see myself using them more often if I can leverage this kind of power out of them.

Some questions I have:

  • Will this be web only or will it eventually roll out to Microsoft apps on all platforms?
  • Will Microsoft stand alone apps like Excel continue to exist or will they be replaced with one app (like the iPhone which now has an “Office” app that combines features of the whole suite)
  • Will this actually catch on with people who are used to saving files to places on their hard drive? It seems ahead of its time.
  • Will it compete with Google Docs? Someone needs to. Google Docs gets a only a few things right, but they get them really right, and that’s why I think it has been so pervasive. Personally, I would far prefer that my work and personal circles relied on great native apps like Office.
  • Will third party apps be able to embed the modular Microsoft elements inside of them, create modular elements to be able to insert in Microsoft docs, or both?
  • Would Apple ever consider participating in this framework with their iWorks apps? Would they recreate their own version?

StaffPad Comes to iPadOS (Reflections on App Store Pricing and Touch Screen Operating Systems)

Five years ago, StaffPad came to Windows Surface tablets. StaffPad is a professional music notation application that turns handwritten notes into beautiful music notation. It is built around the stylus being the primary input, and because the iPad did not have stylus support at launch, StaffPad remained Windows only.

Multiple years into Apple supporting its own official stylus, the Apple Pencil, StaffPad is finally here on iPad!

<div class="sqs-video-wrapper" data-provider-name="YouTube" data-html="

“>

StaffPad’s intro video sells itself, so I am not going to write much about the app here. Instead, I point you to…

StaffPad’s Introductory Blog Post

Download Link to the App Store

Scoring Notes Review – a must read if you are interested

Since the features of StaffPad are covered in the links above, I want to comment on two interesting aspects of this release.

First, the price. At $89.99, this is no impulse purchase. I find it refreshing to see a professionally priced app like this on the App Store. For years, the App Store has seen a race to the bottom type approach for grabbing sales. Users are so used to <5 dollar apps that the idea of paying for software has diminished from reality.

<div class="
      image-block-outer-wrapper
      layout-caption-below
      design-layout-inline
      combination-animation-none
      individual-animation-none
      individual-text-animation-none
    ">




    <figure class="
          sqs-block-image-figure
          intrinsic
        " style="max-width:2500px">







      <div class="image-block-wrapper">
        <div class="sqs-image-shape-container-element



          has-aspect-ratio
        " style="position: relative;padding-bottom:74.95999908447266%;overflow: hidden">







            <img src="https://images.squarespace-cdn.com/content/v1/5595df9ce4b0ce9ff9ecd1a8/1580915051402-K6X26MOI4AOXAB1ZOV52/IMG_2544.png" alt="IMG_2544.png" width="2500" height="1874" style="display:block;object-fit: cover;width: 100%;height: 100%;object-position: 50% 50%" loading="lazy">

        </div>
      </div>






    </figure>


</div>

Increasingly, developers are finding that subscription based pricing is the only way to maintain software and put food on the table. There was a big discussion about this in the Apple community last week when beloved calendar application Fantastical released their version 3 and went to subscription pricing. As is customary when an app goes to subscription pricing, users of the application and bystanders alike were enraged at the idea of a calendar costing four dollars a month.

<div class="
      image-block-outer-wrapper
      layout-caption-below
      design-layout-inline
      combination-animation-none
      individual-animation-none
      individual-text-animation-none
    ">




    <figure class="
          sqs-block-image-figure
          intrinsic
        " style="max-width:1155px">







      <div class="image-block-wrapper">
        <div class="sqs-image-shape-container-element



          has-aspect-ratio
        " style="position: relative;padding-bottom:216.45021057128906%;overflow: hidden">







            <img src="https://images.squarespace-cdn.com/content/v1/5595df9ce4b0ce9ff9ecd1a8/1580915317133-UOKYP5V5RR65Z4AVHD73/IMG_0261.jpeg" alt="I couldn’t resist sneaking my love of Fantastical into this post. The interface is beautiful." width="1155" height="2500" style="display:block;object-fit: cover;width: 100%;height: 100%;object-position: 50% 50%" loading="lazy">

        </div>
      </div>






      <figcaption class="image-caption-wrapper">
        <div class="image-caption"><p class="">I couldn’t resist sneaking my love of Fantastical into this post. The interface is beautiful.</p></div>
      </figcaption>


    </figure>


</div>





















































<div class="
      image-block-outer-wrapper
      layout-caption-below
      design-layout-inline
      combination-animation-none
      individual-animation-none
      individual-text-animation-none
    ">




    <figure class="
          sqs-block-image-figure
          intrinsic
        " style="max-width:1155px">







      <div class="image-block-wrapper">
        <div class="sqs-image-shape-container-element



          has-aspect-ratio
        " style="position: relative;padding-bottom:216.45021057128906%;overflow: hidden">







            <img src="https://images.squarespace-cdn.com/content/v1/5595df9ce4b0ce9ff9ecd1a8/1580915338578-0EX7B5FIOWYUATD1XZQE/IMG_0262.png" alt="And the natural language input is one of many essential features that helps me get my work done more efficiently." width="1155" height="2500" style="display:block;object-fit: cover;width: 100%;height: 100%;object-position: 50% 50%" loading="lazy">

        </div>
      </div>






      <figcaption class="image-caption-wrapper">
        <div class="image-caption"><p class="">And the natural language input is one of many essential features that helps me get my work done more efficiently.</p></div>
      </figcaption>


    </figure>


</div>

As a user of Fantastical, I was happy to keep supporting development. It is one of my most used applications on a daily basis and its features are essential to me having a full time teaching job, while also scheduling gigs, 25 private students, speaking engagements, and all of my other personal events.

Fantastical is what I would call a prosumer application. It offers more power to someone looking for an advanced and well designed calendar, and it has a wide appeal (everyone needs a calendar!). Four dollars a month is steep, but manageable. Now that the price is reoccurring, I do think it will appeal to a smaller audience, as each user will have to reevaluate on a monthly or yearly basis whether or not this application is continuing to be worth the cost.

StaffPad is very different. It is a professional creation tool. Much like Photoshop is essential to designers and photographers, score editors are essential to the lives of most musicians, composers, and music educators. By charging 89 dollars, StaffPad follows a long history of apps in its field, which are often priced between 200 and 600 dollars.

I have to wonder… if the iPad had more software like this, and from an earlier point in time, would users have adjusted their expectations and would more expensive professional apps be more viable? And if so, would the viability of such professional apps lead to more (and better) professional apps on iOS?

And furthermore, would Apple adjust to these trends? Apple still offers no free trial for apps (something that will definitely deter a lot of my music teaching colleagues away from giving StaffPad a chance). Not to mention that professional creative software has a tradition of volume licensing and educator discounts. Educators who would normally be able to afford a program like this for themselves or their class are going to be stuck if they are looking for the same options with StaffPad.

App developers get around to this in number of ways, an example of which is to offer a free app where you have to buy it as an in-app purchase after a week. Of course there is also the subscription model. I am glad StaffPad went with a more traditional model than a subscription because it fits within the tradition of how its class of software is priced. And my hope is that this just might convince more developers to bring their own apps to iPadOS.

Which brings me to my second point…

StaffPad doesn’t, and probably wont, have a macOS app. It is built entirely around stylus input. This is why it could only exist on Windows Surface tablets at first. I am thrilled it is on iPad, but this presents an interesting question for users of Apple products.

A Windows Surface user notices no distinction between whether or not StaffPad operates on a touch-based OS or a traditional point-and-click OS, because they are one and the same. Even as macOS and iPadOS move closer and closer together, this distinction has lead them to be products with very different potentials.

On the other end, all the other players in the score-editor field (Sibelius, Finale, Dorico) remain “desktop” applications that run on traditional point-and-click operating systems. With the power of the current iPad Pro, there is no reason these applications couldn’t exist on iOS, other than that developing for iOS is very different. None of these developers have shown any signs of bringing their programs to iPadOS any time soon, and I would suspect StaffPad has no plans for a Mac version.

I admire how Apple has held their ground about the iPad being the iPad and the Mac being the Mac. It has made both platforms stronger. But as the iPad becomes a more viable machine for getting work done, Apple has got to get a plan for how to solve this essential “input” question.