Posts: 3
Threads: 2
Joined: May 2019
Reputation:
0
Hello everyone, I have been a mbsp user on android but due to the problems that the samsung tablet gives (blackouts, restarts, etc.) I have changed to ipad pro, which in principle seems more reliable and powerful.
To give more confidence to the developer of the system and that can go faster, we could sign up here all the people who would be willing to buy the IOS version. I would be the first: Ipad pro + MBSP + firefly pedal = the perfect team.
Now I must use piascore, I do not like it, and I miss Mbsp a lot, so I want it to arrive as soon as possible.
thank you!
Posts: 13,392
Threads: 302
Joined: Apr 2012
Reputation:
238
The iOS version is going to be created as soon as possible. I have to finish the annotations rework first so that I can use that as the basis for annotating in the iOS version. I'm also finally going full time on MobileSheets starting next year which will give me much more time, allowing me to finish iOS faster. I wish I could create the iOS version sooner, but as it stands now, it's largely a rewrite, because iOS uses a different programming language and different models for things like storage. While there are cross-platform solutions out there, they all have drawbacks, and many of them require you to rewrite your code using an intermediary language anyways, and I would rather have the iOS version be native so that it has the best performance and stability. I really appreciate everyone's support and patience. It's wonderful to know that so many of you like MobileSheetsPro more than the iOS apps already out there, as it gives me confidence that the amount of work required for the iOS version will be worth it.
Mike
Posts: 1,231
Threads: 194
Joined: May 2015
Reputation:
13
(05-21-2019, 02:15 AM)abraham2000 Wrote: due to the problems that the samsung tablet gives (blackouts, restarts, etc.) I have changed to ipad pro
Funny. I have exact the opposite experiences.
Johan
johanvromans.nl — hetgeluidvanseptember.nl — mojore.nl -- howsagoin.nl
Samsung Galaxy Note S7FE (T733) 12.4", Android 13.0, AirTurn Duo & Digit (Gigs).
Samsung Galaxy Note S4 (T830) 10.5", Android 10.0 (maintenance and backup).
Samsung A3 (A320FL), Android 8.0.0 (emergency).
Posts: 13,392
Threads: 302
Joined: Apr 2012
Reputation:
238
05-21-2019, 09:04 AM
(This post was last modified: 05-21-2019, 09:06 AM by Zubersoft.)
Flutter requires you to write your code using the flutter language (which is a completely different kind of programming from java as it is declarative instead of imperative). For anything native that isn't supported by flutter, you have to write the native code and then add the glue to tie it all together. I utilize a large amount of OS specific functionality in each version, so I'd be running up against this problem repeatedly. The last time I checked, flutter also doesn't support all of the native stuff I would need. I do appreciate you bringing it up though, as more and more cross-platform frameworks are being introduced. A lot of people like react native, but once again, it has limitations and drawbacks depending upon what you want to do, and you run into problems when utilizing more complex platform specific functionality.
Mike
Posts: 1,231
Threads: 194
Joined: May 2015
Reputation:
13
Same here. The two band members that still use iDevices always look with envy at the MSPro using others. They can't wait to switch to MSPro as well.
Johan
johanvromans.nl — hetgeluidvanseptember.nl — mojore.nl -- howsagoin.nl
Samsung Galaxy Note S7FE (T733) 12.4", Android 13.0, AirTurn Duo & Digit (Gigs).
Samsung Galaxy Note S4 (T830) 10.5", Android 10.0 (maintenance and backup).
Samsung A3 (A320FL), Android 8.0.0 (emergency).
