No they don't, but some 95% works.

I was able to buy music and play it today, but when I tried to install Google Play Music (player), GooglePlay crashed, and it kept crashing after a reboot too. I had to clear up /data/dalvik-cache and reinstall/relink (ln -s) phonesky.apk to /data/app to get it working again. Possibly clearing up just com.android.vending under it might have been enough.

I probably mentioned somewhere that Chrome installs and its menus work, but it does not render canvas. I would have been nice to see that working...

Google Maps is working, but GPS and location services are not. Nor do we have regular android location Settings to configure them (there are Google settings, but that is not enough).

Besides of that there has not been many problems. Occasional GooglePlay crash that haven't caused any further problems. I can buy stuff, and non Google applications have all worked fine. (Youtube is ok too.)

Note: you don't have to install everything in tutorial on this page:
http://jollafin.blogspot.fi/2013/11/...for-jolla.html

Phonesky.apk (GooglePlay store) is already under the signed package that gets copied in the rsync of system directory, and Google Play Service is not absolute necessity unless you wish to update store (I think). So you should need only the signed package contents to get GooglePlay store working:
http://goo.im/gapps/gapps-jb-20121011-signed.zip

Basically the installation of any regular android apps seems to be a process of copying apk file under /data/app. This makes them to pop up in Jolla app menu too.

With Google Apps that get installed under /opt/alien/system/app, you may have to create symbolic links (ln -s) from /opt/alien/system/app to /data/app. Or plain install Phonesky.apk as I did the first time. Note that you don't have to install all of the apps, and Phonesky (and reboot after that) was enough for me.
I later did links for the rest just in case, but it didn't seem to have much effect in results.

After all these however, you may get errors about google voice search, for instance. You can get rid of these by simple unlinking/deleting GoogleEars.apk from the /data/app, and also just in case from /opt/alien/system/app directories, and rebooting.

The guide uses command
'rsync -av --ignore-existing /home/nemo/dir_that_has_gapps/system /opt/alien'
for initial installation of the gapps on the device.

(Remember the backup before doing that with
'cp -r /opt/alien/system /opt/alien/system_bak')

It is wise to do this copying of whole Gapps system directory for now. Cherry picking can be done later when all the Gapps pieces required for basic functionality can be confirmed. It is likely that for just GooglePlay store functionality not all of those are important. But for some other apps, using login stuff or editing your calendar through your account, would not work with just google framework apk and store installed.

This is still quite a lot of fumbling in the dark, but we really do have a (well enough) working GooglePlay in our hands.

EDIT: Made it a bit clearer whether rsync of the whole system directory from the signed package is necessary or not.