Timeline for OBSOLETE - Official Stack Overflow iOS App
Current License: CC BY-SA 4.0
24 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Aug 7, 2023 at 5:46 | history | edited | Glorfindel♦ |
Marked as obsolete
|
|
| S Aug 7, 2023 at 5:46 | history | suggested | Rohit Gupta | CC BY-SA 4.0 |
Marked as obsolete
|
| Aug 7, 2023 at 3:06 | review | Suggested edits | |||
| S Aug 7, 2023 at 5:46 | |||||
| Nov 30, 2021 at 20:05 | review | Close votes | |||
| Dec 1, 2021 at 7:02 | |||||
| Jul 18, 2021 at 15:33 | comment | added | Sudipta Roy | It’s not available on app store anymore | |
| Dec 31, 2020 at 8:38 | comment | added | ChW | Has anybody an info why the app is currently not available in IOS store? | |
| Jun 18, 2020 at 8:33 | history | edited | CommunityBot |
Commonmark migration
|
|
| Apr 7, 2019 at 14:53 | comment | added | Rakete1111 | Did this app get taken down by Apple just like Google took down the Android version or did you decide to discontinue it? | |
| May 17, 2017 at 18:48 | history | edited | Brian Nickel | CC BY-SA 3.0 |
Updated with details from launch
|
| May 9, 2017 at 18:56 | comment | added | Brian Nickel | @ShadowWizard Guess I should rephrase. The app will still have some key features from SE.app. Split list and item view in landscape, live question preview, but it isn't getting special UI treatment in the way of having it's own special navigation compared to iPhone and it won't have its own custom user profile view. Some views will definitely be sparse or overly spread out compared to their iPhone counterparts, but probably not much more so than in the SE app. | |
| May 9, 2017 at 8:20 | comment | added | Shadow Wizard | Thanks @Brian. But due to the big difference in screen size between the devices, won't the lack of treatment cause lots of layout/design issues? | |
| May 8, 2017 at 17:35 | comment | added | Brian Nickel | @ShadowWizard It was just going to be iPhone initially, but now it's going to be iOS without much special treatment on iPad. Updated. | |
| May 8, 2017 at 17:35 | history | edited | Brian Nickel | CC BY-SA 3.0 |
deleted 3 characters in body; edited title
|
| S May 4, 2017 at 14:28 | history | suggested | Shadow Wizard | CC BY-SA 3.0 |
Early is incorrect at this point.
|
| May 4, 2017 at 10:12 | comment | added | Shadow Wizard | @Brian was the app renamed from iOS app to iPhone app? Those are different things, as there are many devices which are not iPhone which run under iOS. | |
| May 4, 2017 at 10:10 | review | Suggested edits | |||
| S May 4, 2017 at 14:28 | |||||
| Jan 23, 2017 at 22:37 | comment | added | bb216b3acfd8f72cbc8f899d4d6963 | Please, no. Keep it in one app. | |
| Jan 17, 2017 at 23:13 | comment | added | Brian Nickel |
@BrockAdams There's no timeline yet for new features (and API backing them), just focussed getting the app working. Still, there are some smaller changes like submitting suggested edits, tag preferences, and can_ fields ready for 2.3 when I get the app shipped.
|
|
| Jan 14, 2017 at 0:10 | comment | added | J F | So that’s what the original app designers were hired back for! | |
| Jan 13, 2017 at 20:48 | comment | added | ᔕᖺᘎᕊ | This is exciting! :D | |
| Jan 13, 2017 at 20:45 | comment | added | Brock Adams | So, can we expect API version 2.3 (or 3.0)? To support these new features? | |
| Jan 13, 2017 at 20:41 | history | edited | Brock Adams |
edited tags
|
|
| Jan 13, 2017 at 20:09 | review | First posts | |||
| Jan 13, 2017 at 20:41 | |||||
| Jan 13, 2017 at 20:05 | history | asked | Brian Nickel | CC BY-SA 3.0 |