[SailfishDevel] together.jolla.com "Harbour/Store: support for paid applications"

[TE]

@my-jolla I completely agree with you (well, except from the sh**thole
part). I wonder what action can be taken to at least get some statement
from the Jolla sailors. As TJC and this mailing list are obviously
ignored, what other means do we have? Maybe we should:

* Place the topic regularly at the collaboration meetings.
* Send an open letter (devs --> Jolla CEO) – maybe as snailmail.
* Start a petition for paid app support.

As for the apps which are rotting on your harddisk: Have you considered
"selling" the apps as a package via crowdfunding? At least you would
gain some revenue (compared to nothing when leaving the potentially
sinking ship). The community would benefit from fresh apps which maybe
cannot patch the sh*thole but reduce the sinking speed...


On 27.03.2017 09:47, no-re...@jolla.com wrote:
> 
> my-jolla  posted a
> comment
> 
> 
> 
> Commented by my-jolla:
> 
> @bocephus  What "many
> years"? I participated in this discussion twice in 2015, and now came
> back here after two years. So what sense does it make to exaggerate so
> IDIOTICALLY? But you're right - this dreadful company (and its customers
> like you) definitely aren't worth the time spent here. You've just
> gotten rid of yet another developer who wanted to develop for this
> platform. A few more to go and you can close this sh*thole for good,
> mission accomplished.
> 
> In reply to my-jolla's answer:
> 
> So. FOUR freaking years since the launch of Sailfish OS, and TWO
> freaking years after they ensured that "support for paid apps is top
> priority for them", not only there's still absolutely NOTHING in this
> regard, but no one from Jolla has even just mentioned a word about it
> since early 2015 or so. This thread (for years being the top 6th when it
> comes to the number of votes, out of 16,700 topics on this site) has
> always been completely ignored by them, too.
> 
> As a result, Salfish OS remains the ONLY mobile platform on Earth that
> does not support paid apps and therefore does not offer ANY incentives
> for developers to come and make apps for this OS, so they just don't.
> Which in turn causes that during FOUR years since 2013 this platform got
> several times less of native apps than what even the ultra-niche Nokia
> N9 or N900 got in less than 2 years. Read: the least of ALL mobile
> platforms ever created, including even GEOS of the first Nokia
> Communicators in t he '90s. A few hundred native apps in 4 years is a
> DISASTER, and it won't ever change unless developers are allowed to
> monetize their apps on this platform.
> 
> This situation is totally incomprehensible for every sane person. What
> is Jolla's plan? To fully rely on the outdated (and in fact approaching
> its EOL) Android 4.x runtime forever? Will they ever be able to update
> it to at least Android 5 and Google Services (that almost all new
> Android apps now require)? DOUBTFUL, because Google does not permit it
> to be used by non-OHA members and on devices where Android isn't the
> host OS. Even BlackBerry wasn't permitted to upgrade their Alien Dalivk
> Android runtime beyond Android 4.x on their BB10 phones (which
> eventually killed that OS). So what will Jolla do in a year or two when
> their Android 4.x runtime becomes as obsolete as what Android 2.x is
> now, and with no native apps whatsoever? This is the LAST MOMENT to
> finally start building a strong native ecosystem.
> 
> Moreover, due to BB10 demise, it is the last time to try to attract some
> BB10 developers who are RIGHT NOW forced to look for new platforms to
> develop for. BB10 is a Qt-based platform like SFOS, so porting apps is
> easy and quick and not much learning is required for a BB10 developer to
> get familiar with SFOS. So even if SFOS (due to its size) couldn't offer
> MUCH revenue for a BB10 developer, that quickness and easiness of
> porting apps would surely convince many BB10 developers to quickly port
> their apps to SFOS and earn a few bucks. But if this platform continues
> not to offer ANY monetizing possibilities, ABSOLUTELY NO ONE will
> bother. By 2018 all BB10 developers will move to either Android or iOS,
> and once they make the effort to learn their APIs and establish position
> on those tough markets, none of them will ever bother to even think
> about going back to as tiny platform as Jolla.
> 
> It's been now FOUR years since I could not stop wondering how such an
> easy thing as adding payment su pport to the existing app store has been
> completely ignored by Jolla. There are countless companies which fully
> handle the whole online payment process in exchange for a small
> commission (like 1% or so). As app stores usually take 30%, it would
> still leave 29% for Jolla, for doing nothing. Even the app testing / QA
> process would 

Re: [SailfishDevel] together.jolla.com

[AL13N]

there's a roadmap tag

that's good enough for me...

> what I'd like to see is a roadmap (important not only for developers but
> also for regular customers) that can be seen on the main Jolla or Sailfish
> page. This could be literally a visualized graph or something like that.
> On that map should be rough dates to the next releases and issues/features
> that are planned to be in this release. If you would link from the roadmap
> to the together.jolla.com page and vice versa, there would be enough
> information in a sense of "ah, this is why it's done first" or "ah, yes
> it's done at all, nice!".
> Maybe questions/topics on the together.jolla.com page could have a special
> marker/icon that shows on the first glimpse that it is accepted by Jolla
> and will be done in near future.
>
> On top of that a kind of sort function would be cool. "Give the top ten
> voted questions/feature requests".
>
> About the double entries: AFAIK most Jolla team members are in holidays,
> so there is and will be a backlog and there is still the human factor ;-)
>
> BR.
> Sven
>
> P.S.: I was so bold to use this thread because it fitted most but it's not
> a direct comment to the preceding mails...
>
>
> On 26.12.2013, at 12:33, David Greaves  wrote:
>
>> On 26/12/13 00:23, AL13N wrote:
 ... is open! Go there and contribute with ideas :)
>>>
>>> awesome idea... hadn't thought of that.
>>>
>>> some things:
>>> 1. bad search (results in too much duplicates)
>>> 2. wiki post is a bit useless
>>>  A) either remove wiki post
>>>  B) or ability to make a real wiki post
>>>* no answers
>>>* no comments
>>>* easy internal linking
>>> 3. unanswered is becoming huge fast
>>>  A) maybe some kind of an accepted answer from Jolla if it's on the
>>> roadmap?
>>
>> Agree - Unanswered feels like it is going to become full of unanswerable
>> feature-requests. See :
>>
>> https://together.jolla.com/question/427/break-down-your-ideasfeature-requests/#post-id-496
>>
>> These would then be visible like this:
>> https://together.jolla.com/questions/scope:all/sort:activity-desc/tags:voteforme/page:1/
>>
>> However those tags (which basically say "do the community want this")
>> are being
>> removed.
>>
>> Anyone got any better ideas?
>>
>>>  B) how to handle things that are more for community? does this mean
>>> the
>>> app dev can just pose an answer that can be accepted for his app?
>>
>> Yes see comment above about having 'Unanswered' be for community to
>> answer
>>
>>>  C) ... i donno any real solutions
>>
>> Apparently nor do I :)
>>
>> David
>>
>> ___
>> SailfishOS.org Devel mailing list
>
> ___
> SailfishOS.org Devel mailing list
>


___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] together.jolla.com

[Sven Putze]

Hi all,

what I'd like to see is a roadmap (important not only for developers but also 
for regular customers) that can be seen on the main Jolla or Sailfish page. 
This could be literally a visualized graph or something like that. On that map 
should be rough dates to the next releases and issues/features that are planned 
to be in this release. If you would link from the roadmap to the 
together.jolla.com page and vice versa, there would be enough information in a 
sense of "ah, this is why it's done first" or "ah, yes it's done at all, nice!".
Maybe questions/topics on the together.jolla.com page could have a special 
marker/icon that shows on the first glimpse that it is accepted by Jolla and 
will be done in near future.

On top of that a kind of sort function would be cool. "Give the top ten voted 
questions/feature requests".

About the double entries: AFAIK most Jolla team members are in holidays, so 
there is and will be a backlog and there is still the human factor ;-)

BR.
Sven

P.S.: I was so bold to use this thread because it fitted most but it's not a 
direct comment to the preceding mails...


On 26.12.2013, at 12:33, David Greaves  wrote:

> On 26/12/13 00:23, AL13N wrote:
>>> ... is open! Go there and contribute with ideas :)
>> 
>> awesome idea... hadn't thought of that.
>> 
>> some things:
>> 1. bad search (results in too much duplicates)
>> 2. wiki post is a bit useless
>>  A) either remove wiki post
>>  B) or ability to make a real wiki post
>>* no answers
>>* no comments
>>* easy internal linking
>> 3. unanswered is becoming huge fast
>>  A) maybe some kind of an accepted answer from Jolla if it's on the roadmap?
> 
> Agree - Unanswered feels like it is going to become full of unanswerable
> feature-requests. See :
> 
> https://together.jolla.com/question/427/break-down-your-ideasfeature-requests/#post-id-496
> 
> These would then be visible like this:
> https://together.jolla.com/questions/scope:all/sort:activity-desc/tags:voteforme/page:1/
> 
> However those tags (which basically say "do the community want this") are 
> being
> removed.
> 
> Anyone got any better ideas?
> 
>>  B) how to handle things that are more for community? does this mean the
>> app dev can just pose an answer that can be accepted for his app?
> 
> Yes see comment above about having 'Unanswered' be for community to answer
> 
>>  C) ... i donno any real solutions
> 
> Apparently nor do I :)
> 
> David
> 
> ___
> SailfishOS.org Devel mailing list

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] together.jolla.com

[David Greaves]

On 26/12/13 00:23, AL13N wrote:
>> ... is open! Go there and contribute with ideas :)
> 
> awesome idea... hadn't thought of that.
> 
> some things:
> 1. bad search (results in too much duplicates)
> 2. wiki post is a bit useless
>   A) either remove wiki post
>   B) or ability to make a real wiki post
> * no answers
> * no comments
> * easy internal linking
> 3. unanswered is becoming huge fast
>   A) maybe some kind of an accepted answer from Jolla if it's on the roadmap?

Agree - Unanswered feels like it is going to become full of unanswerable
feature-requests. See :

https://together.jolla.com/question/427/break-down-your-ideasfeature-requests/#post-id-496

These would then be visible like this:
https://together.jolla.com/questions/scope:all/sort:activity-desc/tags:voteforme/page:1/

However those tags (which basically say "do the community want this") are being
removed.

Anyone got any better ideas?

>   B) how to handle things that are more for community? does this mean the
> app dev can just pose an answer that can be accepted for his app?

Yes see comment above about having 'Unanswered' be for community to answer

>   C) ... i donno any real solutions

Apparently nor do I :)

David

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] together.jolla.com

[AL13N]

> ... is open! Go there and contribute with ideas :)

awesome idea... hadn't thought of that.

some things:
1. bad search (results in too much duplicates)
2. wiki post is a bit useless
  A) either remove wiki post
  B) or ability to make a real wiki post
* no answers
* no comments
* easy internal linking
3. unanswered is becoming huge fast
  A) maybe some kind of an accepted answer from Jolla if it's on the roadmap?
  B) how to handle things that are more for community? does this mean the
app dev can just pose an answer that can be accepted for his app?
  C) ... i donno any real solutions

___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] together.jolla.com

[Ruediger Schiller]

On Tue, Dec 24, 2013 at 06:22:11PM +0100, Filip Kłębczyk wrote:
> W dniu 24.12.2013 18:10, a.gra...@gmail.com pisze:
> >... is open! Go there and contribute with ideas :)
> 
> and report bugs ;)

Page becomes unresponsive when you change form comment- to answer-input-field.
Cannot send answer without reloading the page only comment.

> 
> Happy Holidays to all list subscribers!
> 
> Regards,
> Filip
> 
> ___
> SailfishOS.org Devel mailing list

so long and thanks for all the fish


Rüdiger Schiller
++
| +** *Chem|st * **+ |
| ++ |
| +** *   www.dostortugas.org  * **+ |
| ## |
| +* Jabber:  trimethylxant...@jabber.org *+ |
| ++ |
++



___
SailfishOS.org Devel mailing list

Re: [SailfishDevel] together.jolla.com

[Filip Kłębczyk]

W dniu 24.12.2013 18:10, a.gra...@gmail.com pisze:

... is open! Go there and contribute with ideas :)


and report bugs ;)

Happy Holidays to all list subscribers!

Regards,
Filip

___
SailfishOS.org Devel mailing list

[SailfishDevel] together.jolla.com

[a.gra...@gmail.com]

... is open! Go there and contribute with ideas :)

Thanks!

-- 
Andrea Grandi -  Software Engineer / Qt Ambassador / Nokia Developer
Champion
website: http://www.andreagrandi.it
___
SailfishOS.org Devel mailing list