Revision history [back]

Trying to change the view on Sailfish - it's not about technique, but about using it...

Many of us think that part of the issues Jolla/Sailfish has, including the almost nonexistant market share, derives from an incomplete analysis of the possible target users and their needs. Even as tech savy people we need a reliable phone with basic functionality working just at fingers tip out of the box. In daily life, while busy and working, I don't want to deal with command line or with broken functions. Too many questions on this forum ask just for this, a reliable working phone with nowadays standard functionality. Some of the reported issues are really small things and wait here since years.

But this time I don't want to re-post those issues or rant, and i'm still commited to supporting Jolla. But maybe Jolla doesn't get it right, how we use our Sailfish phones in daily business life, or doesn't know what the real business cases are or how to prioritize them. So I thought that instead of re-posting for the n-th time the same old technical detail problems we all sigh or rant about, I would set up a scheme for my/your/our daily (business) use of Sailfish (no matter which device).

I think we can skip the minimal basic usage, as it's already working (even if sometimes not at the level we might wish). So I hereby define as "Standard Usage"the basic functionality like: lock/unlock, handle phone calls and SMS, connect to WLAN and 4G networks, basic Mail and Internetbrowser app, and little more. Furthermore I think it would help to optionally give 2-3 cues about the context of usage. So, here go my daily life business use cases:

• Context: working in higher education in middle management, traveling regularly
• Typical use case 1: I travel by train with my Sailfish X and a laptop. I usually have good 4G connection and use tethering for working with my laptop. On my laptop I use a virtual desktop on my home university or I connect through VPN. In both cases I need one of the very few android apps I'm forced to use: a specific two factor authentication android app (kind of proprietary OTP).
• Typical use case 2: once arrived I open a native maps application to find my destination and walk there or take a public transportation. During the meeting I connect trough eduroam (WPA-2) and I may take some pictures of the presentation or whiteboard, store them on my dropbox account, and send them to a colleague in my office by e-mail through Sailfish. I may get some E-Mail with an attachment back, which I directly forward to someone else. Realizing it was and outdated attachment, I connect with my Sailfish through VPN to my office and can get the right file from a smb/cifs-share there. Sadly I can't pay my lunc with some NFC app.
• Typical use case 3: traveling back home and relaxing, I don't want to open my laptop again, and just check my e-mails and the next day calendar on the Sailfish phone, using both imap/caldav or ggogle accounts for private and MS Exchange for business. I then whatsapp (my second android app) for a while with my family and call a friend by phone (contact synced with carddav) and an SMS to a third one. I quickly write down a note for things to remember and then lean back listening to music from the music player or internet radio through my bluetooth headphones. And maybe I play a few minutes a (native) sudoku before dozing away, knowing that the clock alarm will wake me up 10 minutes before arrival.

Well, that was my journey, a typical one, where I'd have the Jolla/Sailfish phone all the time with me. And during coffe break I will gladly tell other people, that I own and use an almost unknown mobile ecosystem which is secure, fast, flexible, smart, independent, and fullfills all my requirements.

An what's your story...? :-)

Trying to change the view on Sailfish - it's not about technique, but about using it...

Many of us think that part of the issues Jolla/Sailfish has, including the almost nonexistant market share, derives from an incomplete analysis of the possible target users and their needs. Even as tech savy people we need a reliable phone with basic functionality working just at fingers tip out of the box. In daily life, while busy and working, I don't want to deal with command line or with broken functions. Too many questions on this forum ask just for this, a reliable working phone with nowadays standard functionality. Some of the reported issues are really small things and wait here since years.

But this time I don't want to re-post those issues or rant, and i'm still commited to supporting Jolla. But maybe Jolla doesn't get it right, how we use our Sailfish phones in daily business life, or doesn't know what the real business cases are or how to prioritize them. So I thought that instead of re-posting for the n-th time the same old technical detail problems we all sigh or rant about, I would set up a scheme for my/your/our daily (business) use of Sailfish (no matter which device).

I think we can skip the minimal basic usage, as it's already working (even if sometimes not at the level we might wish). So I hereby define as "Standard Usage"the Usage" the basic functionality like: lock/unlock, handle phone calls and SMS, connect to WLAN and 4G networks, basic Mail and Internetbrowser app, and little more. Furthermore I think it would help to optionally give 2-3 cues about the context of usage. So, here go my daily life business use cases:

• Context: working in higher education in middle management, traveling regularly
• Typical use case 1: I travel by my Sailfish Clock/Alarm wakes me up wiht my preferred tune (too loud atm) an di chekc my calendar. Before leaving home, I quickly check weather and the timetable for possible train with my Sailfish X and a laptop. delays. I usually have good 4G connection and use tethering for working with my laptop. laptop during my travel by train. On my laptop I use a virtual desktop on my home university or I connect through VPN. In both cases I need one of the very few android apps I'm forced to use: a specific two factor authentication android app (kind of proprietary OTP).
• Typical use case 2: once arrived I open a native maps application to find my destination and walk there or take a public transportation. During the meeting I connect trough eduroam (WPA-2) and I may take some pictures of the presentation or whiteboard, store them on my dropbox account, and send them to a colleague in my office by e-mail through Sailfish. I may get some E-Mail with an attachment back, which I directly forward to someone else. Realizing it was and outdated attachment, I connect with my Sailfish through VPN to my office and can get the right file from a smb/cifs-share there. I also may use the calculator for some quick controlling of numbers presented. Sadly I can't pay my lunc lunch with some NFC app.
• Typical use case 3: traveling back home and relaxing, I don't want to open my laptop again, and just check my e-mails and the next day calendar on the Sailfish phone, using both imap/caldav or ggogle accounts for private and MS Exchange for business. I then whatsapp (my second android app) for a while with my family and call a friend by phone (contact synced with carddav) and an SMS to a third one. I quickly write down a note for things to remember and then lean back listening to music from the music player or internet radio through my bluetooth headphones. And maybe I play a few minutes a (native) sudoku before dozing away, knowing that the clock alarm will wake me up 10 minutes before arrival.

Well, that was my journey, a typical one, where I'd have the Jolla/Sailfish phone all the time with me. And As you can see, besides the "Standard usage" I need a lots of functionality wich may work or not, some being broken since the last version, and others never did work correctly. Oh, and I forget to tell, that during coffe break I will would gladly tell other people, that I own and use an almost unknown mobile ecosystem which is secure, fast, flexible, smart, independent, and fullfills all my requirements.

An what's your story...? :-)

Trying to change the view on Sailfish - it's not about technique, but about using it...

Many of us think that part of the issues Jolla/Sailfish has, including the almost nonexistant market share, derives from an incomplete analysis of the possible target users and their needs. Even as tech savy people we need a reliable phone with basic functionality working just at fingers tip out of the box. In daily life, while busy and working, I don't want to deal with command line or with broken functions. Too many questions on this forum ask just for this, a reliable working phone with nowadays standard functionality. Some of the reported issues are really small things and wait here since years.

But this time I don't want to re-post those issues or rant, and i'm still commited to supporting Jolla. But maybe Jolla doesn't get it right, how we use our Sailfish phones in daily business life, or doesn't know what the real business cases are or how to prioritize them. So I thought that instead of re-posting for the n-th time the same old technical detail problems we all sigh or rant about, I would set up a scheme for my/your/our daily (business) use of Sailfish (no matter which device).

I think we can skip the minimal basic usage, as it's already working (even if sometimes not at the level we might wish). So I hereby define as "Standard Usage" the basic functionality like: lock/unlock, handle phone calls and SMS, connect to WLAN and 4G networks, basic Mail and Internetbrowser app, and little more. Furthermore I think it would help to optionally give 2-3 cues about the context of usage. So, here go my daily life business use cases:

• Context: working in higher education in middle management, traveling regularly
• Typical use case 1: my Sailfish Clock/Alarm wakes me up wiht my preferred tune (too loud atm) an di chekc my calendar. Before leaving home, I quickly check weather and the timetable for possible train delays. I usually have good 4G connection and use tethering for working with my laptop during my travel by train. On my laptop I use a virtual desktop on my home university or I connect through VPN. In both cases I need one of the very few android apps I'm forced to use: a specific two factor authentication android app (kind of proprietary OTP).
• Typical use case 2: once arrived I open a native maps application to find my destination and walk there or take a public transportation. During the meeting I connect trough eduroam (WPA-2) and I may take some pictures of the presentation or whiteboard, store them on my dropbox account, and send them to a colleague in my office by e-mail through Sailfish. I may get some E-Mail with an attachment back, which I directly forward to someone else. Realizing it was and outdated attachment, I connect with my Sailfish through VPN to my office and can get the right file from a smb/cifs-share there. A coworker of mine calls me during the meeting and I want to activate my loudspeaker so he can participate for a few minutes. I also may use the calculator for some quick controlling of numbers presented. Sadly I can't pay my lunch with some NFC app.
• Typical use case 3: traveling back home and relaxing, I don't want to open my laptop again, and just check my e-mails and the next day calendar on the Sailfish phone, using both imap/caldav or ggogle accounts for private and MS Exchange for business. I then whatsapp (my second android app) for a while with my family and call a friend by phone (contact synced with carddav) and an SMS to a third one. I quickly write down a note for things to remember and then lean back listening to music from the music player or internet radio through my bluetooth headphones. And maybe I play a few minutes a (native) sudoku before dozing away, knowing that the clock alarm will wake me up 10 minutes before arrival.

Well, that was my journey, a typical one, where I'd have the Jolla/Sailfish phone all the time with me. As you can see, besides the "Standard usage" I need a lots of functionality wich may work or not, some being broken since the last version, and others never did work correctly. Oh, and I forget to tell, that during coffe break I would gladly tell other people, that I own and use an almost unknown mobile ecosystem which is secure, fast, flexible, smart, independent, and fullfills all my requirements.

An what's your story...? :-)

Trying to change the view on Sailfish - it's not about technique, but about using it...

Many of us think that part of the issues Jolla/Sailfish has, including the almost nonexistant market share, derives from an incomplete analysis of the possible target users and their needs. Even as tech savy people we need a reliable phone with basic functionality working just at fingers tip out of the box. In daily life, while busy and working, I don't want to deal with command line or with broken functions. Too many questions on this forum ask just for this, a reliable working phone with nowadays standard functionality. Some of the reported issues are really small things and wait here since years.

But this time I don't want to re-post those issues or rant, and i'm still commited to supporting Jolla. But maybe Jolla doesn't get it right, how we use our Sailfish phones in daily business life, or doesn't know what the real business cases are or how to prioritize them. So I thought that instead of re-posting for the n-th time the same old technical detail problems we all sigh or rant about, I would set up a scheme for my/your/our daily (business) use of Sailfish (no matter which device).

I think we can skip the minimal basic usage, as it's already working (even if sometimes not at the level we might wish). So I hereby define as "Standard Usage" the basic functionality like: lock/unlock, handle phone calls and SMS, connect to WLAN and 4G networks, basic Mail and Internetbrowser app, and little more. Furthermore I think it would help to optionally give 2-3 cues about the context of usage. So, here go my daily life business use cases:

• Context: working in higher education in middle management, traveling regularly
• Typical use case 1: my Sailfish Clock/Alarm wakes me up wiht my preferred tune (too loud atm) an di chekc my calendar. Before leaving home, I quickly check weather and the timetable for possible train delays. I usually have good 4G connection and use tethering for working with my laptop during my travel by train. On my laptop I use a virtual desktop on my home university or I connect through VPN. In both cases I need one of the very few android apps I'm forced to use: a specific two factor authentication android app (kind of proprietary OTP).
• Typical use case 2: once arrived I open a native maps application to find my destination and walk there or take a public transportation. During the meeting I connect trough eduroam (WPA-2) and I may take some pictures of the presentation or whiteboard, store them on my dropbox account, and send them to a colleague in my office by e-mail through Sailfish. I may get some E-Mail with an attachment back, which I directly forward to someone else. Realizing it was and outdated attachment, I connect with my Sailfish through VPN to my office and can get the right file from a smb/cifs-share there. A coworker of mine calls me during the meeting and I want to activate my loudspeaker so he can participate for a few minutes. I also may use the calculator for some quick controlling of numbers presented. Sadly I can't pay my lunch with some NFC app.
• Typical use case 3: traveling back home and relaxing, I don't want to open my laptop again, and just check my e-mails and the next day calendar on the Sailfish phone, using both imap/caldav or ggogle accounts for private and MS Exchange for business. I then whatsapp (my second android app) for a while with my family and call a friend by phone (contact synced with carddav) and an SMS to a third one. I quickly write down a note for things to remember and then lean back listening to music from the music player or internet radio through my bluetooth headphones. And maybe I play a few minutes a (native) sudoku before dozing away, knowing that the clock alarm will wake me up 10 minutes before arrival.

Well, that was my journey, a typical one, where I'd have the Jolla/Sailfish phone all the time with me. As you can see, besides the "Standard usage" I need a lots of functionality wich may work or not, some being broken since the last version, and others never did work correctly. Oh, and I forget to tell, that during coffe break I would gladly tell other people, that I own and use an almost unknown mobile ecosystem which is secure, fast, flexible, smart, independent, and fullfills all my requirements.

An what's your story...? :-)

Trying to change the view on Sailfish - it's not about technique, technology, but about using it...

Many of us think that part of the issues Jolla/Sailfish has, including the almost nonexistant market share, derives from an incomplete analysis of the possible target users and their needs. Even as tech savy people we need a reliable phone with basic functionality working just at fingers tip out of the box. In daily life, while busy and working, I don't want to deal with command line or with broken functions. Too many questions on this forum ask just for this, a reliable working phone with nowadays standard functionality. Some of the reported issues are really small things and wait here since years.

But this time I don't want to re-post those issues or rant, and i'm still commited to supporting Jolla. But maybe Jolla doesn't get it right, how we use our Sailfish phones in daily business life, or doesn't know what the real business cases are or how to prioritize them. So I thought that instead of re-posting for the n-th time the same old technical detail problems we all sigh or rant about, I would set up a scheme for my/your/our daily (business) use of Sailfish (no matter which device).

I think we can skip the minimal basic usage, as it's already working (even if sometimes not at the level we might wish). So I hereby define as "Standard Usage" the basic functionality like: lock/unlock, handle phone calls and SMS, connect to WLAN and 4G networks, basic Mail and Internetbrowser app, and little more. Furthermore I think it would help to optionally give 2-3 cues about the context of usage. So, here go my daily life business use cases:

• Context: working in higher education in middle management, traveling regularly
• Typical use case 1: my Sailfish Clock/Alarm wakes me up wiht my preferred tune (too loud atm) an di chekc my calendar. Before leaving home, I quickly check weather and the timetable for possible train delays. I usually have good 4G connection and use tethering for working with my laptop during my travel by train. On my laptop I use a virtual desktop on my home university or I connect through VPN. In both cases I need one of the very few android apps I'm forced to use: a specific two factor authentication android app (kind of proprietary OTP).
• Typical use case 2: once arrived I open a native maps application to find my destination and walk there or take a public transportation. During the meeting I connect trough eduroam (WPA-2) and I may take some pictures of the presentation or whiteboard, store them on my dropbox account, and send them to a colleague in my office by e-mail through Sailfish. I may get some E-Mail with an attachment back, which I directly forward to someone else. Realizing it was and outdated attachment, I connect with my Sailfish through VPN to my office and can get the right file from a smb/cifs-share there. A coworker of mine calls me during the meeting and I want to activate my loudspeaker so he can participate for a few minutes. I also may use the calculator for some quick controlling of numbers presented. Sadly I can't pay my lunch with some NFC app.
• Typical use case 3: traveling back home and relaxing, I don't want to open my laptop again, and just check my e-mails and the next day calendar on the Sailfish phone, using both imap/caldav or ggogle accounts for private and MS Exchange for business. I then whatsapp (my second android app) for a while with my family and call a friend by phone (contact synced with carddav) and an SMS to a third one. I quickly write down a note for things to remember and then lean back listening to music from the music player or internet radio through my bluetooth headphones. And maybe I play a few minutes a (native) sudoku before dozing away, knowing that the clock alarm will wake me up 10 minutes before arrival.

Well, that was my journey, a typical one, where I'd have the Jolla/Sailfish phone all the time with me. As you can see, besides the "Standard usage" I need a lots of functionality wich may work or not, some being broken since the last version, and others never did work correctly. Oh, and I forget to tell, that during coffe break I would gladly tell other people, that I own and use an almost unknown mobile ecosystem which is secure, fast, flexible, smart, independent, and fullfills all my requirements.

An what's your story...? :-)

@Jolla: yes, dear sailors, your also develop for those kind of people like me!

Trying to change the view on Sailfish - it's not about technology, but about using it...

Many of us think that part of the issues Jolla/Sailfish has, including the almost nonexistant market share, derives from an incomplete analysis of the possible target users and their needs. Even as tech savy people we need a reliable phone with basic functionality working just at fingers tip out of the box. In daily life, while busy and working, I don't want to deal with command line or with broken functions. Too many questions on this forum ask just for this, a reliable working phone with nowadays standard functionality. Some of the reported issues are really small things and wait are waiting here since years.years to be solved.

But this time I don't want to re-post those issues or rant, and i'm still commited to supporting Jolla. But maybe Jolla doesn't get it right, how we use our Sailfish phones in daily business life, or doesn't know what the real business cases are or how to prioritize them. So I thought that instead of re-posting for the n-th time the same old technical detail problems we all sigh or rant about, I would set up a scheme for my/your/our daily (business) use of Sailfish (no matter which device).

I think we can skip the minimal basic usage, as it's already working (even if sometimes not at the level we might wish). So I hereby define as "Standard Usage" the basic functionality like: lock/unlock, handle phone calls and SMS, connect to WLAN and 4G networks, basic Mail and Internetbrowser app, and little more. Furthermore I think it would help to optionally give 2-3 cues about the context of usage. So, here go my daily life business use cases:

• Context: working in higher education in middle management, traveling regularly
• Typical use case 1: my Sailfish Clock/Alarm wakes me up wiht my preferred tune (too loud atm) an di chekc my calendar. Before leaving home, I quickly check weather and the timetable for possible train delays. I usually have good 4G connection and use tethering for working with my laptop during my travel by train. On my laptop I use a virtual desktop on my home university or I connect through VPN. In both cases I need one of the very few android apps I'm forced to use: a specific two factor authentication android app (kind of proprietary OTP).
• Typical use case 2: once arrived I open a native maps application to find my destination and walk there or take a public transportation. During the meeting I connect trough eduroam (WPA-2) and I may take some pictures of the presentation or whiteboard, store them on my dropbox account, and send them to a colleague in my office by e-mail through Sailfish. I may get some E-Mail with an attachment back, which I directly forward to someone else. Realizing it was and outdated attachment, I connect with my Sailfish through VPN to my office and can get the right file from a smb/cifs-share there. A coworker of mine calls me during the meeting and I want to activate my loudspeaker so he can participate for a few minutes. I also may use the calculator for some quick controlling of numbers presented. Sadly I can't pay my lunch with some NFC app.
• Typical use case 3: traveling back home and relaxing, I don't want to open my laptop again, and just check my e-mails and the next day calendar on the Sailfish phone, using both imap/caldav or ggogle accounts for private and MS Exchange for business. I then whatsapp (my second android app) for a while with my family and call a friend by phone (contact synced with carddav) and an SMS to a third one. I quickly write down a note for things to remember and then lean back listening to music from the music player or internet radio through my bluetooth headphones. And maybe I play a few minutes a (native) sudoku before dozing away, knowing that the clock alarm will wake me up 10 minutes before arrival.

Well, that was my journey, a typical one, where I'd have the Jolla/Sailfish phone all the time with me. As you can see, besides the "Standard usage" I need a lots of functionality wich may work or not, some being broken since the last version, and others never did work correctly. Oh, and I forget to tell, that during coffe break I would gladly tell other people, that I own and use an almost unknown mobile ecosystem which is secure, fast, flexible, smart, independent, and fullfills all my requirements.

An what's your story...? :-)

@Jolla: yes, dear sailors, your also develop for those kind of people like me!

Trying to change the view on Sailfish - it's not about technology, but about using it...

Many of us think that part of the issues Jolla/Sailfish has, including the almost nonexistant market share, derives from an incomplete analysis of the possible target users and their needs. Even as tech savy people we need a reliable phone with basic functionality working just at fingers tip out of the box. In daily life, while busy and working, I don't want to deal with command line or with broken functions. Too many questions on this forum ask just for this, a reliable working phone with nowadays standard functionality. Some of the reported issues are really small things and are waiting here since years to be solved.

But this time I don't want to re-post those issues or rant, and i'm still commited to supporting Jolla. But maybe Jolla doesn't get it right, how we use our Sailfish phones in daily business life, or doesn't know what the real business cases are or how to prioritize them. So I thought that instead of re-posting for the n-th time the same old technical detail problems we all sigh or rant about, I would set up a scheme for my/your/our daily (business) use of Sailfish (no matter which device).

I think we can skip the minimal basic usage, as it's already working (even if sometimes not at the level we might wish). So I hereby define as "Standard Usage" the basic functionality like: lock/unlock, handle phone calls and SMS, connect to WLAN and 4G networks, basic Mail and Internetbrowser app, and little more. Furthermore I think it would help to optionally give 2-3 cues about the context of usage. So, here go my daily life business use cases:

• Context: working in higher education in middle management, traveling regularly
• Typical use case 1: my Sailfish Clock/Alarm wakes me up wiht my preferred tune (too loud atm) an di chekc my and still in bed i throw a glance at my todays calendar. Before leaving home, I quickly check weather and the timetable for possible train delays. I usually have good 4G connection and use tethering for working with my laptop during my travel by train. On my laptop I use a virtual desktop on my home university or I connect through VPN. In both cases I need one of the very few android apps I'm forced to use: a specific two factor authentication android app (kind of proprietary OTP).
• Typical use case 2: once arrived I open a native maps application to find my destination and walk there or take a public transportation. During the meeting I connect trough eduroam (WPA-2) and I may take some pictures of the presentation or whiteboard, store them on my dropbox account, and send them to a colleague in my office by e-mail through Sailfish. I may get some E-Mail with an attachment back, which I directly forward to someone else. Realizing it was and outdated attachment, I connect with my Sailfish through VPN to my office and can get the right file from a smb/cifs-share there. A coworker of mine calls me during the meeting and I want to activate my loudspeaker so he can participate for a few minutes. I also may use the calculator for some quick controlling of numbers presented. Sadly I can't pay my lunch with some NFC app.
• Typical use case 3: traveling back home and relaxing, I don't want to open my laptop again, and just check my e-mails and the next day calendar on the Sailfish phone, using both imap/caldav or ggogle accounts for private and MS Exchange for business. I then whatsapp (my second android app) for a while with my family and call a friend by phone (contact synced with carddav) and an SMS to a third one. I quickly write down a note for things to remember and then lean back listening to music from the music player or internet radio through my bluetooth headphones. And maybe I play a few minutes a (native) sudoku before dozing away, knowing that the clock alarm will wake me up 10 minutes before arrival.

Well, that was my journey, a typical one, where I'd have the Jolla/Sailfish phone all the time with me. As you can see, besides the "Standard usage" I need a lots of functionality wich may work or not, some being broken since the last version, and others never did work correctly. Oh, and I forget to tell, that during coffe break I would gladly tell other people, that I own and use an almost unknown mobile ecosystem which is secure, fast, flexible, smart, independent, and fullfills all my requirements.

An what's your story...? :-)

@Jolla: yes, dear sailors, your also develop for those kind of people like me!

Trying to change the view on Sailfish - it's not about technology, but about using it...

Many of us think that part of the issues Jolla/Sailfish has, including the almost nonexistant market share, derives from an incomplete analysis of the possible target users and their needs. Even as tech savy people we need a reliable phone with basic functionality working just at fingers tip out of the box. In daily life, while busy and working, I don't want to deal with command line or with broken functions. Too many questions on this forum ask just for this, a reliable working phone with nowadays standard functionality. Some of the reported issues are really small things and are waiting here since years to be solved.

But this time I don't want to re-post those issues or rant, and i'm still commited to supporting Jolla. But maybe Jolla doesn't get it right, how we use our Sailfish phones in daily business life, or doesn't know what the real business cases are or how to prioritize them. So I thought that instead of re-posting for the n-th time the same old technical detail problems we all sigh or rant about, I would set up a scheme for my/your/our daily (business) use of Sailfish (no matter which device).

I think we can skip the minimal basic usage, as it's already working (even if sometimes not at the level we might wish). So I hereby define as "Standard Usage" the basic functionality like: lock/unlock, handle phone calls and SMS, connect to WLAN and 4G networks, basic Mail and Internetbrowser app, and little more. Furthermore I think it would help to optionally give 2-3 cues about the context of usage. So, here go my daily life business use cases:

• Context: working in higher education in middle management, traveling regularly
• Typical use case 1: my Sailfish Clock/Alarm wakes me up wiht my preferred tune (too loud atm) and still in bed i throw a glance at my todays calendar. Before leaving home, I quickly check weather and the timetable for possible train delays. I usually have good 4G connection and use tethering for working with my laptop during my travel by train. On my laptop I use a virtual desktop on my home university or I connect through VPN. In both cases I need one of the very few android apps I'm forced to use: a specific two factor authentication android app (kind of proprietary OTP).
• Typical use case 2: once arrived I open a native maps application to find my destination and walk there or take a public transportation. During the meeting I connect trough eduroam (WPA-2) and I may take some pictures of the presentation or whiteboard, store them on my dropbox account, and send them to a colleague in my office by e-mail through Sailfish. I may get some E-Mail with an attachment back, which I directly forward to someone else. Realizing it was and outdated attachment, I connect with my Sailfish through VPN to my office and can get the right file from a smb/cifs-share there. A coworker of mine calls me during the meeting and I want to activate my loudspeaker so he can participate for a few minutes. I also may use the calculator for some quick controlling of numbers presented. Sadly I can't pay my lunch with some NFC app.
• Typical use case 3: traveling back home and relaxing, I don't want to open my laptop again, and just check my e-mails and the next day calendar on the Sailfish phone, using both imap/caldav or ggogle accounts for private and MS Exchange for business. I then whatsapp (my second android app) for a while with my family and call a friend by phone (contact synced with carddav) and an SMS to a third one. I quickly write down a note for things to remember and then lean back listening to music from the music player or internet radio through my bluetooth headphones. And maybe I play a few minutes a (native) sudoku before dozing away, knowing that the clock alarm will wake me up 10 minutes before arrival.

Well, that was my journey, a typical one, where I'd have the Jolla/Sailfish phone all the time with me. As you can see, besides the "Standard usage" I need a lots of functionality wich may work or not, some being broken since the last version, and others never did work correctly. Oh, and I forget to tell, that during coffe break I would gladly tell other people, that I own and use an almost unknown mobile ecosystem which is secure, fast, flexible, smart, independent, and fullfills all my requirements.

An And what's your story...? :-)

@Jolla: yes, dear sailors, your also develop for those kind of people like me!

Trying to change the view on Sailfish - it's not about technology, but about using it...

Many of us think that part of the issues Jolla/Sailfish has, including the almost nonexistant market share, derives from an incomplete analysis of the possible target users and their needs. Even as tech savy people we need a reliable phone with basic functionality working just at fingers tip out of the box. In daily life, while busy and working, I don't want to deal with command line or with broken functions. Too many questions on this forum ask just for this, a reliable working phone with nowadays standard functionality. Some of the reported issues are really small things and are waiting here since years to be solved.

But this time I don't want to re-post those issues or rant, and i'm still commited to supporting Jolla. But maybe Jolla doesn't get it right, how we use our Sailfish phones in daily business life, or doesn't know what the real business cases are or how to prioritize them. So I thought that instead of re-posting for the n-th time the same old technical detail problems we all sigh or rant about, I would set up a scheme for my/your/our daily (business) use of Sailfish (no matter which device).

I think we can skip the minimal basic usage, as it's already working (even if sometimes not at the level we might wish). So I hereby define as "Standard Usage" the basic functionality like: lock/unlock, handle phone calls and SMS, connect to WLAN and 4G networks, basic Mail and Internetbrowser app, and little more. Furthermore I think it would help to optionally give 2-3 cues about the context of usage. So, here go my daily life business use cases:

• Context: working in higher education in middle management, traveling regularly
• Typical use case 1: my Sailfish Clock/Alarm wakes me up wiht my preferred tune (too loud atm) and still in bed i throw a glance at my todays calendar. Before leaving home, I quickly check weather and the timetable for possible train delays. I usually have good 4G connection and use tethering for working with my laptop during my travel by train. On my laptop I use a virtual desktop on my home university or I connect through VPN. In both cases I need one of the very few android apps I'm forced to use: a specific two factor authentication android app (kind of proprietary OTP).
• Typical use case 2: once arrived I open a native maps application to find my destination and walk there or take a public transportation. During the meeting I connect trough eduroam (WPA-2) and I may take some pictures of the presentation or whiteboard, store them on my dropbox account, and send them to a colleague in my office by e-mail through Sailfish. I may get some E-Mail with an attachment back, which I directly forward to someone else. Realizing it was and outdated attachment, I connect with my Sailfish through VPN to my office and can get the right file from a smb/cifs-share there. A coworker of mine calls me during the meeting and I want to activate my loudspeaker so he can participate for a few minutes. I also may use the calculator for some quick controlling of numbers presented. Sadly I can't pay my lunch with some NFC app.
• Typical use case 3: traveling back home and relaxing, I don't want to open my laptop again, and just check my e-mails and the next day calendar on the Sailfish phone, using both imap/caldav or ggogle accounts for private and MS Exchange for business. I then whatsapp (my second android app) for a while with my family and call a friend by phone (contact synced with carddav) and an SMS to a third one. I quickly write down a note for things to remember and then lean back listening to music from the music player or internet radio through my bluetooth headphones. And maybe I play a few minutes a (native) sudoku before dozing away, knowing that the clock alarm will wake me up 10 minutes before arrival.

Well, that was my journey, a typical one, where I'd have the Jolla/Sailfish phone all the time with me. As you can see, besides the "Standard usage" I need a lots of functionality wich may work or not, some being broken since the last version, and others never did work correctly. Oh, and I forget to tell, that during coffe break I would gladly tell other people, that I own and use an almost unknown mobile ecosystem which is secure, fast, flexible, smart, independent, and fullfills all my requirements.

And what's your story...? :-)

@Jolla: yes, dear sailors, your you also develop for those kind of people like me!